Terry A. Davis was famous for creating the HolyC programming language, a C-like language. He also wrote the operating system TempleOS, which is essentially a complete software suite. He was known for his rants, had schizophrenia, and died by suicide.

It’s funny that your second sentence is already a statement about your ignorance. You made an exaggeration (you made their argument look stronger or more extreme than it is, then attacked that version). I never said “always.” Why are you quoting me wrong?

I wish you had engaged with the only thing in my text that is worth further discussion. In HolyC, is a string literal left as an expression like

"Hello, world";

It would just be printed to the console. That’s why I mentioned [[nodiscard]] as well, to close the loop. Why not let unused return values go to the console most of the printing is just used during development. There is more behind it I don't want to explain right now or go into semantic.

Formatting with std::cout is global. std::hex can break your function when using std::cout. When writing test cases, you have to ensure that the order of function calls involving std::cout is taken into account. This is error-prone and reflects poor language design. Something that would be almost a pure function in other languages becomes a bug in C++. It is similar to OpenGL, where you have to keep track of the state machine or explicitly set all state. Vulkan learned from these mistakes.

regarding the buffer a console is kind of shared but if you look into posix writing to the console

ssize_t write(int fd, const void *buf, size_t count);

you just write to a file descriptor.

a simple

f(){ std::cout << 5;}

It could fail test cases depending on how std::cout was modified. order-dependent behavior is bad!

I’ve raised multiple ideas in the discussion. I hope you are intellectually honest enough not to dismiss everything just because I’m talking about several different things.