I don’t do it for the money. I do it because I like doing it.

The reaction is funny too, because in my experience comparing communities of various distros, Fedora’s community is among the the most inviting and professionally-behaving of them.

Personally, I am not running Fedora at the moment, but probably will when my Framework 16 arrives, since Fedora is officially supported on it. And to be honest, I find that I am making the same choices with Arch as Fedora would have made for me (aside from bootloader), so I feel that I’m wasting a bit of effort.

Enjoying it, and time.

These comments really speak to me as someone who is comfortable in Arch but mildly interested in NixOS. The concept seems great, and it seems to work very smoothly when it works. Yet there are always these war stories where people have had to fight the system, to debug some misbehaving hack that is nonetheless required to smash a particular package into the NixOS mould. It is discouraging. The idea I get is that NixOS involves more time doing OS curation chores than does Arch, which already hits the limit of my willingness.

Flakes are another issue. The pre-flakes way seems to be de-facto deprecated, yet the new, flaky way is experimental. I don’t want to waste time learning a doomed paradigm, and I don’t want to depend on anything experimental.

For me, configuration files in git plus btrfs snapshots is just so straightforward. I want to see NixOS as a better way, but I can’t.

Every time I hear this word firefish, I cannot help but be reminded of the phrase “turds of the firefish”, which appears quite randomly in one of Orson Scott Card’s novels.

Neither: I am not aware of it.

Notice how none of these replies are “AI assistant”?

Excellent. Just in time for some migration of my root filesystem I’ve been wanting to do.

Tell them if no VPN, they’re getting sued by a bunch of copyright holders.

We’re talking cross-platform depravity these days.

I even explicitly called out my statement as tongue-in-cheek, so it’s not to be taken 100% seriously. And full disclosure: I myself am not a PHP developer, but much worse: a PowerShell developer, among other languages.

This is a bit tongue-in-cheek, but kbin generally requires its users to be either unaware it is written in PHP or OK with using something written in PHP. That has to exert some selective pressure.

Annoyingly, the article never said what it tasted like.

Exchange rates are a bitch

I am both a (T-)SQL expert and a language design enthusiast. IMO, SQL the language is mediocre in its grammar and extremely resistant to cleanliness. Once you get past that, the things you can actually do with it are extremely useful.

I’d love for a better syntax to exist, but it’s a Herculean task to make one. Modern SQL dialects have gargantuan, labyrinthine grammars, and they grow with each new product version. It’s a lot easier to keep adding to that than to build a feature-complete replacement. This is also the reason why most ORMs are so frustratingly limiting: it’s too much work to support the advanced features of one SQL dialect, let alone multiple.

Well, I don’t, because mine is for ripping threads. Use the right tool for the job.

Dang. In wildfire season here in western Canada, my air filter gets brought out well before the 100 mark.

Just heard of this service but I am signing up first thing tomorrow.

The leopards only eat the bad zoo patrons. Well, that, and every new leopard gets to eat one child, but only when we first get the leopard.

As someone who has mucked about inside the PowerShell code a bunch, it’s a mess. It looks like clean OO design on the surface, but once you dig in, you find it’s actually a fairly tightly-coupled tangle of spaghetti. It gets the job done, I guess, but it’s not enjoyable to hack on.