2010/3/16 Marc Espie <es...@nerim.net>: > Of course, it makes it completely impossible to hack on KDE if you're in > the "C++ is crap, everything that matters should be written in C" mentality. > (in fact, KDE is probably the biggest example of readable C++ code I give > to people. Doesn't hurt that it follows on the steps of Qt, which is itself > awesome). > > So there. > > Even among OpenBSD porters, there are just a few of us who do grok enough C++ > to hack on kde or qt. That probably explains a lot. B The fact that it's > incredibly more efficient than that java crap won't stop newcomers from > learning java instead of C++, though. > >
clang+LLVM is barely able of bootstrapping itself while already generating highly optimized code for C and Objective-C for a long time. If compiler-crafting C++ wizards have such a hard time getting it right, what chance is there for "newcomers"? I prefer C programs because they don't depend on boost, libstdc++, g++ and company. If I remember correctly, groff(and maybe something else?) is directly responsible for a big portion of time spent when you build the base system. I like C++ dependencies more than "you need autotools > x.53 but < x.53.2" dependencies, though.
