Same

No, I think it’s everywhere.

Ok that’s a fair point I had overlooked. Thanks for explaining.

Mhh today I learned. That’s wild. I would have thought that any sane person would allow only 7-bit ASCII for the source code, and forward-compatible character sets in strings (every standard iteration being allowed to add characters, but not remove them).

Nah, I would absolutely want my compiler to error out hard on characters that are not allowed per the standard.

Shit - the next five weeks I’ll read C++ lines in upspeak in my head :(

Corporate needs you to find…

Your friends are the reason why we can’t have nice things in gaming. Literally blinded by blingbling

As someone who drives manuals - a what for the high-beams?

Mumble does the same for voice chats

Oh how I hated it when I experienced the snap shenanigan firsthand.

find . -iname “searchword”

You are arguing against a strawman. Never have I said in this whole thread debuggers were useless. I made a point to say they are absolutely not essential, and for multithreading issues they can be detrimental.

Would that really be worse? Considering they are using an fucking image-to-text-converter… I don’t think it would. Also, regular expressions rule :) just not in this context.

if anything, the code examples confirmed my belief that most python coders are fucking morons.

Not OC but: I won’t always read an article when the post title is a perfectly valid question. Software can be “done”, but typically the environment in which it runs evolves, so at some point a patch might be needed.

İmportant distinction: TeX is considered “perfect software” IIRC while LaTeX has evolved over time (or was still evolving when I last used it in the 2000s)

Saying it is not essential and saying it is generally useless are two very different things.

Most concurrency problems disappear at the pace of a debugger.

And I believe you are very wrong in that belief. However, a reliable statistic is not the first search result that I can find, so we’ll have to disregard the disagreement on that point. You lost me at your C# multithreading reasoning though. A debugger will always interfere with the processes you are looking at, hence making debugging of multithreading-related errors a game of whack-a-mole.