> "More productive out of the box."
> "Write dramatically less code."
> "Absolutely right. Ember promises—and, we think, delivers—tremendous value."
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.
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 banging your head against the limitations and poor design choices of an over-marketed experimental framework?
Let them actually finish the damn thing first, then let's talk about "getting started" with it.
> "Write dramatically less code."
> "Absolutely right. Ember promises—and, we think, delivers—tremendous value."
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.
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 banging your head against the limitations and poor design choices of an over-marketed experimental framework?
Let them actually finish the damn thing first, then let's talk about "getting started" with it.