For me what killed C++ above all else is how incredibly 3rd-party-library hostile it has turned out to be.
The article covers a bunch of stumbling blocks that are external to the language, but there are at least as many in the language itself.
It wasn't deliberate of course, but a million little decisions and unadressed problems in the language ended up conspiring to create a miserable experience when assembling systems from libraries. This may not have been a very big problem 20 years ago - I suspect the current culture of many small libraries as building blocks didn't really exist then - but today it's a show stopper.
How about the way that the standard doesn't specify the linker's name mangling, so many linkers do it in mutually incompatible ways, meaning you can't use a library linked by one linker with a main program linked by another.
Comments
For me what killed C++ above all else is how incredibly 3rd-party-library hostile it has turned out to be.
The article covers a bunch of stumbling blocks that are external to the language, but there are at least as many in the language itself.
It wasn't deliberate of course, but a million little decisions and unadressed problems in the language ended up conspiring to create a miserable experience when assembling systems from libraries. This may not have been a very big problem 20 years ago - I suspect the current culture of many small libraries as building blocks didn't really exist then - but today it's a show stopper.
How about the way that the standard doesn't specify the linker's name mangling, so many linkers do it in mutually incompatible ways, meaning you can't use a library linked by one linker with a main program linked by another.