I have a small suggestion for the Ember.js team. When I was trying to learn Ember, I was looking at the source code of the Discourse project and I noticed that they do some things that are AFAIK discouraged (e.g. referencing App.__container__ directly).<p>Idk how much effort it would be to keep an eye on the project and submit an occasional pull request but doing that might be a good idea. Discourse is probably the first place where people go once they have read the docs and want to see Ember in action. And seeing these hacks might reflect badly on the framework even though it's not Ember's fault.
<p><pre><code> EMBERDART
Just kidding.
</code></pre>
I laughed.<p>This progress for Ember is really making me interested - I will probably do my next big app with Ember. I'm happy to see that they are moving away from requiring jQuery & swapping Handlebars to HTMLbars, which will help reduce Ember's JS required footprint, which is massive currently.<p>Nice integration with ES6 also sounds promising. One thing I fight with Angular so far is with asynchronous loading of modules/controllers/directives/services/etc. - while I love Angular, its not good for lazyloading.<p>I'm a bit wary since I have found that I don't like convention over configuration personally, but I am liking some of the high level decisions made recently to refine Ember.
<p><pre><code> Despite the imminent End of Life status of
Windows XP, we will continue supporting
Internet Explorer 8. We know many Ember.js
users still need to target enterprise and
education customers, who will be on IE8
for some time.
</code></pre>
It'll be interesting to see if the Angular folks end up having to walk back their v1.3 removal of IE 8 support. Also, I'm very pleased to see the Ember folks adopting a more 'realistic' attitude.<p>Edit: Also, where's Ember Data?
Inventing their own build tools instead of using a Grunt plugin seems like a severe case of NIH for ember. I'd be curious to hear their rationale beyond "the currently-available options all have fatal flaws that make them unpleasant to use as your app gets larger."
Honestly, Ember has been incredibly frustrating to get going. Mainly in the area of testing—it's a nightmare.<p>The documentation is nicely formatted but missing a lot of context. For such a large project, it needs more than API docs and the overviews are not especially useful.<p>Using it with Rails is a nightmare, you have to fiddle with ember rails and if you want to use anything but Handlebars it's a huge hassle (tags, what? I thought we'd collectively moved past that to things like Haml, Jade, Thin, etc. . .)<p>I love where it's headed and I like a lot of the ideas, but it's been pretty aggravating to get up and running.
Yay EmberConf! Anyone have any idea where it might be?<p>Sidenote, this was really fun to read for some reason, like eating a bunch of little mini cookies.