3 ms·
Ah this old chestnut... Clearly the author believes in fighting flames with a flamethrower. Anyone could write the exact same arguments against this piece, just
by grogers 13y ago
Ah this old chestnut... Clearly the author believes in fighting flames with a flamethrower. Anyone could write the exact same arguments against this piece, just as he does against Linus. His arguments aren't well backed, and his tone is even more inflammatory than Linus...
Sad to say that a lot of people's bias against c++ is rooted in their experience with it 10-20 years ago. Poor compilers, poor stdlibs, poor portability, etc. If that is you, I would encourage you to check out what modern c++ is like. C++11 fixes a bunch of things, c++14 will fix some things that the committee missed. Yeah, c++ is big and complicated, but so is every language, even C. Yeah the C core language is small, but any large project starts either rolling their own library for data structures, algorithms, string processing, etc, or linking in behemoths like glib. C++ just comes with a lot of the basics included, and learning the best practices and modern idioms of using the language isn't that bad. Consider:
unique_ptr<foo> bar(); // c++
foo* bar(); // c.
The C++ version conveys way more information (and is almost impossible to screw up its use accidentally), without the need for comments, and compiles to the same code. This is just one example, but they abound.