letsgo

Sounds like it's not just me that goes "ok then, try arguing with this" when power cycling an unresponsive computer.

It's completely valid but needs careful use because it can be destructive. Unrestrained anger is way too common and a huge problem for everyone around those afflicted with it.

Not everyone is immune to swearing; I don't see any point in causing unnecessary offence; and they contribute nothing to the meaning, except perhaps voicing a level of emotion which can be better expressed in other ways.

Old man yells at Swift: wait, are we talking about Trump or Putin here?

Toyota Cymru

I have a friend who thinks LOL means "lots of love" and uses it as a generic signoff.

Had to reread it several times when he wrote "Mother in law died yesterday LOL".

That's bonkers, St Paul repeatedly talks about how circumcision isn't a thing Christians need to do, even rebuking those who said it was: Gal 5:12.

https://www.biblegateway.com/quicksearch/?quicksearch=circumcision&version=NIV

especially 1 Cor 7:19 "Circumcision is nothing and uncircumcision is nothing. Keeping God’s commands is what counts."

If capitalisation is used to indicate the start of words then it could make sense for a webserver to serve ExpertsExchange and ExpertSexChange. But yeah having 16 possible versions of "main" would be horrendous.

Must be the updated version of ~~~~####3$3$$%^^~~~! NO CARRIER

I'm British and I only eat beans and curry, so I can't see any problem here.

Also misspelt "even", and ended a sentence with a preposition.

Lower performance though. At each iteration through the string you need to compare the length with a counter, which if you want strings longer than 255 characters will have to be multibyte. With NTS you don't need the counter or the multibyte comparison, strings can be indefinitely long, and you only need to check if the byte you just looked at is zero, which most CPUs do for free so you just use a branch-if-[not-]zero instruction.

The terminating null also gives you a fairly obvious visual clue where the end of the string is when you're debugging with a memory dump. Can you tell where the end of this string is: "ABCDEFGH"? What about now: "ABCD\0EFGH"?