> This is a common saying because it is a common occurrence.
Ha ha. This is not applicable for software, and I assume, for some craftsman.
What's the percentage of software developers that actually get to choose their tools? 40%? 60% at best? Though most likely it's just 20%.
Most projects are pre-existing, it's only natural. You can't create more projects than those already in existence, once a field matures a bit. Which means that you have to use what's already there.
Plenty of people are forced to use bad tools. And they can for sure blame them.
Your craft is your personal responsibility; you use your tools, they don't use you. So, your product is the result of what you do, not what your tools do. Limitations of your tools leave you with greater responsibility to ensure results that satisfy whatever standard you work to.
Blaming your tools for bad results tells people much more about you than about the tools.
We delude ourselves into thinking we're all Picassos when we're just house painters, at best.
These places also have all the resources as well.
This is a common saying because it is a common occurrence.
People who use the language effectively know all about the complaints. Those people live with their complaints knowing no other language even comes close to meeting their needs. No language on the horizon is even trying to meet their needs.
C++ usage is still growing by leaps and bounds. Attendance at ISO Standard meetings is soaring; until Covid19 killed f2f meetings, each had more than any meeting before; similarly, at conventions. Even the number of C++ conventions held grows every year, with new national ones arising all the time.
Rust is having a go at part of the problem space, and making some headway. But more people pick up C++ for the first time in any given week than the total who have ever tried Rust. It is still way too early to tell whether that will ever not be true.
So the HN trend is very much an echo-chamber phenomenon, with no analog in the wider world.