Maybe.

Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.

However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.

Quite the opposite.

GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.

Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.

Linux won because it was simple, not elaborate.

Motorola has been in the tracker game since way before Air Tags.

I remember getting a Bluetooth tracker with my Moto X circa 2014. Back when Tile dominated the market.

You talk about “non-absolutist,” but this thread got started because the parent comment said “literally never.”

I am literally making the point that the absolutist take is bad, and that there are good reasons to call unwrap in prod code.

smdh

Fair. But unwrap versus expect isn’t really the point. Sure one has a better error message printed to your backtrace. But IMO that’s not what I’m looking for when I’m looking at a backtrace. I don’t mind plain unwraps or assertions without messages.

From my experience, when people say “don’t unwrap in production code” they really mean “don’t call panic! in production code.” And that’s a bad take.

Annotating unreachable branches with a panic is the right thing to do; mucking up your interfaces to propagate errors that can’t actually happen is the wrong thing to do.

Unwrap should literally never appear in production code

Unwrap comes up all the time in the standard library.

For example, if you know you’re popping from a non-empty vector, unwrap is totally the right too for the job. There are tons of circumstances where you know at higher levels that edge cases defended against at lower levels with Option cannot occur.

deleted by creator

They can’t even be punished. robots.txt is just a convention, not a regulation. It’s totally not enforceable.

The only legal framework we have is copyright law. Those who oppose this behavior will have to demonstrate copyright violation, and that may be difficult to do since the law hasn’t caught up.

This comment is copyrighted by me and licensed to the public under the terms of the CC-BY-NC-SA 4.0. If you intend to use this comment for commercial purposes, you must secure a commercial license from me, which will cost you a lot of money. If you violate the terms of the CC-BY-NC-SA 4.0 without securing an appropriate license, I will send my army of lawyers that I totally definitely have to defend my copyright against you in court.

orlp invented PDQSort and Glidesort. He collaborated with Voultapher on Driftsort.

Driftsort is like a successor to Glidesort.

Glidesort had some issues that prevented it from being merged into std, and which are addressed in Driftsort. IIRC it had something to do with codegen bloat.

What’s wrong with AC if it’s powered by renewable electricity?

Zsh

No plugin manager. Zsh has a builtin plugin system (autoload) and ships with most things you want (like Git integration).

My config: http://github.com/cbarrick/dotfiles

Unicode cat 😺

Exactly.

My take is that the issue isn’t with tmpfiles.d, but rather the decision to use it for creating home directories.

Someone told me that Goldeneye actually supported dual stick controls if you plugged in two controllers. And Perfect Dark is the same engine.

I need to try that out on real hardware…

With a headline like that, I thought he died…

The thumbnail is of the 9/11 attack with the Wine logo overlayed.

Nearly 3,000 people died in 9/11.

That image is in very poor taste. wtf.

RIP Fuchsia

Apple Security Bounty awards may not be paid to you if you are in any U.S. embargoed countries or on the U.S. Treasury Department’s list of Specially Designated Nationals, the U.S. Department of Commerce Denied Person’s List or Entity List, or any other restricted party lists.

Kaspersky can whine all they want. Russia is embargoed. They’re not getting their money.

Kaspersky is a good company doing good work in the cyber security space. Unfortunately, because of the embargo, they may have to turn to the black market to sell future exploits. Or maybe not; I’m not totally sure what kind of ethical standards they have.