> Linux is not a singular entity. There is no standard Linux UI. There won't ever be a standard Linux UI so that's a meaningless thing to worry about. That's t

> Linux is not a singular entity. There is no standard Linux UI. There won't ever be a standard Linux UI so that's a meaningless thing to worry about. That's the entire problem! We have ONE standard kernel, granted with a few modifications on Android. We have one standard C library (several implementations for edge use cases). We have one standard C++ runtime (and the clang libc++ is completely compatible). On every layer of the stack we have one standard, with one standard implementation, except when you reach the top when it becomes and ungodly mess. Nothing really interoperates in a standard way. Hell, it took until 2006 IIRC to settle on one standard audio API - pulse. Before we run off to reimplement everything yet again, there should be standards of interoperability in place. For example, why does Firefox not use the KDE open file dialog? I run KDE, I expect to get the KDE open file dialog not the GNOME one. Oh, it's because there's no standard "open a file" API call. Because every time someone reinvents the desktop, they reinvent it from the ground up without trying to interoperate. This is probably why Firefox also doesn't always obey my file associations set via Dolphin, the KDE file browser. Yes, let's have unlimited customizability, but we need standardized interfaces for basic desktop functionality. A forest, rather than a dozen walled gardens.