Lots of cool stuff in this release, but the best of it is Alex Matchneer's excellent "Router facelift" patch, which standardizes and promise-ifies the router (while not changing the public API, unlike the last router update). He wrote a guide to it here: https://gist.github.com/machty/5723945
I too would love this, but I think it's not going to happen until 1.0 official/ ember data stable. It's really hard to pitch ember as a viable framework until it becomes stable.
The closest thing right now, though, would be Discourse.
I'm working with Balanced right now to build a full dashboard for their payments product using Ember.js. It's open-source and being used by real users. We started with Ember when it went RC for version 1.0 and haven't had any problems so far. Not using Ember Data (didn't play well with our API), but a good app to look at for regular Ember stuff.
For what it's worth, we are about to start a sprint to rebuild the customer-facing side of a Rails application using EmberJS. I will more than likely post a walkthrough of the experience. We have worked a lot with both Backbone and Ember. They are very different tools and I don't think it's fair to compare them directly, but I am definitely a big fan of Ember. I even have a t-shirt!
If you are interested, blog.chriswinn.com is where I will end up posting the Ember walkthrough - probably in the next few weeks.
I am amazed at how a minor RC release of this framework gets voted to the front page every couple of weeks. Whoever is making it happen has some serious HN-foo, or knows how to avoid tripping the voting ring detector.
It certainly was the shizzle until AngularJS came out.
Now, these constant HN front pages for every RC that comes out every other week certainly look a lot more like astroturfing than genuine evidence of popularity.
I think that guy has a point with:
https://github.com/emberjs/ember.js/commits/master/ember.jso....
"Ember is released in "revisions", because it's not production ready and not ready to be 1.0. Hence the core team chose to rather call breaking changes a new "revision". Well guess what dudes, that's exactly what versions are for. Why couldn't you just like normal people release 0.4, 0.5? Why do you need to hit 1.0 directly?"
21 comments
[ 3.0 ms ] story [ 58.5 ms ] threadLots of cool stuff in this release, but the best of it is Alex Matchneer's excellent "Router facelift" patch, which standardizes and promise-ifies the router (while not changing the public API, unlike the last router update). He wrote a guide to it here: https://gist.github.com/machty/5723945
Hacking this past weekend it seems harder to find much in the way of solid guidance past very simple apps.
The closest thing right now, though, would be Discourse.
https://dashboard.balancedpayments.com
https://github.com/balanced/balanced-dashboard
If you are interested, blog.chriswinn.com is where I will end up posting the Ember walkthrough - probably in the next few weeks.
Now, these constant HN front pages for every RC that comes out every other week certainly look a lot more like astroturfing than genuine evidence of popularity.
honestly, i can't think of a better use of something named HACKER NEWS, but maybe i'm new here.
I think that guy has a point with: https://github.com/emberjs/ember.js/commits/master/ember.jso.... "Ember is released in "revisions", because it's not production ready and not ready to be 1.0. Hence the core team chose to rather call breaking changes a new "revision". Well guess what dudes, that's exactly what versions are for. Why couldn't you just like normal people release 0.4, 0.5? Why do you need to hit 1.0 directly?"
I think that now is about time to have version 2.0pre