And who hasn’t contributed any code to this particular repo (according to github insights).
In September the NixOS constitutional assembly should finish their work, and the community will be able to elect governance. I’m guessing that’s when the drama will start getting resolved.
In the meantime, there are multiple maintainers that have left because of the drama - which is more troublesome than the board members leaving - but nixpkgs has a LOT of maintainers, and there are new ones joining all the time. It’s still healthy and won’t implode so quickly.
They are major concerns, but they aren’t the only reasons people would use Linux, and also not everyone who uses Linux does it for these reasons. For example, while I care about them, my most important reason for using it is utility features such as my tiling WM.
That only works if the main reason someone uses Linux is personal privacy.
However, it also uses halium and libhybris. That means you can’t just install your favourite distro and upstream tools. Everything that needs GPU acceleration needs to be patched for libhybris. For example, that means no upstream wlroots - and the latest patched version I think is 0.12 or so.
Actually, no, this seems to work on a very different principle.
Not really. It seems to use a very different technology from termux.
I like the idea, but I really hate that they’ve hardcoded the provider.
How do you declaratively apply the configuration? Is that a feature of Kvaesitso?
Good point. I’d try to grep for something like [Bb3][Ee3]g[Ii1][nη]\w+<and so on>
but I just know I’ll miss something
Oh, in that case we don’t need to read either - just run a simple grep!
Finally, presumably if anyone added some malicious code in a their program, it would be sneaky and not obvious from quickly reading the code.
On the one hand, doas is simpler. Less code means less bugs, and lower chance someone manages to hack it and gain admin rights. On the other hand, sudo is more popular, and so has a lot more people double-checking its security. Ultimately, I don’t think it matters - when someone unauthorized gains admin rights, usually it’s not due to bug in sudo or doas, but other problems.
AI that can auto generate all those command line arguments I keep forgetting? Sure.
Closed source terminal that requires account? No way.
We had Ansible, containers, ZFS and BTRFS that provided all the required immutability needed already but someone decided that is is time to transform proven development techniques
Just so you know, NixOS is older than all of these, actually. And for that matter, no less flexible.
I’m just guessing, but you can try brackets around xclip -o | wl-copy
in the long command.
Exactly! Many of the criteria included aren’t all that good for new users, and neither are the suggestions. It’s not really a good resource for experienced users either.
Well, when you get from 3 to 2000 in only a few years, the vast majority of these versions will be unusable. No wonder they had to drop everything after 11…
I’m confused - why is Microsoft trying to - or expected to, by the article authors - patch a vulnerability in GRUB?