[aerogear-dev] Concern with es6 modules and AeroGear.js

[Lucas Holmquist]

for those of you don’t use http based email, i’m looking at you qmx and abstractj,  this might be a little ugly



I want to start off by saying that i think ES6 modules are cool and that i like them.

I think the concern that i have in their current state is that there is to much "processesing" that needs to be done to make them work with existing browsers.

While this processing is done with automated grunt tasks, i feel that it puts to much "extra" code in the library for not that much reward.

Another concern with the processing is that it adds lots more development dependecies. One of which is upgrading to npm 2.0, which wasn't as straightforward as i was thinking.

I do want to commend Lukas, for all his hard work on the es6 modules branch, Good Work My Friend!!

As "developers on the edge"™ we are exposed to new shiny tech that we want to use right away like modules, AMD, browserfy, etc...

But i wonder about the other 90% and what they are looking for. Do they even care about AMD, etc...

I think as a mobile library, we need to not add extra overhead.

But i think we should keep working on the ES6-modules branch and keep it up to date and direct people to that if they would like to try it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150106/0c9bdb3b/attachment-0001.html