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

30

u/[deleted] Sep 15 '16

People saying it's too late and that they moved one, I think you are exaggerating.

Nothing stays static in our industry. It seems like we as developers are always looking for something new. Remember that React is already 3 years old, and Angular 1 peaked popularity when it was 3-4 years old.

I think that given time, we will see Angular 2 takes the stage, especially in large organizations that benefit TS and the completeness (opinionated) of NG2.

Anyways, I love the fact that NG2 is built with ES6,7 and TS in mind, while React was only modified to work with it.

13

u/[deleted] Sep 15 '16

Angular 1 had lots and lots of very obvious issues and suffered from a muddled design in general. It stayed relevant because there was nothing else out there to do what it could.

Angular 2 has to go up against React, it won't take the stage by default just because the latter has made it through a couple of years. React is not muddled, it knows exactly what it wants to do and how. What exactly are the issues that React has and Angular 2 can solve?

12

u/[deleted] Sep 15 '16

Opinionated complete framework, against a library.

If you specialize in NG2, you know state handling, ui rendering, routing, resource handling, universal apps.

For react, you need to learn each of these independently, while updating on the current trends (no state handling -> flux -> reflux -> redux).

8

u/[deleted] Sep 15 '16

I like Reacts gradual approach for that very reason but might be just me. With React it's not about a ton of technology you have to swallow come what will, it's more about understanding concepts first. Functional design, immutable data, what is state and how it flows. Once understood there's nothing to learn, no API to browse. You naturally write your app using the additions you need.

1

u/[deleted] Sep 15 '16

What exactly are the issues that Angular 2 can solve, but not Vue.js, Meteor, Mithril, Riot, a React boilerplate or Aurelia?

8

u/vinnl Sep 15 '16

Angular 2 will definitely be widely adopted. There's no way it's going to be a dominant as 1 was, though.

5

u/ergo14 Sep 15 '16

I saw lots of folks moved to other solutions like Polymer or Aurelia. I will pick up angular 2.x for some project just for fun.

6

u/rk06 Sep 15 '16

Imo, if those large enterprises do actual research on angular2's features and track record(like router crisis and breaking changes in RC), they will stay away from angular2.

Though most folks choose angular because it is backed by google, so i am certain that angular2 will see adoption. But it will not reach the levels of angular 1

13

u/[deleted] Sep 15 '16

Are you talking about a crisis that was during the development stages of NG2?

7

u/rk06 Sep 15 '16

"router crisis" refers to the complete re-(re-)*write of router after RC1 was released

*maybe there was one more rewrite. But i had stopped counting at that point.

7

u/halfTheFn Sep 15 '16

The router crises that affected even Angular 1. One day, we have a Component router that says, “Start using this one instead of old ng-route, it will ease the transition!” Weeks later: “this implementation of the Component Router (ngComponentRouter module) has been deprecated and will not receive further updates.” https://docs.angularjs.org/guide/component-router

8

u/L43 Sep 15 '16

Give it a year of stable APIs and everything will be forgotten. If the APIs remain stable...

8

u/leeharris100 Sep 15 '16

Router crisis? Jesus people on this sub are so dramatic. I mean seriously... It was in development. Anything can change.

5

u/Mael5trom Sep 15 '16

Those breaking changes were specifically because Angular2 wasn't done. Google is moving to semver now, so that shouldn't be an issue going forward. It definitely isn't a "reason not to use it".

2

u/rk06 Sep 15 '16 edited Sep 15 '16

Logically speaking as angular team has said that they will follow semver, you are definitely correct.

But practically speaking: once bitten, twice shy.

2

u/[deleted] Sep 15 '16

what were you bitten by? An open dev process? Would you rather they did everything behind closed doors and only presented the final result?

1

u/[deleted] Sep 15 '16

If the release candidate is not a release candidate, do not call it a release candidate.

If you are unwilling to do that, then I would prefer you work privately, yes.

1

u/[deleted] Sep 15 '16

NG 1 and 2 run side by side very happily. A few changes to your routes and you're good to go. People are still stuck on that first intro video where Google said it wasn't backwards compatible. That doesn't matter, both run. Leave old code alone, move new code forward.

The track record is actually really good, and well thought out.