They didn’t say it was purposeful or not, just that it isn’t always misleading… Sometimes someone can have RBF and actually be exactly like they look

All Kids Shuffled Off To Become Someone Else’s Problem

Yeah, Ma Bell breaking up into the Baby Bells is the only real example I can think of, and even they came back together later (though, by then, there was enough diversity in the market that they couldn’t reclaim the level of market dominance they once had)

I’ve been using it off and on for over twenty years and it’s never needed more than running the installer to get it working on Windows in that time…

I mean… The kernel is called NT, not Windows, but okay

Unintentionally brilliant

That is what we like to call a “gateway drug”, first they try out an Android, then “just a taste” of Steam Deck, and next thing you know they’re installing arch btw on their grandparents’ computers

And this is exactly why I wouldn’t do my own, I had no idea either of those were legal/possible

What claim, that I probably could? I didn’t say anything at all about it being easy, it would be a pain in the ass and involve a lot of checking the RFC, but I could probably make one that accurately represents the spec if I wanted to take the time, and even then I’m not exactly confident I would hit every edge case.

But why would I go to that hassle when there are well designed and vetted ones available?

I believe you missed the point I was making

Embrace
Extend
Extinguish

And this right here is a great example of why simple basic RegEx is rarely adequate

At the very least, should be something like

^[^@\s]+@([^@\s.]+\.)+[^@\s.]+$

I’m like 99% sure I missed at least a few cases there, and will say “please don’t use this for anything production”

I’d love to know where they got the idea that the spec doesn’t allow that…

One of the reasons I’ve always avoided .info, nobody seems to believe it’s a real domain

That’s what it looks like to me too

I could probably write a RegEx for email format validation that’s accurate, but why would I when there are ones already written and readily available that covers all possible legit variations on the standard? I never understood why people insist on writing their own (crap) RegEx for something with as many possible variations they can miss like email…

And that one isn’t even a weird edge case! It’s a domain with a sub domain, if they can’t even cover that case then it’s an extra shitty RegEx

The good news is Linus did eventually learn this isn’t okay and took some time off to reflect on how to approach these things better.

He still doesn’t tolerate things like he was responding to here, still responds to them firmly and directly, but doesn’t rant, yell, or hurtle insults

For the first part, no clue, but for the second, absolutely

Just because you work for someone else doesn’t give them the right to treat you badly and that sort of behavior can and should be reported to a person’s employer.

That’s very “ends justify the means” of you. No, that’s not the question here. Linus could have gotten the same results without the yelling and insults. You do not need either of those to be direct, assertive, and clear on what the issue is, something that Linus has since learned

“You’re not wrong, [Linus], you’re just [being] an asshole”

Yeah, that’s a hard pass on passive aggressiveness, constructive criticism isn’t either of those things nor rude and angry ranting. Love Linus, but he really did need to chill out a bit more with these things. He could have gotten the same point across without coming across as yelling at the guy, just firmly pointing out that it was caused by the patch, the patch did things it shouldn’t ever do, and don’t break userspace or blame userspace programs

Yeah, Gnome is VERY different than in 2008