|
|
|
|
|
|
by otabdeveloper4
2112 days ago
|
|
|
> ...C++ committee's ignorance towards practical concerns such as debug build performance, error messages, build times... These practical concerns have no place in an ISO standard. Do you even know what the C++ committee's purpose is? |
|
|
Writing and selling more books.
All these are affected by evolution of the language. As the standards committee pushes more and more multi-layer templated library features as modern best practices, debug times suffer, error messages suffer, compile times suffer.
The C++ committee doesn't look at prior art in academic literature[0], they don't even consider many implementation concerns which only become apparent after implementations are widely used in real world. The gap between language designers and implementers is obvious.
There are C++ apologists who claim it is because of legacy. Yeah but I won't be buying those books every three years until they half-fix every misfeature in half broken template library way.