Comment Re:reason why (Score 1) 26
Abso-fucking-lutely!
The JS ecosystem (and frankly the python ecosystem too) is made of lunatics who think I have nothing better to do than patch my system every 3 month because they decided that it was more pretty to swap the order to parameters somewhere.
The number of NPM packages that are deployed widely and that just break at an upgrade is staggering. And because fucking JS, you don't get a proper error message at the upgrade recompilation. You need to rely on having a test that catches the difference. What a fucking nightmare of an ecosystem.
I am currently the maintainer of a small project but we can't break production. We did our major upgrades in summer 2024. So we used the most up to date release, v22, that came out 3 month before. This was 18 month ago, and its EoL is in about a year. Who has the ability to commit the engineering time to upgrade every single one of your services every 3 years?
These are not minor changes, these are going to be different majors. So I do expect some feature break. The last update which was also within 3 years caused a forced upgrade of database driver and abstraction layer to a new major. And they decided to rewrite their entire fucking API.
I do not understand web people. How do they not go insane because of the horrible engineering decisions they keep on making in that field? You know what, the shitty Perl webservice I wrote in 2010, it still fucking works! And no one has touched it since.