4 ms·
I believe the "Linux Sucks 2021" [0] video did a great job of explaining not just how the YoLD hasn't happened, but why it will never happen, now. Linux is bui
by snvzz 5y ago
I believe the "Linux Sucks 2021" [0] video did a great job of explaining not just how the YoLD hasn't happened, but why it will never happen, now.
Linux is built with a bad architecture (spaghetti monolithic kernel with no stable APIs), which has a tremendously high cost of development, and also a high cost of maintenance. Large companies (e.g. Google) have realized this isn't sustainable, and are shifting away into better architectures (e.g. Fuchsia), which tend to be microkernel multiserver systems.
As money goes away, Linux maintenance cost can't be met, and it'll crumble on its own weight.
I do still hope a good desktop/workstation OS with a FOSS license will happen. It just won't be Linux, because its architecture was never suited for it.
[0] https://www.youtube.com/watch?v=WtJ9T_IJOPE https://www.youtube.com/watch?v=WtJ9T_IJOPE
- phoe-krk 5y agoHonest question: are the NT or XNU kernels any better architecture-wise? What about BSDs?
- sharikone 5y agoI am not qualified enough to answer for NT and BSD (I only can note they appear very stable nowadays). But XNU is not much better than Linux. It has a schizophrenic soul with its BSD and Mach duality for everything. It is bogged down by Apple's never-ending "security" lock down efforts. It has no equivalent of "jails/containers". And, again, it is practically unusable for anything that is not created by Apple and is not extendable now that they are phasing out kexts. I think a very interesting recent effort in kernel architecture innovation is Fuchsia.
- tagrun 5y agoWhat do you mean by "kernel with no stable APIs"? Linux developers, as a policy, don't break user space. And since when Google became the representative of stable APIs? During 90s, the de facto desktop OS used a monolithic kernel, so clearly, having a monolithic kernel doesn't prevent common adoption on desktops. Fuchsia is a microkernel, which would play nice with phone vendors with binary blob drivers, but this is a licensing issue not a technical one.
- tenebrisalietum 5y agoProbably meant ABIs which causes proprietary drivers to be locked to the version of Linux they are shipped with.
- tagrun 5y agoThat would be an entirely separate issue related to licensing (which historically led to the creation of GNU and free software foundation BTW).
- trasz 5y agoHow is the lack of stable kernel API/ABI related to licensing?
- temac 5y agoThere is an indirect relationship in that only out-of-tree kernel-space Linux drivers are inconvenienced by that, that lots of out-of-tree kernel-space Linux drivers are proprietary ones, and that most kernel-space Linux proprietary drivers are dubious on licensing grounds (to be clear, NVidia seems to be one of the most clean in that regard, but I'm not aware of tons of proprietary drivers as clean as they are). The thing is: it makes little sens for a kernel under GPLv2 to maintain an internal kernel space ABI for drivers (and I'm not even sure Linus would qualify with the licensing, but maybe I'm more moderate than he is). Ok I'm aware there is a mess at least on the Android side, but maybe the majority of it is questionable on licensing grounds to begin with (but the Linux Foundation is particularly lenient on licence compliance, btw, not surprising when you see the list of corporate members, and for some of the main ones their past practices - hm VMware hm...) And that being said, I would be curious to see tons of old Windows binary only kernel space drivers continuing to run on modern systems, or ironically even some user space drivers (IIRC, printer drivers are userspace but 32-bits ones do not work on 64-bits systems)... Ok there is more binary compat for a few major versions if you are lucky. But then MS can always randomly requires WDDM 2 for its next OS anyway. In the end, some old and/or exotic hardware work better (or at all) on recent Windows while some old and/or exotic hardware work better (or at all) under recent GNU/Linux distros, but I'm quite unsure this has anything to do with the precise kernel space API & ABI policies. What does not usually work is attempting to project a model on something that has vastly different premises. So yes, licensing can influence technical decisions. If your ecosystem is vastly built around binary only vendors, a more stable ABI is vastly more valuable than if you ecosystem is vastly built around source only free software vendors, AND pushing for in-tree integration on top of that...
- smoldesu 5y agoNone of this is particularly wrong, but none of it is particularly threatening, either. Google isn't going to fix API breakage by introducing "another competing standard"[0], and they're certainly not going to solve backwards-compatibility with it either: which is becoming an increasingly big question in the sector. Yes, Fuscia can promise a better world, but who's going to get onboard with Google? Certainly not the majority of FOSS developers, who have effectively nothing to gain by abandoning a well-supported, mature ecosystem. It might have potential to replace Android, but only because Google's repeated bastardization of the codebase has lead to a pretty unsustainable system. > It just won't be Linux, because its architecture was never suited for it. Linux was designed to be abstracted over, and extended for any number of use-cases. It certainly does a better job of this than Windows, which has a terrible habit of hiding things in system registries, creating directory structures that don't make any logical sense, and building completely un-automatable system utilities (ever heard of someone's Windows ricing script? exactly). MacOS is literally just BSD lugging along 50 tons of XNU zombie code that it will someday replace. Ask most developers what they'd add to MacOS, and 9/10 responses are going to be a feature that already exists on Linux (good package manager, performnant docker support, updated coreutils, you name it). So in a way, the current "leaders" are still following in the footsteps of giants. Unless you have any better suggestions for a desktop metaphor that nobody else has though of yet, I don't really see any way that the status quo could be improved. [0] https://xkcd.com/927/ https://xkcd.com/927/