I know tar zxf and xjf off by heart. I probably do 100x as many extracts as creates. Tar is a stupidly antiquated command though.

I once developed an electronic program guide for a cable TV company in New Zealand and I’d lose my mind if I had to use timezones. The basic rule of thumb was:

a) Internally you use UTC religiously. UTC is the same everywhere on Earth, time always goes forward, most languages have classes that represent instants, durations etc. In addition you make damned sure your server time is correct and UTC.

b) You only deal with timezones when presenting something to a user or taking input from a user

Prior to that I had worked for a US trading company that set all their servers to EST and was receiving trades through the system which expressed time & date ambiguously. Just had to assume everywhere that EST was the default but it was just dumb programming and I bet to this day every piece of code they develop has time bugs.

The only reason people use JS is because it’s the defacto language of browsers. As a language it’s dogshit filled with all kinds of unpleasant traps.

Here is a fun one I discovered the other day:

new Date('2022-10-9').toUTCString() === 'Sat, 08 Oct 2022 23:00:00 GMT'
new Date('2022-10-09').toUTCString() === 'Sun, 09 Oct 2022 00:00:00 GMT'

So padding a day of the month with a 0 or not changes the result by 1 hour. Every browser does the same so I assume this is a legacy thing. It’s supposed to be padded but any sane language would throw an exception if it was malformed. Not JavaScript.

Yuzu gave them the opening to sue though. If they had been more circumspect - “Oh this is to develop homebrew / indie games nudge nudge” then maybe Nintendo wouldn’t have unleashed the lawyers or done so ineffectively. After all it wouldn’t be Yuzu’s fault if some wicked website corrupted their pure intentions by releasing device keys or patches that allowed their emulator run commercial games. But they were more blatant than that.

Also from an empathic perspective, of course Nintendo were going to sue. Yuzu should have known they would since that’s what console platforms do when something interferes with their profits. Yuzu is doubly bad since it interferes with hardware sales and game sales unlike custom firmware / cartridges which only affect game sales.

Of course the genie is already out of the bottle. Yuzu’s source code and binaries were on github for anyone to clone / fork. All the games are out in the wild. The piracy will carry on. I think it’s fair to say the NSP is effectively dead as a platform at this point. If a NSP2 turns up this year, as rumored, then I expect it will have revised anti-piracy measures and potentially a heavy online service aspect to go with it - it’s far easier to detect pirates and wield the banhammer when a device is online.

It’s a rotten analogy. Comparing Linus having a go at some volunteers is not analogous, or comparable to a father abusing kids.

Because of it, quite obviously.

I define effective by the fact it was self evidently effective. No need to split hairs or dissemble here. Linux is objectively, indisputably the most important piece of code in the world. Everything else, such as a the context free boo hoo about some times when he has had a go at people is just noise.

The logic is simple. This is s his style and it demonstrably worked. I’m sure you could point to someone else’s style that also works in another context but that’s irrelevant.

There is a difference between a rant and a tantrum. If you read the post, you could see very clearly he makes a point very forcefully.

This is a nonsensical comparison

Exactly. It might not be good to be on the receiving end, but the chain of discussion that went before these rants should have given people the clue they needed to stop while they were ahead.

Yes you could but he didn’t and clearly his style was self evidently effective. And I’d add that if you’ve ever read the LKML archives, that these rants were rare and usually preceded by long chains of discussion before it reached that point.

In almost instances of Linus going off on one in public it is because maintainers weren’t doing their jobs (to act as quality gatekeepers), or particular developers thinking they could steam roll road changes through if they kept submitting them, or not listening to what Linus was saying. I remember Linus used to ream out Hans Reiser a lot (the guy who was subsequently imprisoned for murdering his wife) because he constantly tried to get ReiserFS into the kernel despite serious issues Linus had with it.

So generally when you see a rant, there is a history behind it and the rant itself is directed with a point. I also think it’s self evident that the kernel has benefited from this “benevolent dictator” model. I’m sure some people have gotten all precious over their feelings being hurt. The rest raised their game and the result has been a code quality standard you’ll probably never see anywhere else.

His style of being direct, having a high quality threshold and calling out bullshit immediately and bluntly is why the Linux kernel went from a university project to powering everything from lightbulbs to super computers. I think it kind of ridiculous that this demonstrably effective style got framed as “toxic” just because he hurt a few people’s fee-fees.