cbarrick

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.

Do Nerd Fonts use the Unicode private use area?

It seems not. It seems like they replace CJK characters instead.

The PUA seems like the right way to handle this.

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.

TIL. Thanks for the correction.

\1. Many retro games were made for CRT TVs at 480p. Updating the graphics stack modern TVs is valuable, even if nothing else is changed.

\2. All of my old consoles only have analog A/V outputs. And my TV only has one analog A/V input. The mess of adapter cables and swapping is annoying. I want the convenience of playing on a system that I already have plugged in.

\3. I don't even still have some of the consoles that play my favorite classic games, and getting retro hardware is sometimes difficult. Especially things like N64 controllers with good joysticks.

Studios don't need to do a full blown remake to solve these problems. But I'm also not going to say the Crash and Spyro remakes weren't welcome. Nintendo's Virtual Console emulators toe this line pretty well.

But studios should still put in effort to make these classic games more accessible to modern audiences, and if that means a remake, that's fine with me.

(I'm mostly thinking about the GameCube/PS2 generation and earlier. I don't see much value in remakes of the Wii/PS3 generation yet.)

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.