3 ms·
> For example angular 2 is not compatible with angular 1 That's not the problem, angular 1 and angular 2 are 2 completely different frameworks that share the n
by aikah 10y ago
> For example angular 2 is not compatible with angular 1
That's not the problem, angular 1 and angular 2 are 2 completely different frameworks that share the name and the team only. The team wanted to piggyback on the fame of the first version, but they share absolutely nothing conceptually. and contrary to what the Angular team says there is no "upgrade path", you need to learn the stuff from scratch once again.
The problem is, and the Angular team will find out very soon, "second systems" unless they provide huge advantages over the first version, are always a failure.
- prophesi 10y agoIt was quite the rough path when I converted an app from v1 to v2. First I had to get the app to work with Typescript (not necessary, but it seemed there'd be better docs/tutorials in Typescript with v2). Then gradually rewrite each piece of code using ng-upgrade as I relearned everything. But I still must say that v2 definitely provides the advantages to warrant the hassle.