[AngularJS] Re: Why moving from one version of Angular to another is so painful ? Is Angular a right choice for the client side development ?

2018-05-17 Thread Sander Elias
Hi sskini76, No, there is almost no re-work needed between version 2 and 6. There are some breaking changes, but those should be easy to fix, and have only low impact. And they occur only if you did some special stuff with injection-tokens. Some of the I18n stuff did change also. When you used

[AngularJS] Re: Why moving from one version of Angular to another is so painful ? Is Angular a right choice for the client side development ?

2018-05-17 Thread sskini76
Thanks for the response, does't it mean we have to re-work & re-test the application every time ? This is leading to over heads & increase in cost of the solution/project. Incase of fixed cost project, clients will not pay a single penny extra. On Tuesday, 15 May 2018 00:51:12 UTC+5:30, Tito

[AngularJS] Re: Why moving from one version of Angular to another is so painful ? Is Angular a right choice for the client side development ?

2018-05-14 Thread Sander Elias
Hi Skini, In an addendum to what Tito said, Between version 2 and version 4 were no breaking changes, and to version 5 only a few small ones. I upgraded a large number of projects to version 6 already and did run into anything major. Can you point out the things you were able to do, you can

[AngularJS] Re: Why moving from one version of Angular to another is so painful ? Is Angular a right choice for the client side development ?

2018-05-14 Thread Tito
this is not anything new with any framework. I think at some point you have to say I will go with v4.0 release it and then keep it that way until you see a benefit of moving to the next version. upgrade to the next version is not really required On Monday, May 14, 2018 at 12:07:56 PM UTC-7,