3 ms·
It'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 jQ
by gkop 13y ago
It'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.
- steveklabnik 13y ago> 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?
- gkop 13y agoRead on > If you’re serious about front end development, I advise you to take the time to learn Ember properly. The article isn't fair to Angular. It's like saying, If you're a professional web designer, you should always use semantic markup and a CSS pre-processor, and never Twitter Bootstrap. In fact, Twitter Bootstrap and Angular both have their places alongside Sass and Ember.