Khleedril

@freeman @Scoopta Yes it does.

@patrick @ruffsl Don’t lose sight of the fact that Github is actually Microslop, and they’ll do anything to keep their fingers in that pie.

@Maragato Ah I see, I was thinking of consumer businesses rather than producer businesses. In that case I would definitely opt for community-produced distros, every time.

@ItsMyVault101 @codeinabox Where we’re going, we won’t need computers.

@Maragato A business worth investing in would go for a wholesale distribution, like Debian or Slackware, rather than a retail one like Ubuntu or Red Hat. I don’t recognize the term ‘business distribution.’

@Retro_unlimited @Lemmchen This is one of the big things about #foss: there is no cause for restrictions, other than what the hardware can provide. None of this, ‘Buy the Pro version to make a longer movie’ nonsense. If the software breaks your machine, you get to keep both parts and the author is not liable!

@pressanykeynow @Corbin There is some python in the build infrastructure.

But this is the real reason for the push-back against Rust: it is something else that everybody involved has to learn, and that means diluting the extreme expertise in C that makes the kernel so good.

In a distant nirvana, there will be no C left, only Rust, and then all developers can really drill down on that.

@nyan @Gobbel2000 This, totally. But then if you are going to throw unconstrained machine learning in there you are going to run into hard-to-diagnose bugs.

@sip @Delilah Why would you? The alias is longer than the thing it replaces!

@Limerance @schnurrito Well, Linux\systemd\Wayland\KDE if that’s your salt; Linux\Guix\AwesomeWM for me!

@FauxLiving @cm0002 It is actually one of the best things you can read. That and the #Rust book.

@okwhateverdude @SirHaxalot The billionaires have the whole surveillance thing in their pockets. I mean the whole shebang, Five Eyes and everything.

@Itdidnttrickledown @ruffsl Nix is dumbing it down? I think you are shooting the messenger here, not those that are doing the dumbing down.

@MonkderVierte @Samueru_sama I don’t think the standard (more like a guideline) is bad in itself: consistence of file-system use across applications is good for all our sanity. It is the assumption that all applications use it rigorously that is the problem. The word is SHOULD, not MUST.

@Linktank @OR3X Wow, you’re rubbish.

@entwine @IcedRaktajino Haters know there are loads of other good ways to orchestrate an operating system. E.g. #shepherd

@refalo @mmmm #guix also follows this philosophy, but uses #shepherd as the root process.

@cornshark @cm0002 The main con is that it won’t run.

@exu @tangonov To be fair, vibecoding is doing that, it is just that many people are too lazy to even vibecode properly.

@NaibofTabr @HappyFrog I think this is just incorrect. You don’t need swap space to be the sum of the active swap file and the size of RAM, it only needs to be at least the size of RAM. The numbers in the article suggest bigger sizes for smaller RAM so there is less chance of a heavily-loaded running system crashing. You do want a bit more space when hibernating just to make the hibernation process a bit smoother.

Happy to be corrected by someone with provenance.