7 ms·
C++ for high-level code tends to be this way. Waste tons of focus on saving a couple of CPU cycles, but the whole thing is waiting on RPCs anyway. Also you pro
by harkinian 3y ago
C++ for high-level code tends to be this way. Waste tons of focus on saving a couple of CPU cycles, but the whole thing is waiting on RPCs anyway.
Also you probably used less efficient algorithms because the smarter ones were too annoying to implement in C++, and there's possibly a solid Python lib that does it with hyper optimized C code anyway.
- harkinian 3y agoOh and those measures that save 2 extra CPU cycles do things in a way more error-prone way, which some day causes memory corruption.
- harkinian 3y ago... which you spend more CPU cycles than you ever saved trying to debug it
- lpapez 3y agoYeah I agree. The language lives in a weird niche where both intricate low-level details are visible, but also supports abstractions only visible from outer space. You always have some low-level detail which can be nitpicked about, even though it does not matter in the slightest. Admittedly, choosing C++ for such a high-level project wasn't a good idea at all, but that is what the first few devs knew best and sticked with it.