So you’re telling me that there was a Mac super computer in '05?

TL;DR - We can now control swappiness per cgroup instead of just globally. This is something that userspace oom killers will want to use.

You don’t need to provide root access just because you used GPL code, you just have to follow the GPL.

Well, to follow version 3 of the GPL, you do actually need to provide effective root access.

Specifically, version 3 of the GPL adds language to prevent Tivoization.

It’s not enough to just provide the user with the code. The user is entitled to the freedom to modify that code and to use their modifications.

In other words, in addition to providing access to the source code, you must actually provide a mechanism to allow the user to change the code on the device.

The name “Tivoization” comes from the practice of the company TiVo, which sold set-top boxes based on GPL code, but employed DRM to prevent the user from applying custom patches. V3 of the GPL remedies this bug.

For Zulip, I’ve only used it on the web. Apparently they have iOS, Android, Desktop, and Terminal clients.

For Matrix, there are many clients on all platforms, but none have ever stood out to me. Element is the official client, and it’s… fine I guess.

I love this, especially the criticism of the FSF.

For coms, Zulip seems OK. I would really like Matrix to take off, but I honestly don’t really like any of the clients.

Yes, thanks for the spelling correction.

8½ is a pretty surreal. Considered one of the most influential films of all time. One of the earliest examples of post-modernism in film.

Every scene in Ex Machina is basically a dialogue covering different arguments in the philosophy of AI. Plus a surreal dance scene.

I was blown away by mother! when I first saw it. But looking back on it, the allegory wasn’t exactly subtle.

Once Upon a Time in Hollywood is a meta-modern masterpiece.

Tropic Thunder, as a meta commentary on comedy, is actually really good. Aside from the great comedy itself.

The meaning of version numbers can vary across projects.

One common scheme is Semantic Versioning, which divides the version number into three parts: MAJOR.MINOR.PATCH*

• MAJOR is incremented when there are backwards incompatible changes.
• MINOR is incremented when new features are added in a backwards compatible way.
• PATCH is incremented for smaller big fixes.
• Each number is reset to zero when a higher level number is incremented.

* It’s a bit more complex than this, but this is the gist.

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.

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.

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 😺