2 ms·
I don't get why projects like these don't simply change their design to allow more flexibility and merge into one mega-project. Rather than have Gnome VS KDE fi
by 0xbadcafebee 6y ago
I don't get why projects like these don't simply change their design to allow more flexibility and merge into one mega-project. Rather than have Gnome VS KDE fighting it out, why not simply choose one as a base, and hack it up to allow for the other one's functionality? Both teams could then use a shared codebase, and provide tailored customizations of how to run it. I can't imagine that it's impossible to make GNOME work like KDE, or KDE work like GNOME, with some small code tweaks.
In other words, if you have two different window systems with two different ways to manage a call to a part of the window... just pick one. Then have the "other team" add any missing functionality. Then give it to the app devs, so the devs can make their apps according to the one standard system, so users can use the one standard system and get on with their lives.
How you implement it is trivial technicalities, because, as a user-facing application, the only important thing is the functionality that users want. Getting in the way of what the users want means you don't care about them, and then why should they use your thing?
- sergeykish 6y agoGNOME and KDE are not the only desktop environments on Linux [1]. MATE forked from Gnome 2, much closer than KDE yet they are separate projects. Trinity forked from KDE 3, XFCE is a GTK based project. Imagine same argument for macOS and Windows (if that was possible) — lets merge UI. It would be complete disaster, hated by both camps. [1] https://wiki.archlinux.org/index.php/desktop_environment https://wiki.archlinux.org/index.php/desktop_environment
- 0xbadcafebee 6y agoI would love it if they had the same programmatic interface, but allowed different distributions and customizations of the interface. It doesn't matter how the code works, it matters what the user experience is. So keep the code the same but provide a different user experience if you want. Can you imagine if roads were designed so only specific cars could drive on them, and so in order to have different vehicles, we had to build completely different sets of roads??
- sergeykish 6y agoWe have themes and extensions (different experience, same codebase), we have libinput, X11/Wayland (same codebase). It is the same old question "why many languages, libraries, frameworks?" Can you imagine if engine was interchangeable between car models, planes and ships too? But also appliances, power plants, rockets maybe? You may enjoy Nissan Leaf commercial - it questions only engine type though, not universal transmission. https://www.youtube.com/watch?v=vog7yDmcDNQ https://www.youtube.com/watch?v=vog7yDmcDNQ