If I'm writing C++, I'm usually optimizing for portability over performance, in which case I would prefer std::endl as it would yield the best results regardless of platform; it also keeps the end-of-line character out of other strings, making code just a little cleaner.

\n is for when I'm done pretending that anything that isn't Unix-like is OK, or I'm counting the cycles of every branch instruction.

They aren't the same thing so the comparison is weird.

endl has a flush which is important when doing something like embedded work or RTOS development. If i was doing multiple lines they all were \n until the last line when i actually want to push the buffer.

Obviously depending on the tuning of the compiler's optimization multiple flushes could be reduced but the goal should always be to write as optimal as possible.

\n, because I ordered a newline, not a flush.

What the heck is endl???

#define endl "\n"

Environment.NewLine()

\r\n gang

os.linesep

Lol jk none of my stuff runs on Windows anyway

I'm on side \PHP_EOL

https://docs.oracle.com/javase/9/docs/api/java/lang/System.html#lineSeparator--

Java, of course.

Rebel side \0

Environment.NewLine might exist in C#

\r\n

Well, Java has System.lineSeparator so, maybe no?

vbCrLf

Endl is faster to type