Re:Angular vs. React – the tie breaker
by karmajunkie on Thursday July 09, 2015 @10:34AM
(#9858028)
I'm stuck on an older version of angular, but have directives become more composable in the last couple of versions? I had real problems composing them as element directives, which is the only way i'd be able to swallow the equivalence argument.
[ Parent
| on HN ]
Yes they have, everything is gearing towards component-based architecture in the more recent versions of Angular, and 2.0 is going to be all about components. This is a good read - http://teropa.info/blog/2014/10/24/how-ive-improved-my-angul...
Which is funny because Google is also sponsoring Web Components (via Polymer), so I wouldn't be surprised if Angular is one grand experiment to see if the world will adopt data-bound web components as the next step in the evolution of the web.
Re:Angular vs. React – the tie breaker
by lucisferre on Thursday July 09, 2015 @11:26AM
(#9858378)
Sorry can you elaborate? How have they become more composable? I don't recall a point at least post 1.X where they were more or less useful for composition than they are now.
Sure, there are a lot of subtle things which have been improved in later Angular versions.
First of all, you don't need $scope anymore in controllers, you can still use it for functions like $watch, but you don't need to inject it in just to add properties to your controller, you can just use `this.foo = 'bar';`
You also have the controllerAs syntax which I don't think is present in earlier Angular versions, which provides a shorthand for your controller, and bindToController for directives, which allows you to bind attribute values directly to the directives controller without extra syntax.
If I remember other things I will update this comment.