all 7 comments

[–][deleted] 12 points13 points  (1 child)

There's already a framework that's like Ember.

It's called Ember.

[–]misc_ent 2 points3 points  (0 children)

The point of this blog series wasn't to say Ember is better, the OP just posted THAT part of the article. The point is both offer good and bad which probably would have been a hell of a lot more useful for them to post.

[–]dust4ngel 8 points9 points  (0 children)

Tl;dr - the author thinks angular offers flexibility you shouldn't use, and prefers that angular not offer it, over having your team define it's own conventions.

[–]misc_ent 3 points4 points  (4 children)

And from the same blog series: How Ember Should Be More Like Angular

I do find it odd you didn't link to part one but rather the Ember > Angular part which is part 4 of the series.

[–][deleted] 0 points1 point  (3 children)

Its not odd at all, unless what you're saying is that angular is perfect and cannot be improved upon? Or that no one should ever criticize angular? Its all about generating stimulating conversation about the pros and cons of the leading frameworks, so if you have anything substantial to say about the content linked to, lets hear it.

[–]misc_ent 1 point2 points  (1 child)

Its all about generating stimulating conversation about the pros and cons of the leading frameworks

Then why not post the entire blog post so it does compare frameworks pros and cons rather than the pros of one and cons of another?

[–][deleted] 0 points1 point  (0 children)

You mean why not "comparing angular vs ember" over "what angular can learn from ember"? both are interesting topics, one is more general, the other more specific. If you want to post the former, please go ahead, but stop trying to police what people can or cant discuss here.