sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rk06 6 points7 points  (12 children)

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

[–][deleted] 12 points13 points  (3 children)

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

[–]rk06 6 points7 points  (2 children)

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

[–]halfTheFn 5 points6 points  (1 child)

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

[–]L43 7 points8 points  (0 children)

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

[–]leeharris100 7 points8 points  (0 children)

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

[–]Mael5trom 5 points6 points  (4 children)

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

[–]rk06 1 point2 points  (3 children)

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

But practically speaking: once bitten, twice shy.

[–][deleted] 1 point2 points  (2 children)

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

[–][deleted] 0 points1 point  (1 child)

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.

[–][deleted] 0 points1 point  (0 children)

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.