AngularJS versus Ember
eviltrout.com
AngularJS versus Ember
1–10 of 163 posts
Re: AngularJS versus Ember
#2Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
Re: AngularJS versus Ember
#3Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
I agree. The article is a reasonable discussion of the differences between the two frameworks from the perspective of an experienced Ember user, and does a decent job illustrating why Robin prefers Ember.
The title is argumentative and inflammatory. I think lots of people will read the title on Twitter and roll their eyes at the Ember attack-marketing machine when the article itself contains some valuable points.
Re: AngularJS versus Ember
#4Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
I went back and forth on the title. I don't usually write sensational titles but for some reason decided to give it a try.
I think it's a very good point and I doubt I'll do it again.
Re: AngularJS versus Ember
#5Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
I agree. The article is a reasonable discussion of the differences between the two frameworks from the perspective of an experienced Ember user, and does a decent job illustrating why Robin prefers Ember. The title is argumentative and inflammatory. I think lots of people will read the title on Twitter and roll their eyes at the Ember attack-marketing machine when the article itself contains some valuable points.
You are absolutely correct. I realize I'm in the minority, but I take all blog titles with a bushel of rock salt. Probably because I like to have my own little jokes when I write titles, so I try to ignore what they appear to say and use them only to decide whether to read the post, not to decide whether the post is any good.
Re: AngularJS versus Ember
#6It's not even close for what purpose?
For example, there's a wide common case of simple apps hacked together by 1 or 2 developers, traditionally composed of jQuery spaghetti. Maybe Angular is a perfect tool to better organize these typical, not-particularly-ambitious apps, where Ember would be a pre-mature optimization.
And perhaps Ember is the perfect tool for sophisticated apps written by teams of developers.
Re: AngularJS versus Ember
#7Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
"Ember vs AngularJS: I Prefer Ember and Feel that I Have Compelling Reasons for That Preference" is a bit longer, though.
Re: AngularJS versus Ember
#8Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
I went back and forth on the title. I don't usually write sensational titles but for some reason decided to give it a try. I think it's a very good point and I doubt I'll do it again.
It could be worse. One fellow I know wanted to write about the benefits of significant whitespace, and thought it would be funny to call his essay "White Power." I doubt he'll try that again.
;-)
Re: AngularJS versus Ember
#9It's not even close for what purpose ? For example, there's a wide common case of simple apps hacked together by 1 or 2 developers, traditionally composed of jQuery spaghetti. Maybe Angular is a perfect tool to better organize these typical, not-particularly-ambitious apps, where Ember would be a pre-mature optimization. And perhaps Ember is the perfect tool for sophisticated apps written by teams of developers.
> It's not even close for what purpose?
As the article says at the end:
> Ultimately, I think you should examine your application’s goals. Do you want to build something that pushes the boundaries of what people expect from the web? Is your application going to be super simple, or do you want to add powerful features and maintain it well over time?
Re: AngularJS versus Ember
#10Coming from someone that has used neither framework, I like the write up w/ examples. However, I wasn't convinced that "it's not even close" so maybe a bad title choice.
Would it be on the top of HN if it had a more reasonable title? Is the audience just as complicit as the author in trending towards flamebait?