[aerogear-dev] JS Future Roadmap

[Bruno Oliveira]

+1000

--  
abstractj

On January 18, 2014 at 1:31:53 PM, Lucas Holmquist (lholmqui at redhat.com) wrote:
>  
> I was having some thoughts on the future of AeroGear.js that i  
> needed to share.
>  
> Experimental Branch
>  
> I think i want to create a branch that is very experimental, that  
> targets new and upcoming API's, like Object.Observe, and Promises,  
> etc…
>  
> I feel this is the only way to drive innovation
>  
> I was thinking this is sort of our "Canary" branch, and when things  
> start to become less pollyfilly, then we can start to move these  
> features in.
>  
> I still however want the code in this branch to be complete, not  
> just random crap
>  
> 2.0
>  
> I would like to see that in 2.0 we start to remove our jQuery requirement,  
> and focus more on Modern Browsers and have our 1.X branch be our  
> less than modern browser( IE9 ) supported branch. much like how  
> jQuery has a 1.X and 2.X branch, obviously the difference between  
> our branches won't be as extreme.
>  
> The major thing we use jQuery for atm is jQuery.ajax and Promises.  
> this is nice for cross broswer compatibility and for transpoting  
> other things other than json, which brings me to my next point  
>  
> I would also like in 2.0 to make our library( pipeline ) only speak  
> json. I think this will make it really simple to have our own AeroGear.Ajax()  
> method and be able to keep it small in size
>  
> 1.X Branch
>  
> Once we hit all our 1.X milestones( sync, offline ) then what is  
> the current master branch would become a 1.X branch, and we recieve  
> bug fixes, but no new features. If something in the future could  
> be back ported, then maybe, but it wouldn't be a priority
>  
> This branch would still have a jQuery requirement and would be  
> for legacy stuff( IE9 )_______________________________________________  
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev