C because it’s what is used for low-end linux & embedded work.

Shell scripts because they’re the caulk that holds a Linux distro together.

Rust when possible because it’s how I wish systems programming could be.

I was a “ironically” racist as a young teen, it took me till my early adulthood to realise that being ironically racist is just being racist, and the edgy “humour” that is made at others expense isn’t funny or clever, and is incompatible with the kind, empathetic person I wanted to be.

Cringing at my teen self pushes me further into deprogramming myself from that shit, but I’m encouraged by the adage “if you don’t look at yourself from a decade ago and cringe, you wasted that decade”.

I remember old Tesla and Firepro drivers had a jank, proprietary alternative to SR-IOV but didn’t think any vendor (except Intel with i915’s GVT-g) had an implementation for their consumer devices.

Software to allow partitioning gpu resources among multiple virtual machines instead of just assigning the one PCIe device to a single VM. Very useful for having a single GPU do 3D acceleration on a host and multiple guests at the same time.

• Lisp is responsible for most of the parts of programming widely considered enjoyable.

• Fortran is still often used in some of our most performant libraries.

• POSIX shell was one of the most important parts of unix-like systems becoming how they are today, and it’s compatibility is still an invaluable glue for tying programs written in the 90’s to programs written today.

It feels like no matter where I move to, a communist seems to move in at the exact same time… It’s uncanny.

Tailscale edits /etc/resolv.conf, since your DNS isn’t working start by making sure that file is how the archwiki suggests rather than what tailscale changes it to.

An uninstalled tailscale may still have left that file modified.

The specifics matter, but generally no.

When an actual fraud investigation is being done into something major like a casino laundering money, my government tends not to turn it into a media circus until after investigations are underway.

When a politician tells me they want to ‘tackle fraud’, especially welfare fraud, I hear “I want to arrest people for being poor”. It sounds like a dog-whistle to me, because every time I hear it used, it’s by people bearing a “the cruelty is the point” mindset.

It seems a lot of new developers want to do some things differently; old guard devs can either make some compromises, or accept that fewer new devs will want to be part of upstream.

Dunno man, when what the dev of 30+ years said was more or less “fuck off”, it seems that advice was in fact heeded

It’s a chicken and egg problem; manufacturers aren’t going to care to upstream drivers if not enough of their users are on Linux, which slows new hardware. It’s much better than it was, but still ongoing.

Amd’s 7000 series amdgpu driver was busted in several ways for like a year post launch, and is still missing tunables for many GPU features.

Manufacturers are capable of making out of tree and unfree modules, but honestly I prefer the slow progress if it means most driver work stays in-tree.

Either Linus or Greg K-H, likely after feedback from many others.

We should be looking at his given reasons, not making assumptions based on some ineffable set of considerations that he might have.

Christof’s given reason of complexity is sensible, it’s also one already considered when allowing R4L in the first place; adding rust language support has been deemed worth the additional complexity.

I used ZFS with Arch for a while, the volume manager was what I’d call the largest benefit; in my opinion nothing else comes close to being as useful and well integrated.

I stopped because ZFS incompatibility with recent kernels (which I needed for GPU reasons) made me have to rescue my system more often than was ideal.

Some other minor downsides:

• boot can take ages due to ZFS using udev-settle.
• deduplication status is… Complicated.
• you’re kind-of stuck with the performance of your slowest vdev; L2ARC & a metadata device don’t really compensate well for a zpool that is predominantly a raid-z2 of spinning rust.

1. Get kicked from freedesktop for fostering a toxic community.
2. Ditch wlroots for your own compositor.
3. Shit on other compositors in your spare time.
4. Tell people they should just be plugging into Hyprland instead of rolling their own compositor.

Man if I was concerned about sinking the time to make a configuration for the compositor with a bus factor of 1 man-child, and a toxic community; I can’t imagine anybody investing the time to make a compositor is going to want to hitch themselves to that cart.

The compositor is really solid and makes for a great user experience but I’ll be fucked if every word vaxry writes doesn’t make me want to move to sway or niri.

Nixpkgs has more and newer packages than the aur.

The initial time to get shit done is longer; you can’t simply make install, but honestly you shouldn’t have been doing so on arch anyway.

Making your own derivation is much easier than making your own PKGBUILD and should be considered in those terms because you’re not just shoving some binary into /usr/bin for it to explode later when glibc updates.

When things fuck up, reverting to your previous config is at worst a reboot away.

I have much less time than I used to, so moving from arch to Nixos has prevented the time otherwise wasted in an arch-chroot trying to fix issues like the kernel upgrading past what the zfs-dkms supports.

If you’re using specialised proprietary tools, working them in with Nix can be an absolute nightmare, but I use a debian container for them.

My parents treated my device access something they had to keep a keen eye on. They were good at manually making sure I wasn’t sitting around having my brain rot, but their spying on what I was doing into my teens left me with some trust issues.

They briefly tried to use technological solutions to control my access and monitor me, but all that served was to make me very good at circumventing them. Outsourcing parenting to a computer program doesn’t work, and kids notice when you try.

For the same reason spoken languages often have semantic structures that make a literal translation often cumbersome and incorrect, translating nontrivial code from one language into another without being a near expert in both langauges, as well as being an expert in the project in question, can lead to differences in behaviour varying from “it crashes and takes down the OS with it”, to “it performs worse”.

I’ll also tac on that when you use cloud storage, what do you think your stuff is stored on at the end of the day? Sure as shit not Bcachefs yet, but it’s more likely than not on some netapp appliance for the same features that Bcachefs is developing.

In addition to the comment on the mentioned better hardware flexibility, I’ve seen really interesting features like defining compression & deduplication in a granular way, even to the point of having a compression algo when you first write data, and then a different more expensive one when your computer is idle.