> Has it occured to you you might simply not understand the advantages of this approach?
> Putting aside how useful it is to only have one language to learn in a stack...
Glad we are not talking about this - I'd have to point out that "I do not have to learn/understand" is a bad continuation when one starts with the claim the other was ignorant.
Decreasing stack complexity is a noble goal, regardless of how familiar you are with the stack as a whole. If a project used both cmake and autoreconf, you'd probably be the first one to call for a rewrite of one to the other (or both to your favourite third).
It decreases onboarding time, simplifies hiring, and reduces cognitive load when you yourself have to work with it.
If you want to decrease complexity the first thing to go would be the modern front end stack with it's own build tools, package managers, run times, servers and languages.
> Putting aside how useful it is to only have one language to learn in a stack...
Glad we are not talking about this - I'd have to point out that "I do not have to learn/understand" is a bad continuation when one starts with the claim the other was ignorant.