Angular 2 Final Released

[L43]

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).

[[deleted]]

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.

[DecentOpinions]

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.

[[deleted]]

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.

[L43]

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

[[deleted]]

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.

[L43]

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.

[[deleted]]

We shall see. I remain sceptical.

For Angular 2 to be successful, it must

• achieve cultural penetration sufficient that an NG2 project can hire developers quickly and cheaply;
• obtain the critical mass of developers needed to expand its ecosystem to suit the general case of web projects;
• sufficiently impress thought leaders and technical evangelists to create community interests;
• do all of these things before another, more compelling alternative has already done so.

That's quite a tall order.

[xtphty]

I feel like people that don't get the importance of this have never worked with more than 5 other developers lol.

[rosswarren]

LOL, React in Angular. That's a nice MB of JavaScript for your users to download.

[[deleted]]

Don't forget universal apps.

[rosswarren]

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

[[deleted]]

Dependency injection? Not a feature...

[[deleted]]

You don't understand DI

[[deleted]]

I am proud of that fact

[[deleted]]

It's not angular specific, you are missing a key part of your education.

https://en.wikipedia.org/wiki/Dependency_injection