It probably seems like I wrote the above as a one-off shit post to bag on OP for the lulz. But I did have a solid engineering basis for writing it.
The tools being better or worse isn't the issue I was getting at. Quadlets may well be an improvement on several fronts. But every tool / dependency / service / etc increases the cognitive burden of a project. That is one more component to have to learn for people who interact with it. One more expansion of the overall system to keep in mind (if such a feat is still possible.) One more increase in complexity - and that's quite a bad thing because complexity is harder to maintain.
When you always chase the latest and greatest things. You may end up with a collection of shiny tools that specialize in everything just the way you want it. But push it too far and you end up with designs that are unrecognizable to anyone with the skills you need. OSes, package managers, scripting languages, DBs, dev-ops, and cloud infrastructure approaches that no one recognizes. And when people want to be productive they're not going to be impressed by the dazzling number of obscure technologies being used. It will seem more like a red flag than anything.
There's a nice contrast you can make between web technology and templeos. Terry Davis built this operating system called templeos and part of his goals for building the OS were to keep it within a certain number of lines - lets say 25k. That means the entire kernel, file system drivers, graphics, editor, terminal, and compiler -- all have to fit within 25k. In other words every line had to count. Terry Davis hated bloated software and wanted to write an OS that had low resource usage. So templeos runs in 32 bits -- specifically using 32 bit register operations because they're faster. He built an entire language from scratch and all the tooling to run it. Templeos can build its entire kernel inside itself using his tooling and it does so within seconds. His tools don't even have a linker.
Now Terry knew something many programmers today don't: it's that when you keep things simple, when you include only what you need, and design in the simplest way possible, you can actually achieve better results. Terrys code is fast, it builds instantly, it has a low memory foot print, and its easy to maintain. Compare it to the web today. A multitude of ways to build, pack, combine, distribute, minimize, respond, push, pull... The web was never meant to be rocket science but somehow trying to keep up with modern web development feels like getting teeth pulled. If terry had of built the web it would look shitty like windows 95 but pages would load instantly, use almost no data, wouldn't need 8 gb of RAM to run chrome, and probably would encourage regular users to write code.
Complexity, bad. Simple, good.