alt Hacker NewsNot sure why JS is the problem though. You can use JS in small doses to drastically improve the user experience on websites. The fact that heavy frameworks are sometimes used in contexts where they are overkill is not strictly JS' fault. By that logic you would also need to go down the rabbit hole of what compilers produce efficient programs on the server side and ban everything else.
I think the tools we have nowadays are perfectly fine. It's a matter of how they are used. And I am pretty sure efficiency is not what companies think of when they launch a product.
Languages, language tools, language communities and language reputations are kinda inseparable.
You can write Java without using incredibly huge class, function, and variable names. You don't have to apply complex design patterns everywhere, or use a complicated framework you barely understand. You don't have to write code that produces 50-line stack traces. I don't have to import a dozen dependencies each with a dozen dependencies of their own, creating an endless security update treadmill. You don't have to write code that needs a gigabyte of RAM for the smallest microservice. Problems like long garbage collection pauses can be solved.
But if I take a job writing Java software? Probably I'm going to be handed a codebase written the way most Java developers write Java code. And I'd better make peace with that, or find a different job.