Should do I upgrade my angularJS 1.0.8 project to 1.7.7, or create an hybrid app

[Vinícius Chab]

I work in a very small team, in big company (12k+ workers). We have an internal system widely used (pretty much everyone that works here). The system was built more than 6y ago, when AngularJS was THE tech to use.

We're in 2019, and AngularJS is pretty bad (compared to Angular 8). Upgrading was always an idea, but the system is integrated with groovy, and we have 400+ files that would need change. And that, of course, stopping the team a few weeks for this is definitely impossible (since the team is small, this upgrade would stay for only one person to do).

This discussion caused the app to stay... 6 years without updating (we're on angular 1.0.8). Now I'm facing two options here, either upgrading our AngularJS to 1.7.7 (kissing the devil), or making the app hybrid with Angular 8.

What option would be better?

Is it possible to create a hybrid app, even if we use (a lot of) groovy (.gsp and .groovy files)?

If not, or, if it's not worth it, how do I upgrade my version from 1.0.8 to 1.7.7?

[Tito]

Time to kiss Satan.
Hybrid is not worth imho.
Bite the bullet and rewrite in angular 8. One component at s time.
Time wasted in a hybrid Frankenstein could be used to learn and make a solid app

[Sander Elias]

Hi Vinicius,

Only do a hybrid app if the means is rewriting the full app to Angular. It is a temporary step. If there is a large change that large parts of the old application need to stay in use, don't go hybrid.

There are a few alternatives.

first, make an Angular app that wraps around the old app. (simply said, run your old app inside an iframe inside your new app, this way you can upgrade not only angular but also all 3rth parties)

second, use angular elements to add new portions to your old app. This works and is reasonably future save, but you have to keep all deps from the old app, aside off al the deps of the new app.

You can talk to me to find out more.

Regards

Sander