I met Tom at I/O last year and have been following Ember ever since. It's striking to me how consistently the message among newcomers is "this is hard/confusing". I considered evangelizing it at my then-employer when it was still called SproutCore, but remember thinking "if it's going to take me at least a day or two before I begin to understand, how long is it going to take the rest of my team?" There are a lot of i…
One of the things that I really wish we could discuss as "a collegial group of developers" is whether this is the "Best Effort" or not. Honestly, as it stands, I don't know if I'd ever try and explain Ember to anyone aside from the basics which I've done. The concepts are interesting - as you say - but in practice it just feels like a mediation on "what can we leverage with clever naming" that results in code that is…
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?
http://web.archive.org/web/20110530004346/http://blog.sprout...
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 futzing around with an over-marketed research project?
Let them actually finish the project first, then let's talk about "getting started" with it.