3 ms·

Probably much more than you would think. https://en.wikipedia.org/wiki/Hype_cycle https://en.wikipedia.org/wiki/Hype_cycle Ember is firmly in the "Plateau of

• k__ 8y ago
  The only stuff I heard was that there are many outdated Ember projects that owners need to be updated. My flat mate did a few projects stuck on Ember 1.4 that needed to be updated to 2.0 last year. Somehow Ember devs loved to use private APIs, so most of the apps broke on an update and much had to be re-written.
• lucisferre 8y ago
  I'm not sure how linking to an article about the hype cycle can be considered evidence of Ember's maturity relative to its peers. Ember's 1.0 release was 2013 which is the same year React was announced. Yes Ember has earlier history as Sproutcore going back to 2011, but Facebook was using React internally since 2011 as well. I'd also argue that Ember 2.0 was pretty different from 1.0. Angular is older, going back to 2009, but as 2.0 is a total rewrite as well as departure from where they started out I'm willing to let that one go. (It is also a complete tire fire so let's just ignore it altogether). VueJS is arguably the "new kid". But really only just barely. The first release was Feb 2014. I'd hardly consider Vue immature at this point though. I really don't see how one can argue it has a tangible maturity advantage here. I also think that most of the newer generation of SPA frameworks have learned lessons both from the previous generations and their peers (with the exception of Angular perhaps).
  • gwright 8y ago
    I didn't read that as evidence, simply a link to define the term "Plateau of Productivity".