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.

While I think the cynicism is well-earned, we should pay attention to when we're proven wrong and highlight when companies do something right. Bitwarden's fuck-up gave them an opportunity to signal that they're not intending to build a wall for their garden, and they took it.

Moving some packages (especially libraries) onto an unstable branch while keeping others back on a stable one. It probably won't fuck you immediately, but when it does it'll be a bastard to diagnose because you will have forgotten what you did.

It really depends on what you're most comfortable with; when you go for such a custom option most of the design decisions are about personal preferences.

I suggest you draw out some layouts on a piece of paper, adjust them until you feel happy and then plan out how you want the keymap to look. When you're happy, look for a layout that fits what you want or build your own on KiCAD.

I bought a kyria from Splitkb, and I've been very happy with the design. If I needed another keyboard, it would probably be a very similar layout, but have slightly fewer keys, be low-profile and no oleds.

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.

They're not trivializing, just noting that the different things you need to discuss for kernel development compared with other work. It is very different in a lot of ways, and does shape your perspective. I also find it interesting.

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".

A rather overly simplistic view of filesystem design.

More complex data structures are harder to optimise for pretty much all operations, but I'd suggest the overwhelmingly most important metric for performance is development time.

Yes, but note that neither the Linux foundation nor OpenZFS are going to put themselves in legal risk on the word of a stack exchange comment, no matter who it's from. Even if their legal teams all have no issue, Oracle has a reputation for being litigious and the fact that they haven't resolved the issue once and for all despite the fact they could suggest they're keeping the possibility of litigation in their back pocket (regardless of if such a case would have merit).

Canonical has said they don't think there is an issue and put their money where their mouth was, but they are one of very few to do so.

Opengear in Brisbane; development teams often use Linux.

Brand new anything will not show up with amazing performance, because the primary focus is correctness and features secondary.

Premature optimisation could kill a project's maintainability; wait a few years. Even then, despite Ken's optimism I'm not certain we'll see performance beating a good non-cow filesystem; XFS and EXT4 have been eeking out performance for many years.