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

65

u/Attila226 Sep 15 '16

I hate to say it as any early adopter of Angular, but I don't think it matters anymore. Most of the cutting edge devs that I know moved on to React.

16

u/leeharris100 Sep 15 '16

Angular 2 is awesome in a different way. It's a package that contains a lot more and it's targeted at large scale SPAs. React is just a view library that anyone can pick up for any sized project.

Angular 2 will never be able to compete with the popularity of React in the same way that Laravel will never be able to compete with Wordpress. React fits into many situations but Angular 2 is great for certain projects.

26

u/Mael5trom Sep 15 '16

Angular2 isn't targeted at the "cutting edge devs". It is designed for the every day dev. That is a big difference.

13

u/[deleted] Sep 15 '16

LOL, angular 2 combined with its laundry list of other recommended technologies isn't exactly aimed at every day development.

5

u/[deleted] Sep 15 '16

Babel, transpiling alternate syntaxes and powerful frameworks/libraries (ie React and Angular) are pretty standard now I think.

→ More replies (1)
→ More replies (10)

4

u/yesman_85 Sep 15 '16

Most yeah, but definitely not all. We are still full on Angular, I personally didn't like React at all.

5

u/L43 Sep 15 '16

Maybe they will move on to Angular 2 now?

3

u/jibbit Sep 15 '16

I for one can't wait to convert my app that i just finished converting from jquery >angular1 > meteor > react to angular 2

4

u/L43 Sep 15 '16

Haven't you moved to Inferno yet?

→ More replies (1)

0

u/[deleted] Sep 15 '16

[deleted]

0

u/[deleted] Sep 15 '16

[deleted]

0

u/[deleted] Sep 15 '16

[deleted]

21

u/L43 Sep 15 '16

But it is easier if they all come in one big package, with one 'recommended' way to handle it all. There are two ends of the spectrum that each library/framework aims at - hyper customisability for React and ease of development for Angular 2. I can see people who don't want to shop around for a form validator, etc. etc. happily moving to Angular 2 (and even those who would shop around, if it turns out to be the best design - yet to be seen).

15

u/[deleted] Sep 15 '16 edited Sep 15 '16

Or they could just pick up the industry defaults for React projects - Redux for state management and react-router for, uh, routing. This is what is already happening.

Besides, you miss a larger point. There's only sense submitting to the yoke of a framework's "opinionated defaults" if those defaults are actually good. From what we've seen of the release candidate, NG2's... aren't.

19

u/DecentOpinions Sep 15 '16

Or they could just pick up the industry defaults for React projects - Redux for state management and react-router for, uh, routing.

As an outsider who hasn't used React at all yet, it seems hard to keep up with that. It's hard enough to keep on top of everything else we have to deal with already—build tools (Gulp, Grunt, Webpack etc.), test frameworks, CSS preprocessors (SASS, LESS, Stylus, PostCSS) and so on without the added complexity of keeping up to date on the latest React router/state manager etc.

4

u/[deleted] Sep 15 '16

latest React router/state manager etc.

These things really haven't changed much over the last twelve months. There are lots of opinionated starter kits, too.

6

u/L43 Sep 15 '16

Sure, that's true. But my point is that React isn't marketed as a framework, whereas Angular 2 is.

11

u/[deleted] Sep 15 '16

But so what? NG2 offers me a 'swiss army knife', in much the same way as NG1 did. The difference is, though, that back in 2013 Angular's competitors sucked. You had Backbone, Ember, Knockout and, what, KendoUI? Now I have Aurelia, Vue, Meteor, React/Redux, Mithril, CycleJS and even Angular 1 itself is still a viable choice.

The market is so much more crowded now, and Angular 2 needs to offer a compelling value proposition to differentiate itself. In the last eighteen months the project has simply failed to do that.

3

u/L43 Sep 15 '16 edited Sep 15 '16

They all have their goods and bads. Just don't use it if you don't like it, and let the community decide.

All I would say is if Google starts widely adopting it (which they already have in e.g. some parts of App Engine even though it was still in beta) people will flock to it.

→ More replies (0)
→ More replies (1)
→ More replies (3)

7

u/[deleted] Sep 15 '16

Don't forget universal apps.

2

u/rosswarren Sep 15 '16

ES6 modules or CommonJS modules are a form of dependency injection already. You don't need another.

→ More replies (5)
→ More replies (5)

1

u/kovensky Sep 15 '16

That would imply also moving everything else they use besides React to RxJs / Angular too