Rust and Cargo enters the room.

128 GB here which runs out if I compile the complete project at work with -j32. And this sucks because 128 GB right now means the RAM cannot run super fast, meaning it is a bottleneck to any modern Ryzen…

A random hacker news comment. I’m in EU, where this kind of tracking is not legal, so I cannot validate…

If it is a Samsung tv, they have been automatically connecting to any open wifi, maybe your neighbor has one. And there goes the data.

Avoid Samsung.

Autechre’s NTS Sessions. All of them work great, but start with the fourth one.

We’ve been using Linear in my latest company and it is actually quite good. No bullshit fast UI, boards, issues linking with Git, a support that can take a feature request that is often implemented in a week or two after asking it.

Yeah. He is pretty horrible. What surprised me though is his daughter’s film company has a pretty solid track record on quality movies and tv series:

https://en.m.wikipedia.org/wiki/Annapurna_Pictures

But yeah, Larry Elison sucks…

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.

Underground techno parties. Lots of cool people.

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.

Wait, the article says to use parmesan, eggs, pancetta and spaghetti? Uh, it is pecorino, eggs, guanciale and spaghetti. This is basically the only way to get the best results. You can fuck with any other italian pasta, but carbonara is only good if done exactly with these four ingredients. And of course a ton of black pepper.

I know, I tried every possible combination. The only one that makes sense is the one with pecorino and guanciale.