8 Reasons to not use Ember.js for your next project

added by JavaScript Kicks
11/18/2014 2:11:26 PM

302 Views

I was very fortunate a few months ago to have the opportunity to learn and use Ember.js to build a dashboard within an existing rails application. The dashboard felt like a standalone app within our main site and we wanted it to feel very snappy. We decided to give Ember a shot for building it.


4 comments

Drew Peterson
11/18/2014 7:36:19 PM
I can't say I agree with much of what was said here, and the comments rebuke most of them as well. Still, I'd be curious to see what @awgreenarrow08 thinks, given his recent article touting Ember!

Andrew Walton
11/19/2014 12:22:02 AM
Wow. Yeah I saw this the other day and don't really agree with anything there. I know there was a reddit post on it and the commenters rebuked most of the points. I'll just drill down: 1) Silent Errors He's talking about a Handlebars template here. He's trying to render out a property that doesn't exist. Should accessing a property that is null / undefined really cause a JS error? I don't think so. The solution to that is fairly simple: if your data doesn't show up, check your spelling. I think this is more of an issue with the language not being strongly typed and allowing you to type invalid property names than anything else. 2) Deep linking - unreliable I think it's fairly obvious here that he's having an issue with improperly implemented routes. I have deep linking in the Ember apps I've worked on, and was able to get them all to work just fine. I did have this exact issue at one point with deep linking, but it turned out to be me not fully understanding how to correctly implement routes. 3) Few libraries This is becoming less of a problem every day. I saw an article a while back giving a detailed tutorial on pagination in ember, and I believe there is an ember-cli-pagination addon available now. 4) Few code examples / resources I couldn't disagree more here. I feel that the tutorials on the Ember and Ember-cli websites are great resources and give plenty of code samples. 5) Slower development As one of the commenters says: "Do not use an unknown framework for a project on a deadline." Of course you're going to experience slower development with a framework you have no prior experience with. How in the world is this a reason to not use Ember? 6) Added layers and complexity This goes back to #5. He dislikes Ember 'magic' because he is completely unfamiliar with the framework. The same would hold true for a developer who had no prior experience with Ruby, but I don't see him complaining on that front. If you can't tell, at this point I've already started growing tired of this article. 7) It restricted our design I have no way to refute this point without any concrete examples of HOW it restricted their design. In my time using Ember, I still have yet to come across an example of Ember RESTRICTING my design. As with many frameworks / libraries, there will always be times when the framework doesn't lend itself to a particular design paradigm. However, this is not unique to Ember, it happens with all frameworks / libraries. When you hit that point, you pivot and tweak the design a bit. 8) Javascript This is where it all comes to a point. He simply doesn't like Javascript. How in the world could anyone take the author seriously in his review of a Javascript framework when he admits in the article that he dislikes it and basically dismisses it as a language altogether? My advice to the author: if you don't like Javascript, fine. I'm not going to spend time trying to convince you that Javascript isn't the devil and that you should give it another shot. But please. Please. Please don't write another article reviewing a Javascript framework in a negative light just because you don't like the language. Stick with writing reviews on Ruby.

Robert Greyling
11/19/2014 10:41:55 AM
Great synopsis! I was wondering abotu a few of those - thanks for filling in the detail. Sometimes I really wish people would think before delivering such string opinions. Or maybe it's just more evidence for the [Dreyfus model](http://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition) :)

Robert Greyling
11/19/2014 10:43:14 AM
Haha, you can tell I'm a programmer typing string instead of strong :) I really need to work on that "Edit comment" feature =)