Early C compilers were not optimising compilers. The hardware was very limited.
Although I would agree it was possible to design the language much better to avoid Null, most buffer overflows etc.., C was not designed to be good from PL standpoint. It was designed to write something and then evolved.
Same for issues like diversity hiring and SJWs irritating well-running open source projects. I say this as a left leaning person. Politics and religion tend to divide people thus they have to be kept away, it won't harm anyone but self important non-technical idiots who think renaming master to main will change the life of oppressed people.
There is politics as in FSF / GNU and there is politics as in Mozilla. Lot of mozilla activism is not relevant to privacy / open web. Not to mention it also limits many people from donating to them.
Do you use an ad blocker like UBlock Origin? That speeds up web by significant margin. I also used that to disable JS by default and enable only when needed, works well for me.
I am tired of wasm hype. Can someone explain what it does so well than existing cross platform solutions like CLR / JVM? It doesn't yet have a GC nor is most efficient for that matter. And JIT is not efficient in terms of memory and power compared to native code.
It is because you want to hire inexpensive web developers to develop for desktop and get the check box ticked. Your average bootcamp webshit doesn't even know Big O notation. I don't expect them to be as productive as good developers either.
The web ecosystem is a big mess where trends change every month and working in web ecosystem requires looking up things a lot because no one bothers to master the thing. It doesn't help that many web developers don't have solid foundations.
This is a trap managers generally fall into. Cheap developers aren't equivalent to competent developers, and their incompetence will cost you more than what you save by hiring them instead of a competent developer.