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”
I presume “desktop” is the operative word here, so mobile devices aren’t counted. Even most Mac users run Chrome I think
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.
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)
Personally, I do think it’s a useful exercise to decide what your red-lines are when it comes to OS level age verification.
For me: Having a field in a database that could contain my DoB is acceptable. Having a prompt to populate it during first time set up is very concerning. Requiring that data to be validated by a third party is the red line.
If you don’t want to be boiled like a frog, bring a thermometer.
I’d say don’t risk it if you’re not based in the UK.
I have a .uk domain and had to provide proof of residence or something to nominet. I can’t remember the exact process now, but they did temporarily suspend my domain (without warning) until I contacted them.
Well now I’m nervous! My first instinct though is that the vast majority of Emacs packages are plain elisp, and Emacs users have a habit of cracking open and tinkering with their packages, so any malicious code ought to be spotted quickly.
With the native compiled modules however, it could be another story…
That’s only true in the sense that liking scheme makes you become a language nerd
I get that calling command line tools is a bit clunky, but python is always my go-to when shell scripting gets too painful
Could be a non-native speaker using an LLM to translate with a specific tone
MacOS Requirements: 💵💵💵
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?