This is valid and I hate it.

Anyway, according to Wolfram Alpha’s calculation (because I’m lazy), my car has a fuel economy of 2.126x10^11 inverse hectares

Of note, it also straight up doesn’t work on Tom Bombadil. He is immune to its temptation, and it doesn’t make him invisible.

Not all trains. I’ve yet to see a subway with one

I recently had a complaint with a website:

“Users are having trouble scrolling!”

My response:

“Are they using the scroll wheel/directly scrolling with the touchpad, or using the scroll bar?”

They were, of course, using the scroll bar. I am now somehow responsible for design choices made at the level of the browser, because browsers have decided that the scroll bar should be nigh impossible to use. Yippee.

She’s not even holding the flute right. I’m not sure the Lord will appreciate her fingerings

Honestly, I think it actually makes some sense this way around. To me, in JS “==” is kinda “is like” while “===” is “is exactly”. Or, put another way, “equals” versus idk, “more-equals”. I mean, “===” is a much stronger check of equivalence than normal “==”, so I think it deserves to be the one with the extra “=”

Identity. “A is literally B” instead of “A equals B”. This is necessary here in JS because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons

Counterargument: it ruined https://youtu.be/Vx5prDjKAcw and that’s not cool.

Downvoted from lemmy.sdf.org