Hacker News new | ask | show | jobs
by logical42 4847 days ago
the documentation has improved rather drastically as of late. the router api is stable going forward, so it's actually a pretty good time to be experimenting with ember (though this was not true about 4 months ago).

Personally, I really like ember. I think most people would have a better experience with ember if:

(1) they avoided learning off of the master branch during the crazy api changes over the last few months

(2) avoided ember data for the time being (or ever, I have my doubts about how viable it is)

(3) they asked questions on stack. the ember core team is actually pretty snappy at answering questions.

but there is still a bit of lingering weirdness with the router that people should look out for, the things that come to mind are:

a) back button errors

b) awkwardness in the serialize/model hooks depending on whether you're navigating through the app, or trying to get to a url in a new browser window

but despite its shortcomings, I've really grown to love the organization that ember gives to my javascript code base, and how it would make my program scale as it grew in size and complexity.

1 comments

When I took a look at emberjs a few months bach ember-data was one of the most appealing parts. What are your concerns regarding viability?
read-only attributes comes to mind, but that was four months ago and it seems that it's been pretty much worked out here, https://github.com/emberjs/data/pull/303..

Regardless, I still think it's a bit overkill. You'd be surprised to see how much of the basic ember-data functionality you can achieve just by using Ember.A and Ember.Object.