CppCon
2 HN recommenders · recommended in 10 months, 2017–2025
1:36:27 · 175K views · Sep 24, 2016
Dan Saks's CppCon 2016 talk on why C programmers resist C++ and how to talk to them about it. He argues that persuasion rarely works by arguing and examines the culture gap between the two communities.
Recommended in C versus C++ and embedded threads as the expert view on adoption and persuasion.
11 comments from Hacker News
The mentioned cppcon presentation by Dan Saks is awesome. Highly recommend watching even if you are not interested in C or C++ : this video
So, I will let one of the renowned experts speak instead. CppCon 2016: Dan Saks “extern c: Talking to C Programmers about C++” this video Embedded Development with Dan Saks [LINK] Regarding Java vs C++, yes the enterprise world has adopted Java, however as someone doing consulting across Java, .NET and C++, I am really seeing it coming back since ANSI C++ has picked up steam again. I see it in projects related to IoT, AI, VR, big data,.... They are all polyglot projects with C++ plus something else, not C plus something else.
I mean the embedded systems where Assembly and C89 still rule, and there is very hard to change, because the problem of adopting anything else is cultural. Basically, while there are projects being done in C++, and many companies are finally migrating from C to C++, the large majority is sticking with C. If you prefer to listen to someone actually relevant in the C++ embedded community, here is what Dan Saks has to say about it. this video [LINK]
according to dan saks, who apparently to some people is famous c++ is faster than c (well in the test setup he describes below) [LINK] Language Design Implementation Relative Performance either any inline 1 (fastest) C++ polystate non-inline 1.56 x fastest C++ bundled non-inline 1.65 x fastest C polystate non-inline 1.70 x fastest C bundled non-inline 1.79 x fastest C++ unbundled non-inline 1.82 x fastest C unbundled non-inline 1.95 x fastest He furthermore argued that the biggest mistakes C++ developers did to kill the adoption of C++ for C programmers was to diverge from the previous line of "C++ is a better C" to "if you're using C++ as a better C you're doing it wrong" this video (I have no skin in the game, I was just curious to see if it's worth looking at rust for embedded when I came across that talk)
> But C++ still can't be used in many places that C is Unless we are speaking about PICs or similar old school 8 and 16 bit CPUs, with compilers like those from MIKROE, there is hardly a platform left were the vendor compiler isn't C and C++ (even if it doesn't go beyond C++11). And if it must be deployed as freestanding, there are still enough improvements to take advantage of. In the end it boils down to human factor in most cases, however as Dan Saks puts "If you're arguing, you're losing.", taken from CppCon 2016: “extern c: Talking to C Programmers about C++” this video