This is a spectacularly helpful response, speaking well to the culture and philosophy of those behind ember.js.<p>I'm not sure Bill "I feel your pain" Clinton could have put it better.
Add <a href="http://addyosmani.github.com/todomvc/architecture-examples/emberjs/" rel="nofollow">http://addyosmani.github.com/todomvc/architecture-examples/e...</a> to <a href="http://emberjs.com/guides/" rel="nofollow">http://emberjs.com/guides/</a><p>Congratulations it's now much easier.
I really do feel dumb asking this.<p>What the hell does Ember <i>do</i>? Is it another front-end MVC JS library? Is it a competitor to Node? Rails? CodeIgniter? "Ambitious web applications" tells me jack and I get no indication of what its "tremendous value" is.<p>Edit: That sounds a little more aggressive than I meant it to. If anyone can explain it without vomiting buzz words I'd love to understand because it seems intriguing.
Ember has been undoubted advantage for our startup. Its at the core of our client code, there were glitches in learning and rework with Router V2 API but that is still ok in exchange of what we got. So far, we love that we chose EmberJS and we are getting better at using it. But we wish the community grows and people find it easier to adapt.
It's great to see the Ember.js team focusing on these things as the framework approaches a 1.0 release. I've built a few apps on top of Ember over the past few months and that initial learning curve was what lead me to almost abandon it.
I put some effort into getting something working in Ember recently, and after the initial learning curve it did get a bit easier. I'm really glad that they've frozen the API and are getting to work on better documentation.
ok. fair enough. this is a good response and now the community is eager to see the update on this.<p>it would be fair to say that there are a number of developers out there who DO want to try EmberJS (myself included) and that's why there are so many passionate people commenting and discussing on the topic of difficulty in getting started with EmberJS.<p>So I'd say this is a good problem for EmberJS team to have. And hope you guys deliver, because imagine the sheer number of people who will be behind this project when that happens. :) Good luck! I plan to come back to it when I can get my brain around it!
Feedback also can be entered @ <a href="http://discuss.emberjs.com/t/ideas-for-improving-the-getting-started-experience/666" rel="nofollow">http://discuss.emberjs.com/t/ideas-for-improving-the-getting...</a>
Hey - quick thing - when logging in with Facebook to the discussion (<a href="http://discuss.emberjs.com/t/ideas-for-improving-the-getting-started-experience/666" rel="nofollow">http://discuss.emberjs.com/t/ideas-for-improving-the-getting...</a>) I get the Facebook error<p>"Invalid redirect_uri: Given URL is not permitted by the application configuration."<p>which normally means there's something screwy with your app settings (<a href="https://developers.facebook.com/apps/413817622014573" rel="nofollow">https://developers.facebook.com/apps/413817622014573</a>)
> "More productive out of the box."<p>> "Write dramatically less code."<p>> "Absolutely right. Ember promises—and, we think, delivers—tremendous value."<p>No matter how often you say it, doesn't make it true. At a certain point, we have to stop just believing the hype at face value, and start actually evaluating what the piece of software really does with a critical perspective.<p>Aren't the same guys who are telling you that Ember is simple and easy to use and high-performance and well-designed and ambitious and removes boilerplate and cures cancer and kisses babies ... the same guys who were saying the same things about SproutCore two years ago?<p><a href="http://web.archive.org/web/20110530004346/http://blog.sproutcore.com/announcing-sproutcore-2-0/" rel="nofollow">http://web.archive.org/web/20110530004346/http://blog.sprout...</a><p>Isn't the data layer still totally unfinished? Didn't a lot of folks just get burned by wildly changing router APIs? Isn't it obvious from what few public production apps there are (after 2+ years) that the results end up sub-par, glitchy and wonky? Why would you want to spend time banging your head against the limitations and poor design choices of an over-marketed experimental framework?<p>Let them actually finish the damn thing first, then let's talk about "getting started" with it.