Yes yes, most people just happen to have a “friend” this happens to.

Does Chinese only have the one 1st person pronoun?

Well, a few niche topics are well/over represented. Linux & Communism are very niche in real life, at least in my experience, but quite well represented here.

Disclaimer: I’m learning Japanese & I don’t know Chinese.

It looks like the original character for the 3rf person pronoun is now the masculine pronoun & the female pronoun is made by substituting the person component (人, I don’t know how to type the left-component form) with the woman component (女).

Communism was previously provided by Marxism-Leninism, but it has been mostly unmaintained for a while, and was thus dropped from the latest Debian. Try the more actively developed Maoism fork.

You got the kernel from Debian’s official (read: central) repo, didn’t you? The decentralized mirrors exist for a reason, bootlicker!

my new laptop literally is more than double in each spec

13.6"

Where did you find a laptop with a 27.2" or larger screen?

No, I don’t want to “turn children on”.

If it were a magic lang item, you could treat the resulting value in a special way. Then, you could create an optimization pass for this situation: if a variable is assigned random in a loop and the loop can only be exited with a certain value, the compiler can coerce the magic rand value to it.

You could do a lot worse. If the type of i was an object, you could overload the negation operation to have side-effects for the third snippet, for example.

I don’t know what I was thinking.

But, if you borrow C’s semantics, you are allowed to “optimize” away side-effect-less loops, even if they would never terminate. But that would require the random method to be pure.

I feel like an idiot. Also, in the “Good” example, no underflow occurs. i goes from 0 to -10, and x is assigned to -i every loop.

It might still be possible to optimize away the random number example, if the random function were made a magic language item, but it would not be even remotely close to being worth the effort.

The compiler should be able to optimize all of them to the same machine code.

1. This is already good.
2. Easily optimized by constant folding.
3. This one depends on the semantics of signed underflow, so it may not do what you want.
4. The loop can only exit if x==10, so as long as the nextInt() method doesn’t have side effects, the loop should be eliminated. But, again, language semantics can affect this.

Edit: Very wrong for 3 & 4, see replies.

Depends on your religion, I guess. The Flying Spaghetti Monster seems pretty edible.

one could argue this is a harmless way for people who suffer from this to get their fix.

I don’t know how many people get off from drawings. I think that AI-generated child porn might be better?

I’ve never understood the complaints about that. It’s not like real children are hurt by those drawings.

Also Ireland, Norway & Sweden.

If you make it amphibious and go fast enough, it will plane.

1. do not use ANY company resources. This could put you at risk of theft.
2. do not do it on company time or make it look like it’s on company time. See point 2.

Did you mean “See point 1.”?

I mostly agree with you, but this is not quite true:

XDG implementation (which is also only used as a fallback when the three DE-specific implementations fail, even though all of them actually support XDG so having separate implementations is pointless)

Yes, the DE-specific implementations is pointless (as far as I know, I use a WM), but the XDG implementation is actually used first, and the function returns true if any impl returns true, like xdg() || gnome() || gnome_old() || kde().

rework the code so that there is a difference between “this DE wants light mode” and “couldn’t figure out of this DE is in light or dark mode” - both of these are now represented by the “false” return value.

This isn’t that bad? Yes, having an enum with three variants would be better and more readable, but the code just defaults to light mode if nothing wants dark mode, and prefers dark mode even if separate impls want both light and dark mode.

With multiple impls, you have to resolve conflicts somehow. You could, for example, match on current DE/WM name, only using the current DE’s impl, defaulting to XDG, avoiding the problem entirely or just use first impl that doesn’t return “default” or “error”.

I don’t like AI generated code, having reviewed some disgusting slop before. But it’s better to criticize the code’s actual faults, like the incorrect impls (which you listed) or failing the Linux CI.