Its a british thing. If a company wants to lay off a large amount of employees, they have to go through a process called consultation. This obliges them to sit down with your trade union rep (if you have one) and tell them why your job is being cut.

Not sure how much difference it makes in practice, but at the very least it guarantees a 40 day period between announcing redundancies and actually firing people.

Komrade Desktop Environment

I had no issues when my domain was registered with GoDaddy. It was shortly after switching to porkbun that the issues started. Porkbun blamed nominet and nominet blamed porkbun. Not sure what actually happened, but it does seem related to nominet’s policy about who can hold a .uk domain

Nominet manages the .UK domain, and they’re a bit funny about proof of residence. Not sure I had to give Porkbun any photo ID, but the did temporarily suspend my domain. Took forever to clear up.

IMO the moral if the story is avoid ccTLDs (though now I have it I’m sticking with it for as long as I can).

No apologies necessary! I was partly kicking the hornets nest to see if an interesting discussion fell out…

That blog post is absolutely brilliant! It does a great job of stating what a user should want from a system: easy and deterministic re-deployment. If atomic ends up being the best too for that job, I’ll come back. But for now I’m happy with Debian, a separate home partition, and a strong preference for flatpak over apt.

Hmm, I think I agree with this.

Certainly I’d love a universal GUI/CLI package manager with optional sandboxing. I don’t use nix, but it seems like the closest solution out there right now

Its not so much the UX that I take issue with, but the complexity of what’s going on under the hood.

The way I see it, either the base image of an atomic/immutable distro is suitable for you, or it isn’t. Once you start getting into the territory of layering new tools/drivers/whatever on top, you’re reintroducing the statefulness that the atomicity was supposed to eliminate.

This is cool, and I’m interested to see where this goes. But to me the whole sysext thing is actually a compelling argument for why Linux power users (i.e. most Linux users on lemmy) aren’t suited to immutable distros.

When something as fundamental as git requires multiple obscure commands to install, you’ve got to think twice about the target audience.

Dumper’s delight

Its a fair point, and well explained. However, I think it implies that illegal immigrants are fine so long as they’re not more criminal than the general population.

Generally if somebody is using crime statistics to argue for more immigration control, they’re probably the kind of person that believes the only acceptable amount of crime for an illegal immigrant to commit is zero crime.

I had a go at using guix as a package manager on top of an existing distro (first an immutable fedora, which went terribly, then OpenSUSE). Gave up for a few reasons:

• As mentioned in the article, guix pull is sloow.
• Packages were very out of date, even Emacs. If I understand correctly, 30.1 was only added last month, despite having been available since February. I get that this isn’t the longest wait, but for the piece of software you can expect most guix users to be running, it doesn’t bode well.
• The project I was interested in trying out (Gypsum) had a completely broken manifest. Seems like it worked on the dev’s machine though, which made me concerned about how well guix profiles actually isolate Dev environments. This was probably an error on the dev’s part, but I’d argue such errors should be hard to make by design.

All in all I love the idea of guix, but I think it needs a bigger community behind it. Of course I’m part of the problem by walking away, but 🤷