3 ms·

Not directly related but I would appreciate any thoughts on which angular version one should go with, for a new development (fairly large enterprise project) at

Not directly related but I would appreciate any thoughts on which angular version one should go with, for a new development (fairly large enterprise project) at this point of time. How hard would it be to upgrade to version 2.0 if we start our early development on v1.5, assuming 2.0 is not ready for prime time (or is it?)

Bahamut 10y ago
All depends on if you use any third party Angular 1 libraries. If you do, it can be trickier, as one will have to rewrite the functionality in Angular 2. For example, my current company screwed itself by using a fork of UI Grid, and thus probably cannot upgrade the current app to Angular 2 easily.
devuo 10y ago
It's going to take a massive amount of work to upgrade from 1.0 to 2.0. Don't do that to yourself. Just go with 2.0.
knicholes 10y ago
There's a way to bootstrap your angular 1 app with an upgrade module so that you can have both running at the same time. There are ways to upgrade/downgrade your services/components so that they can be used in either Angular 1 or 2. I know Angular2 is planning a release that breaks its forms API, so there may be more small breaks like that, so take that for what it's worth when deciding to use Angular 2 or Angular 1 (or both, once 2 stabilizes more for your enterprise app). It took me two hours to bootstrap my angular 1.5 app with the upgrade module, along with transpiling .ts files with my es6 JS. Be aware, though, that if you do use Typescript, your build system is going to change, and you're going to have to figure out how to use a module bundler (SystemJS or WebPack, probably). It may get pretty confusing if you're not used to transpilation, too. For example, when you want to instrument your code for code coverage for your unit tests, you need to map that instrumented code and its results to your typescript files and not the es5 transpiled version of your code to see which lines are failing/not being run/whatever. There are good plugins, but there's definitely some effort involved. People on my team are using Angular2 in their own projects and are claiming huge productivity gains. They love the relative simplicity and power.

Bahamut 10y ago

All depends on if you use any third party Angular 1 libraries. If you do, it can be trickier, as one will have to rewrite the functionality in Angular 2. For example, my current company screwed itself by using a fork of UI Grid, and thus probably cannot upgrade the current app to Angular 2 easily.

devuo 10y ago

It's going to take a massive amount of work to upgrade from 1.0 to 2.0. Don't do that to yourself. Just go with 2.0.

knicholes 10y ago

There's a way to bootstrap your angular 1 app with an upgrade module so that you can have both running at the same time. There are ways to upgrade/downgrade your services/components so that they can be used in either Angular 1 or 2. I know Angular2 is planning a release that breaks its forms API, so there may be more small breaks like that, so take that for what it's worth when deciding to use Angular 2 or Angular 1 (or both, once 2 stabilizes more for your enterprise app). It took me two hours to bootstrap my angular 1.5 app with the upgrade module, along with transpiling .ts files with my es6 JS. Be aware, though, that if you do use Typescript, your build system is going to change, and you're going to have to figure out how to use a module bundler (SystemJS or WebPack, probably). It may get pretty confusing if you're not used to transpilation, too. For example, when you want to instrument your code for code coverage for your unit tests, you need to map that instrumented code and its results to your typescript files and not the es5 transpiled version of your code to see which lines are failing/not being run/whatever. There are good plugins, but there's definitely some effort involved. People on my team are using Angular2 in their own projects and are claiming huge productivity gains. They love the relative simplicity and power.