Lacking wonga

That trailer was beautiful. Even if you have no interest in buying the game it’s well worth a watch

If you've been drinking it out of a bottle, you've actually been having Burton beer for over a decade

BBC News - Best-selling bottled ale Doom Bar not brewed in Cornwall - BBC News https://www.bbc.co.uk/news/uk-england-cornwall-33175395?app-referrer=deep-link

I dont get why they didn't just call that update 11.0? Or use that for this update?

I guess if you're changing the semantics of your version numbers its also a good idea to introduce a deliberate discontinuity to mark the change?

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.

Probably relevant that most GNU projects have a limit to how big a change you can make without signing a copyright waiver. My guess is that the logic here is "if its small enough that a human doesn't need to sign a waiver, it can be produced by an LLM"

Komrade Desktop Environment

I don't think it's actually about longer days. Its suggesting that too much time indoors (away from bright natural light) degrades sleep

He's resigning but contesting the resulting by-election.

I guess the logic is that he's about to get suspended, which would likely trigger a by-election anyway, so he'd rather do it in his own terms.

Funny thing is that winning this self-imposed by-election doesn't necessarily stop the recall election from happening shortly thereafter. He's just as likely to get suspended if he wins again, and it still only takes 10% of the electorate to be pissed off with him to trigger it again.

Maybe he'd win both contests, but I could also see the people of Clacton deciding that he's become a liability and opting for e.g. a Restore candidate instead.

Honestly I'm wondering if this is his way of trying to make an exit but saving some face and blaming the establishment?

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

Yeah, this has been going on since way before the conflict in the middle east. Temporary workers are basically a loophole to get around labour rights

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.

Exactly this. IMO we just need better ways of rendering a mailing list inbox as a series of issues/PRs. And maybe better tooling from IDEs to "open a PR" using git send-email.

Source hut is close to my ideal here, but still seems rather complex. Maybe I just don't appreciate the necessary problems it solves yet.

Agree with several people here that named parameters are a good solution, they add minimal overhead at the call site and function declaration and look very natural.

Another option for languages that want function arguments to have fixed size is bitmasks. I wonder if it could be a useful language feature to infer the flag names from the function declaration. Something like

def my_function(arg1, arg2, [FLAG1, FLAG2]) {
    if (FLAG1) {
        do thing
    } 
   ...
}

my_function(val1, val2, FLAG1 | FLAG2)

Maybe they had an insurance policy for if a headliner couldn't attend? In that case definitely easier for the organisers to just cancel and claim

Bre-entry