Re:Bringing Forward the End-of-Life Date for Node.js 16
by solardev on Saturday June 11, 2022 @03:00PM
(#31707162)
> 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
Re:Bringing Forward the End-of-Life Date for Node.js 16
by ostenning on Saturday June 11, 2022 @03:06PM
(#31707230)
> 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
Re:Bringing Forward the End-of-Life Date for Node.js 16
by cersa8 on Sunday June 12, 2022 @03:21AM
(#31712358)
I've yet to experience a painful Node.js update. Backwards compatibility has been very good.
Re:Bringing Forward the End-of-Life Date for Node.js 16
by 8n4vidtmkvmk on Saturday June 11, 2022 @09:42PM
(#31710441)
are 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
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.