I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.
35,176 karma · joined December 17, 2016
I don't think they are, actually; they appear to be arguing microkernel vs monolithic kernel, and we have unix-likes based on microkernels.
Do you have a way to do it on the hardware people actually have that doesn't destroy performance every time the CPU context switches? You can always move all your filesystems to FUSE if you like the performance...
Which is, of course, why GrapheneOS is based on minix, right?
Edit: Really, this is just GOS being GOS; only ever Security (by their own very specific, poorly defined definition thereof), with nothing else allowed to be a consideration. There is a reason the industry went with monolithic kernels when other options existed. Even today in 2026, we've merely worked out how to reduce the performance hit of microkernels, and in the 90s Torvalds was very justified in preferring to ship something that would actually run decently on extant hardware.
Edit2: To be fair. I like minix. I have actually tried to make HURD into a usable system. I want these things to work. But there are harsh tradeoffs in play that are still painful even after decades of work, and this kind of post does not exactly convince people that GOS is making level-headed evaluations of technical choices.
I mean. I'd sure be reluctant to depend on it until it had trickled out through the ecosystem
Because the pi has a maintained kernel and a userspace I don't have to fight.
Thankfully, that's not really how open source ecosystems work. There are still people interested in both using and developing X11.
> Outside of legacy systems, I just don't see why people are going out of their way to get back on X11/Xorg outside of perceived FOSS politics and posturing.
Well, when Wayland supports the features that people use on X11 I suppose we can discuss it. As of the present day, moving "forward" to Wayland would mean massive regressions in a11y tools that I'm not willing to give up just yet, and accepting a fragmented landscape where questions like "how do I change the keyboard layout" or even "is it possible to change the keyboard layout to anything but us+qwerty" are "It Depends™, what compositor do you use" (because Wayland deeply believes in reinventing the wheel over and over again, forever).
Xorg is not actively developed. X11 is fine.
I wouldn't wish to defend them, but by all accounts the biggest reason is because Xorg's code quality is quite poor, which is (if true) somewhat fair. I wish they tried replacing it without breaking everything and shipping the terrible design that is Wayland, but the goal of replacing Xorg is reasonable.
> AI tools have several ethical issues. They require an unreasonable amount of energy[1] and water[2] to build and operate, their models are built in part with heavily exploited workers in unacceptable working conditions[3], usually without consent from or compensation for creators of the source material[4] and oftentimes causing DDoS attacks against FOSS infrastructure in the process[5] (which in turn force the deployment of challenge-based protections and increase cost and complexity of self-hosting for everybody[6]). Furthermore, they are being used to undermine labor and justify layoffs[7]. These are harms that we do not want to perpetuate, even if only indirectly.
( https://docs.nura.eco/policies-and-processes/development/ai-... )
If you really believe that AI tools are automatically unethical because they destroy the environment, harm workers, and constitute an attack on FOSS infrastructure, then it doesn't really matter how the tool is being used. If you just don't want to see code quality decline, then it's probably not a problem.
.... Right. Exactly. Everything has some vulnerabilities, but if an attacker has to use a relatively rare VM escape, that's a huge win.