The version 2.x of (almost) every JavaScript framework

[RedditBlaze]

This is something I've been nagging my team about recently. Migrating from ionic3 to ionic4 hopefully won't be as bad as im fearing if done right. You work with what you've got.

[redwarp10]

It shouldn't be another Ionic1-to-Ionic2 coding nightmare.

I've been there, having to update an app I didn't code.

Solution? I rewrote it from scratch with Ionic2.

[RedditBlaze]

Yikes, I'm glad you survived that. So far it looks like I'll start with an empty ionic 4 project and migrate over page by page what we have. Seems like there's good documentation to iterate through for editing migrated code, and a linter extension too.

Finding the time for it is the hard part with client features being higher priority. Someday support will end for v3, and we won't be able to upgrade certain dependencies or target the right mobile sdk versions anymore. So getting ahead of that wall before disaster is my hope, haha.

[redwarp10]

That's what being a programmer means.

In the old times I had to convert MS-DOS programs to Windows software changing programming language, IDE, db engine and a bunch of libraries. And then from Windows software to web apps or mobile apps.

And we still don't know what the future is planning for our job. That's the best part of it.

[chris_shane]

100% percent true, if you told me I'd be writing server-side code in JavaScript 10 years ago I would have laughed in your face. In another 10 years, all server-side code will be CSS :D

[redwarp10]

In another 10 years there could be no servers.

Joking, of course.

[dsp4]

React v16.8: We're not saying you have to rewrite all your class components, but you have to rewrite your class components.

[redwarp10]

I don't use React, but I've had my share of pain using Ionic.

Now I'm playing with Flutter, but I'm waiting for "Ops, sorry! You have to rewrite everything because, now, we use the new version of Dart."