It’s certainly good, I’m not arguing that. My point is, if the wine team is interested, they can fork the unmaintained project, and work on that. Eventually, people will switch over to the active fork. What Microsoft is doing, is helping the process along, and making it easier. So it’s good, and helpful - but not really a “donation” to winehq.
I guess it’s simply the framing: It was a not very actively maintained open source project. So they’ve decided to turn it over to a new maintainer. Calling that ‘donation’ is a bit pushing it
I’m confused - why is Microsoft trying to - or expected to, by the article authors - patch a vulnerability in GRUB?
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.
Not really. It seems to use a very different technology from termux.
That said, you can use a third party service only for sending, but receive mail on your self-hosted server.
I think NixOS is awesome, but it certainly doesn’t offer “access to (basically) all Linux-capable software, no matter from what repo.” - at least not natively. You can do that through containers, but you can do that with containers on any distro. Where it shines is declaring the complete system configuration (including installed programs and their configuration) in its config file (on file-based configuration, I wouldn’t really consider blendos a viable competitor).
“Just works” is not a mentality imposed by Microsoft, and has nothing to do with loss of control. It’s simply (a consequence of) the idea that things which can be automated, should be. It is about good defaults, not lack of options.