4 ms·

Nice! Angular is described by its creator as a better browser. That's why it gets so much heat. Because you actually have to hook into a app lifecycle you dont

by aikah 12y ago

Nice! Angular is described by its creator as a better browser. That's why it gets so much heat. Because you actually have to hook into a app lifecycle you dont control. And you know what ? that's great,because it means there is only one way to skin a cat and when you have to work with a huge team,it's time saving as there is no architectural debate. That's frankly why I like big and opinionated frameworks such as Angular. It's basically the framework's way or the highway,code becomes predictable and you only need to know how the frameworks works to understand other's people code. You know there will be no DOM manipulation in controllers. You know that the view layer will communicate with other layers through services.You know that developpers will have to use promises. And you know you'll be forced to write testable code that makes heavy use of dependency injection.

ninkendo 12y ago
I'd agree with you but then I realize I just got done pruning pure dom-manipulating jQuery code out of a colleague's angular directive today. Honestly I wish angular were more opinionated.
jbigelow76 12y ago
>That's frankly why I like big and opinionated frameworks such as Angular. That's weird that you say that Angular is opinionated, or maybe it's not. When I first started hearing about Angular, the story was that Angular was very opinionated compared to Backbone which made you figure everything out on your own. Then as Ember gelled Angular became the un-opinionated framework that left the developers to their own devices compared to the very opinionated "Ember way". I guess every framework is what you want it to be, or what you don't.
- junto 12y ago
  Ember makes strong opinions about the backend webservices as well as the front end. I don't think Angular does that.
  - regularjack 12y ago
    Ember Data is opinionated about the backend, Ember itself isn't. You can use Ember without Ember Data, as is the case with Discourse, one of the largest Ember apps out there. http://eviltrout.com/2013/03/23/ember-without-data.html http://eviltrout.com/2013/03/23/ember-without-data.html
hippich 12y ago
It probably depends on how far you try to get from angular in angular-based project. As soon as you try to do something differently - it might bite you and bite you badly. As for promises - try to define custom parser or formatter on ngModelController using anything asynchronous :) And yes, you are right - it might be easy to understand other's angular code for you, but when javascript developer come into angular project, try to explain why utility library called 'Service' and why DI does not take care of loading these dependencies :)

by aikah 12y ago

ninkendo 12y ago

I'd agree with you but then I realize I just got done pruning pure dom-manipulating jQuery code out of a colleague's angular directive today. Honestly I wish angular were more opinionated.

jbigelow76 12y ago

>That's frankly why I like big and opinionated frameworks such as Angular. That's weird that you say that Angular is opinionated, or maybe it's not. When I first started hearing about Angular, the story was that Angular was very opinionated compared to Backbone which made you figure everything out on your own. Then as Ember gelled Angular became the un-opinionated framework that left the developers to their own devices compared to the very opinionated "Ember way". I guess every framework is what you want it to be, or what you don't.

junto 12y ago
Ember makes strong opinions about the backend webservices as well as the front end. I don't think Angular does that.
- regularjack 12y ago
  Ember Data is opinionated about the backend, Ember itself isn't. You can use Ember without Ember Data, as is the case with Discourse, one of the largest Ember apps out there. http://eviltrout.com/2013/03/23/ember-without-data.html http://eviltrout.com/2013/03/23/ember-without-data.html

hippich 12y ago

It probably depends on how far you try to get from angular in angular-based project. As soon as you try to do something differently - it might bite you and bite you badly. As for promises - try to define custom parser or formatter on ngModelController using anything asynchronous :) And yes, you are right - it might be easy to understand other's angular code for you, but when javascript developer come into angular project, try to explain why utility library called 'Service' and why DI does not take care of loading these dependencies :)