Isn't this mostly self-inflicted, though. The 2010 way works just as well today. * npm as a tool, sorry, it sucks. You got to replace all other languages with

Isn't this mostly self-inflicted, though. The 2010 way works just as well today. * npm as a tool, sorry, it sucks. You got to replace all other languages with javascript, live with the consequences of that choice. * libraries/packages/... are easy to add but hard to maintain. Extremely fine-grained packages with no culture of long-term stability make this a lot worse. * I'd rather have git complain about a merge than spend time finding out which of file.html, file_old.html, file2.html file_new.html , ... are in use. Lucky you if only 1 file is the answer. * The whole 'programmers want to install tooling but the sysadmins wont let them' story goes back to at least the '80 ies. Devs on unix installed software in their home folder instead of letting responsible sysadmins install it system-wide (when the sysadmin has time and can be convinced it is usefull).