It’s a very C++ thing that the language developers saw the clusterfuck that is stream flushing on the kernel and decided that the right course of action was to create another fucking layer of hidden inconsistent flushing.
programmers manage to do stupid shit in every language. i was wondering if there was a way to stop them, and golang comes close but maybe proves it can’t be done. idk!
No debate, std::endl can be a disaster on some platforms due to flushing crap all the time.
It’s a very C++ thing that the language developers saw the clusterfuck that is stream flushing on the kernel and decided that the right course of action was to create another fucking layer of hidden inconsistent flushing.
I hear C++ was greatly inspired by the fifth circle of hell.
programmers manage to do stupid shit in every language. i was wondering if there was a way to stop them, and golang comes close but maybe proves it can’t be done. idk!
Just because the box says something is flushable doesn’t mean you should flush it.
Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.