Comment Re:C++ is probably a little bit better (Score 1) 407
Well basically no. Given your statement:
So flame away, fanboys. I'm used to it. The truth hurts, and the more squealing I get, the more I know that I am saying the truth.
I don't expect this reply will get through to you or get meaningful a responses. Others might benefir so here goes:
Even with the standard libraries, there were rarely systems without a lot of custom storage code. By it's own claimed abilities for code reuse, C++ was a failure before C++11.
Well, depending on how you meant that, it's either wrong or a triumph of C++. I have used systems where there has been extensive use of custom containers. The main reason for that was it targeted android and android didn't really ship with C++. It shipped with a language looking much like C++ except with several key features and the standard library nuked. It's hardly C++'s fault for languages that are almost-but-not-quite C++ not being C++.
Other than that one, people mostly seem to make do with the standard containers for things they work for.
In my own code I also make use of two non STL containers, one for images and one for Linear Algebra (vectors and matrices). It's a triumph that these work and look and feel just like native or standard library things. They also don't use custom code: it's either C++ arrays for fixed In my own code I also make use of two non STL containers, one for images and one for
sized objects and backed by std::vector otherwise.
So now I'm going to make the same mistake again. If we take Stroustrup's publication of The C++ Programming Language in 1985 as the start of the ongoing C++ era, then it took over 25 years for the language to become somewhat OK.
No one will deny that C++11 was late. Hell it was meant to be C++0x. However, you're comparing one of the better languages today (C++14) with languages from 30 years ago which is disengenuous. It took C++ 25 years to become a good language relative to others 25 years from its inception. But it was good in the mean time compared to its contempories too.
I wouldn't want to use '98 era C++ now, but I wouldn't want to use Java 1.1, VB6, ancient javascript, bash 2.06 or a host of others now either.
In my estimation, C++ was never a good idea.
Well, the world more or less disagrees with you. It's the only language out there that provides high level abstractions and low runtime penalties. The only serious competitors have come around recently and aren't really production ready. What else scales as well?
Changing the internal workings of an object is very likely to propagate outside the object.
Not if you code worth a damn. Yes we all know objects are sized things and changing the object requires a recompile. However, my code compiles on LLVM, GCC and Visual Studio and ha at various times compiled on MIPS Pro and whatever that sun compiler was. I think someone got it to compile with STLPort on Android too back when that was a thing.
That's 6 complete, from scratch reimlementations of the same objects (the standard library). Yet despite those complete changes no fooling around was required in that regard.