I was joking here a bit, but:

• A big crowd of people has suddenly a lot of weed.
• People in Berlin like to go to bars and like to smoke weed (a fact)
• Suddenly there’s a lot more weed, many people more are smoking it either in the bar (allowed in a few places at least in Neukolln) or outside the bar (about every other place outside Neukolln)
• Fun.

So it was my take on laughing a bit about the winter 2024…

Yeah. I don’t mean that. But how is it going to look like in bars when everybody suddenly has hundreds or so grams of weed…

I’m in Berlin and half of my neighbors have these 3m tall weed plants on their balconies. 3-4 usually, and nobody really cares. I wonder how the winter is going to be when everybody suddenly has half a kilo of weed…

In my experience, nix works exceptionally well with Rust. Python and JavaScript are nastier, especially if the libraries use C extensions.

Zenarmor ftw.

Musl can be a bit annoying compilation target sometimes. Usually it works but I’ve debugged bugs a few times that were due to musl target.

I prefer my distro with glibc…

But do not run Linux, the kernel.

Ah. And delivered very often in the tiniest possible bottle. One drop of cola that just turns into steam on your tongue.

Where is the kilo of crushed ice and a liter of coke, huh?

Just found both of the albums. Can’t wait to listen!

I do that all the time.

His job is to not get the maintainers to agree, but his job definitely is to bark a bit if somebody behaves like Ted.

It might even be Rust is not meant for Linux kernel and it will never happen. Or it happens in the driver layers, but stays out from the core. We do not know yet. The concern Ted is raising is definitely valid: if the C APIs change, people who work daily in the C code cannot spent cycles fixing the Rust APIs. These people have their day jobs which pays them to maintain these subsystems, and it is at least not yet clear will these employers fund rewriting anything in Rust. There are tens of filesystems in Linux, with lifetimes passing around that are not documented and might not work in Rust.

Note: I’m a Rust dev for the past 10 years, and I follow this discussion with high interest.

Yeah. Isn’t it funny that the most popular file system in the world has such a codebase, and it is not even well documented how it works!

I have my reasons to choose XFS or bcachefs with my machines.

Yes and no. Linus can yell to people and he does, he can force his say as he has been recently doing by expecting sched_ext to land in 6.12. BUT. Linux is a bazaar, it’s so big and there are so many different factions forcing them to do anything is going to take a long time. Lots of different teams are working on Linux, with their own priorities.

And LLM is mostly for investors, not for users. Investors see you “do AI” even if you just repackage GPT or llama, and your Series A is 20% bigger.

The borrow checker is exactly what the kernel needs.

Ted is the maintainer of ext4 and there are not many people in the world who understand this code.

For Rust to succeed, it has to get the subsystem maintainers to agree. It is going to be many years of petting very angry bobcats…

And that is not even the worst I’ve heard, makes you a bit numb if you follow LKML.

Upper middle class gays somewhere in Gilbert Arizona who just want to see their retirement savings to go zoink. You have your walled swimming pool and Trader Joe’s nearby.

Did so years ago. Everybody uses it from my family and friends. I’ve had a very active group chat there for eight years with friends. My mom uses it actively, even calls me using Signal. My partner knows it is the best chat app and actively uses it.

I just asked ages ago for everybody to switch to signal, they valuated the features and for a group chat automatically deleted messages and strong encryption were really interesting for everybody. Now we can shoot shit in a group chat without needing to worry that the logs are stored somewhere forever.

Me neither, but the risk is there and well documented.

The point was, ZFS is not great as your normal laptop/workstation filesystem. It kind of requires a certain setup, can be slow in certain kinds of workflows, expects disks of same size and is never available immediately for the latest kernel version. Nowadays you actually can add more disks to a pool, but for a very long time you needed to build a new one. Adding a larger disk to a pool will still not resize it, untill all the disks are replaced.

It shines with steady and stable raid arrays, which are designed to a certain size and never touched after they are built. I would never use it in my workstation, and this is the point where bcachefs gets interesting.

Sway is on wayland and wayland together with systemd is the best thing that ever happened to Linux.

/me throws a smoke bomb to the floor and runs away laughing.