3 ms·
> Maybe I didn't look hard enough, but there's no obvious switch to "just turn off all the legacy stuff, thnx". There is. Break compatibility for it, and whate
by vkou 7mo ago
> Maybe I didn't look hard enough, but there's no obvious switch to "just turn off all the legacy stuff, thnx".
There is. Break compatibility for it, and whatever poor bastard that is still maintaining software that is targeting a PalmPilot is free to either pin to an older version of your library, or fork it. Yes, that's a lot of pain for him, but it makes life a little easier for everyone else.
- Slothrop99 7mo ago[dead]
- josephg 7mo agoThis is my philosophy too. If the nodejs project doesn't support node 18, why on earth should I? Here's the schedule, if anyone hasn't seen it. Node 18 is EOL. Node 20 goes EOL in a bit over a month. https://nodejs.org/en/about/previous-releases https://nodejs.org/en/about/previous-releases