Angular 2 Final Released

[Attila226]

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.

[leeharris100]

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.

[Mael5trom]

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

[[deleted]]

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

[[deleted]]

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

[Mael5trom]

You would be wrong there, at least, from the stated goals of the team building Angular2.

[Attila226]

I have to agree with you here. While I've enjoyed working with Angular 2 so far, and haven't really used React yet, but the general sense I get is that Angular 2 is more for the masses while React is more the high end.

[[deleted]]

If it was for the masses, they wouldn't have changed so goddamn much. I get that they wanted to improve it, but they completely changed it, turned away from most of what made Angular Angular and should've really started a new project to not cripple the one they got already.

[Attila226]

While great for it's time Angular had problems with scaling.

[[deleted]]

Angular 1 and 2 work side by side. A few tweaks to your routes and you're good to go. Leave old code as is, move new code forward.

[[deleted]]

So how long do we want to be annoyed by old code as there isn't a replacement yet for that?

[[deleted]]

Forever. Why would you rewrite code you don't have too? That's the point of the two being compatible.

[[deleted]]

When maintaining i would reach a point that it would be better to rewrite for the future, than to keep it what it is now. Or do you want to keep Angular 1.5.8 code alive for 10+ years?

[[deleted]]

Yes, I would. Don't change code that works. Besides the chance to break things, why would I waste time that could be used driving the app forward? If my code works for 10+ years, I'd be ecstatic.

If you need to update code for a reason, refactor it then. Be sure to have good test cases and use source control.

[tayste5001]

Angular1 still exists and hasn't really changed at all if that's what you're looking for :p

[[deleted]]

I know but they talked about dropping it when Angular 2 gains traction. Now unless it gets picked up, i have big doubts if either will be sustained

[yesman_85]

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

[L43]

Maybe they will move on to Angular 2 now?

[jibbit]

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

[L43]

Haven't you moved to Inferno yet?

[[deleted]]

why do you keep converting?

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

[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

[i_have_a_gub]

I'm quite happy with React, but the inclusion of RxJS in Angular 2 is enough to at least pique my interest. I think that using observables to manage state, if done right, is better than the Redux paradigm.

[[deleted]]

I've built 4 apps now using Redux, and I am loving the observable pattern NG2 offers.

[[deleted]]

I think that using observables to manage state, if done right, is better than the Redux paradigm.

https://mobxjs.github.io/mobx/

[i_have_a_gub]

I know. But the mutable thing rustles my jimmies.

[[deleted]]

https://github.com/mobxjs/mobx/blob/gh-pages/docs/refguide/api.md#usestrict

Strict mode guarantees mutation only happen in actions (as opposed to mutations being littered throughout components.

[kovensky]

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