3 ms·
For me it's exactly the other way around. Spent 20 years in C++ (before that 5 years of C), but slowly and steady got fed up by the language complexity, redunda
by flohofwoe 8y ago
For me it's exactly the other way around. Spent 20 years in C++ (before that 5 years of C), but slowly and steady got fed up by the language complexity, redundant features, standard library bloat and compiles times. Went back to C and it's like a breath of fresh air.
The turning point for me was realizing that C++ mostly helps with managing the complexity of many small memory allocations, but it's better to avoid such a "many small memory allocations" scenario to begin with. And without that, C++ looses much of its appeal over C.
- AstralStorm 8y agoIf you're not using the type safety and error handling afforded by C++ you're probably not using C++11. (reminder: latest version is C++17 which brings much higher usability at compiler implementation complexity cost) Where C++ in modern form helps is generally getting rid of unsafe accesses and uses. I'll take exceptions over checking error codes all the time.
- Ace17 8y agoDon't you miss virtual functions? I found that no matter how you did it, implementing polymorphism in C (with function pointers) is tedious and verbose ; also, it discourages the creation of new interfaces (too much boilerplate).
- flohofwoe 8y agoNo, I don't use virtual methods (or inheritance, or runtime polymorphism) in C++ that much either.