Maybe firing half the tech workers was a bad idea. Maybe creating a reinforcement loop of enshittification or layoffs was a bad idea. Maybe making lines of code changed a key performance metric was a bad idea.
You get more left pads the more you cut the budget. Less time to think means more complicated software and pulling in deps you don’t need.
I can’t believe that saga happened, and still happens all the time with npm.
I want to like tools like uv/uvx but you download it for the mostly sane package manager and it installs the zero permission pull deps and execute tool for you.
Supply chain attacks are not new and very scary.
Maybe firing half the tech workers was a bad idea. Maybe creating a reinforcement loop of enshittification or layoffs was a bad idea. Maybe making lines of code changed a key performance metric was a bad idea.
most of these vulnerabilities were written more than a decade ago
Then again, maybe it was a good idea, if all they’re going to do is add a zillion left_pads from npm to the project.
You get more left pads the more you cut the budget. Less time to think means more complicated software and pulling in deps you don’t need.
I can’t believe that saga happened, and still happens all the time with npm.
I want to like tools like uv/uvx but you download it for the mostly sane package manager and it installs the zero permission pull deps and execute tool for you.