3 ms·
Continuing with the rest of your paragraph in your first link: There are many constructions that are ambiguous, there's no way to parse them and decide what th
by wglb 15y ago
Continuing with the rest of your paragraph in your first link:
There are many constructions that are ambiguous, there's no way to parse them and decide what they mean, that you can't trust the compiler to do. For example, you use the "less-than" and "greater-than" signs not only to mean less-than and greater-than but also in templates. There are lots of little things like this, and many things in the implementation, that you can't be sure the compiler will do anything reasonable with.
And he goes on to suppose what another CS practitioner might say:
DDJ: You've mentioned Edsgar Dijkstra. What do you think of his work?
DK: His great strength is that he is uncompromising. It would make him physically ill to think of programming in C++.
JWZ, who Peter Norvig called the best programmer that he ever worked with, offered a scathing analysis of C++ and its contribution to the failure of Netscape. (Coders at Work http://www.codersatwork.com/. http://www.codersatwork.com/.) In the same book, Ken Thompson offered a similarly negative view of the language and its genesis.
For some detailed issues, read all of http://yosefk.com/c++fqa/ http://yosefk.com/c++fqa/. Funny but not funny.
I say this as one who spent 10 years programming in C++. Those dirty corners that Knuth mentioned are different with every team practicing C++, resulting in a style guide that cordons off chunks of the language.
- pjmlp 15y agoDijkstra stopped using computers for work around 1972, and the last programming language he used was ALGOL, so his opinion about C++ most likely does not count. About JWZ, I would not say that someone that throws chairs around rooms, and dedicated part of his life to flame C++, has a thrusty opinion about it. Finally, Ken Thompson has stuck in C for so long, and even Go is just a better C, that I doubt he really understands the concepts behind the abstractions C++ offers. In the end it goes back to people using C++ without proper background. The world is complex and most languages that try to be the tool from low level systems programming up to normal business applications, end up being complex. Even if they start simple. Any modern language that tries to replace C++, will end up being as complex. PL/I, Ada, D, C#, Haskell, OCaml, Scala, Lisp are all examples of languages that have a kind of similar complexity level with C++, and also require people with proper CS background to handle them. Sometimes the complexity is the language itself, other times it is the abstractions it offers. Judging from the skill set I see in cheap labour in IT, even BASIC is too complex for many people. I am not on a crusade to defend C++, I also find that it has many warts and we need a better systems programming language, which is also able to offer the control and set of abstractions that C++ does. Now will it be D, Rust, Clay or something else? Until it happens, C++ will be the only answer for a class of problems.