r/javascript • • Sep 15 '16

Angular 2 Final Released

http://angularjs.blogspot.com/2016/09/angular2-final.html
358 Upvotes

190 comments sorted by

View all comments

31

u/mdboop Sep 15 '16 edited Sep 15 '16

And nobody cares. I doubt adoption rates will be significant, but who knows, I guess. It just seems like there are so many things going against it that will outweigh its merits. Embracing rxjs, awesome. Typescript, fantastic if you're into it. But people are sick of Angular 1.x for the most part, Angular2 took forever to be released (feels like the opportunity went stale a while ago), and it's still pretty damn complicated compared to React or Vue.

People talk about how JS frameworks change all the time and say React will likely not be around forever (I hear this from co-workers when I bring up why we should switch from Angular 1.x to React), but someone on my team brought up an excellent point: React is used to build FB's flagship product. It's literally everywhere in the site. But Angular? Nowhere to be seen in any Google product of note. To me, that speaks volumes (on top of it's other merits).

edit: and, of course, React will not be around forever. But I'd put my money on it over Angular2 any day. edit2: forgot a word

21

u/Shaper_pmp Sep 15 '16 edited Sep 15 '16

You also left out the most important point - Angular is a framework, and with any framework almost everything is done "their way or the highway" (or at least, their way or you're off in the weeds of unsupported/second-class-citizen workflows with limited support and documentation).

React is a library, and - like any other library - if necessary you can swap it in and out for alternatives without completely reengineering your entire application.

Frameworks are convenient but fundamentally limiting because they dictate the structure of your application, so you're always trying to express both the problem and the solution in terms of one specific tool. With a full toolbox you can hammer nails, screw in screws and spread glue as appropriate. With exactly one tool in your toolbox you either severely limit the kinds of projects you can undertake or you inevitably end up banging in screws sooner or later because that's all you can do.

Composing libraries together takes more effort, but gives you more flexibility, allows you to avoid lockin more easily, and allows you to express your solution in terms of the problem-space instead of coercing you into a "one size fits all" approach that never really quite does.

8

u/rk06 Sep 15 '16

In those cases, one can chose aurelia.

2

u/Channel6 Sep 15 '16

Shame this comment will be lost in the usual flood of react vs Ng, there really is an alternative...

0

u/[deleted] Sep 15 '16

[deleted]

1

u/FrozenOx Sep 15 '16

I find a lot of language/framework subs are dead on Reddit. Everyone serious about some dev language/framework/tool is on its Slack or Gitter channel now.