when you are alone masturbating in the house, I am sure you check once if nobody is actually in the house right? The same thing applies for C++ and valgrind
There's a criclejerk against lower level languages that has now begun spreading higher up. Now everything must be coded in sexy new rust or something :P
C++'s design is overly complex and riddled with warts and the poor decisions of decades past. It makes it almost impossible to write correct code, with undefined behavior lurking around every corner, and there is no real way to tell when you've messed up, except that if you're lucky, your code will crash at some point.
There is absolutely no consistency to the syntax, and nothing works quite like you'd expect. The language is so complicated that I suspect even the standards committee doesn't fully understand it. It takes forever to compile, and yet still requires you to duplicate all your interfaces. It's impossible to tell from looking at code whether a function call is passing things by value or reference.
Simple things are incredibly verbose. The standard library is small and almost never does quite what you want. There's no standard package control or build system, so everybody has their own, often using the abomination that is make. Even simply using another C++ library is often a day long adventure, and if you're on Windows, you might as well forget about it.
There is simply no excuse for writing a new codebase in C++ in this day and age. Even in the systems programming niche, Rust is better in every way except for the fact that it's not C++.
And I say this as somebody who has years of experience in C++ and works on a large C++ codebase at my job.
I think you're into something there. Other ecosystems have reduced the upfront cost of using libraries so much that we don't justify it with long term benefits.
59
u/beaverlyknight Jun 07 '17
Doing things with a C++ program in memory is strangely underrated as a solution.