3 ms·
There are so many large scale C++ projects that prove Linus wrong every day. One of them, you probably use it every day. hint: it's a search engine. Whatever l
by shin_lao 16y ago
There are so many large scale C++ projects that prove Linus wrong every day. One of them, you probably use it every day. hint: it's a search engine.
Whatever language you use, you need rigor and diligence. You need to manage the project and follow up on developers.
You need to agree on a subset of the language, that will become your local dialect. I'm pretty sure that Linus doesn't accept "any C source code".
C++ has got more features than C. That's neither intrinsically good or bad.
I could argue about the merits of templates and what they enable you to do, and someone would tell me "it's hard to understand".
Well, any language you don't know is "hard to understand". C++ is not "C with classes" anymore. It's something else. It's a different language.
In the end what really matters is the quality of the developers and the quality of your process. The language is just how you implement your concepts.
- kensan 16y agoI would inject into your list of what really matters something Linus said: communication. Having each member of the team (1000 contributors to the kernel by Linus's estimation) in a different corner of the world is a huge consideration.
- eps 16y agoMain problem with C++ is non-technical. Based on some experience interviewing a dozen people a week for several months, C++ programmers tend to routinely overestimate their proficiency with the language, while C programers tend to have the opposite self-assessment. To put it differently - on average C++ devs are cocky, eveyone is a guru and C devs are basically modest.
- shin_lao 16y agoI agree with you. I often interview people who consider themselves "C++ expert" but struggle to use the STL's algorithms correctly.