21–30 of 81 posts
It came and went, plain and simple. It made assumptions and design choices which at the time seemed sound but by today’s standards look silly. Mustache templates for instance. Separating logic from presentation should be a choice not a hard/fast rule with a severely limited templating engine.
Umm, I'm not sure that a "disclaimer" actually nullifies that.
As someone who has moved from using Ember daily for 2+ years to now using React/Redux, I miss Ember on a daily basis. React suffers from lack of standardization like no other. I hate starting a new project or working on an existing project and having to think about where to put things. Ember grew from developers who existed in the Rails space and understood that convention over configuration is the way to go. React d…
As someone who has moved from using Ember daily for 2+ years to now using React/Redux, I miss Ember on a daily basis. React suffers from lack of standardization like no other. I hate starting a new project or working on an existing project and having to think about where to put things. Ember grew from developers who existed in the Rails space and understood that convention over configuration is the way to go. React d…
And it shouldn't even have to sacrifice it's "open/modular" nature to fix that.
The core team (Dan, etc) could just adopt/suggest a few specific companions (router, redux, etc) that they consider "official" part of React, and still allow open interfaces for people to be able to replace them with whatever they want.
Right now there are three main frameworks. Angular, React, and, Vue. Ember has always been the little guy even in the days when Backbone dominated. But it seems to have been replaced by Vue in this regard.
I think there is a lot of tribalism in the js community and liking one framework (often the one you use for work) is synonymous with hating the others. Take this survey done where the people who have "heard of Ember and would NOT use it" is completely outsized with the rest of the data. ( https://stateofjs.com/2017/front-end/results/ ) I've been developing professionally for 15 years and even in that short a time I'v…
As in nature in general, it helps, from an evolutionary standpoint.
Having too many, and letting them all be, instead of people rooting for their favorite and having one or two emerge as the leaders, leads to dispersion of resources, confusion for newcomers, and multiple weaker implementations of the same thing...
Even if the emergent leader is not the best, the mere fact of it having eclipsed the others, means tons of work, libs, documentation, books, support etc will be concentrated towards it.
And it's better to have one leading framework that's 3/5 good with huge community and support, than a 5/5 good framework with lackluster community and support.
I think it's the natural evolution of frameworks. About 5 years ago, we had the Cambrian explosion of front-end frameworks -- Angular, React, Ember, Meteor, Backbone, even jQuery was still hot back then, and certainly dozens more. Technology had advanced enough that we finally were seeing new innovative ways of building web apps, and everyone had their own opinion on how to do it the Right Way. This was certainly goo…
Angular 1 and Backbone belong to an older generation of frameworks imo and shouldn't be lumped in with React and Meteor.
I'd argue that Backbone is from an even older generation.
As someone who has moved from using Ember daily for 2+ years to now using React/Redux, I miss Ember on a daily basis. React suffers from lack of standardization like no other. I hate starting a new project or working on an existing project and having to think about where to put things. Ember grew from developers who existed in the Rails space and understood that convention over configuration is the way to go. React d…
What it suffers from is a small community: we depended on a table component someone wrote which used some weird internal APIs and never got properly upgraded to ember 2.0 so we got stuck with ember 1.x until now because the overhead cost of switching to another library was too high to be worth it. Even then, the maturity of the project has been great and things don't break all the time. The API has been improving and the ember developers are proactive about pulling in the best ideas from newer projects. If you read the Ember RFCs they're always introspective and future-conscious and great. I really hope the project survives, not that I had much doubt. I think there is still quite a dedicated crowd.
I invested a lot of my time over the last few years into Ember and though it was a difficult decision I eventually had to accept that I would be better off moving to Vue.js. I have written a bit about my decision here: https://hackernoon.com/why-i-am-migrating-propertywebbuilder... Its a shame but the reality is that ember will not stand the test of time.