3 ms·
I don't know why people are complaining that they should have done things differently. 15 months is sufficient to migrate any application to Node 17. But let's
by nindalf 4y ago
I don't know why people are complaining that they should have done things differently. 15 months is sufficient to migrate any application to Node 17.
But let's be real, everyone on Node 16 is going to forget about this and panic next August. Then it'll take a Herculean effort by a few heroes in each company to pull off the migration under a tight deadline of a few weeks.
- solardev 4y ago> 15 months is sufficient to migrate any application to Node 17. If you don't work in tech, it's hard to explain to the higher-ups why some big software upgrade that will result in no user-facing improvements needs to take months off your million-dollar product launch. Besides, given the turnover these days in both people and frameworks, you're lucky if you're even still on the same stack 15 months later, lol
- ostenning 4y ago> Besides, given the turnover these days in both people and frameworks, you're lucky if you're even still on the same stack 15 months later Its a sad reality of web development unfortunately
- 8n4vidtmkvmk 4y agoare node version upgrades a big pain? i haven't used it for anything enterprise level. only hit a few quirks here and there with some deps. i just drop back and wait for library maintainers to fix.... but i guess if you are that library maintainer it sucks
- cersa8 4y agoI've yet to experience a painful Node.js update. Backwards compatibility has been very good.