3 ms·
> The blog post's author ignores that the GNOME project isn't willing to support basic interoperability with other software, and instead wants to make a GNOME-e
by znpy 4y ago
> The blog post's author ignores that the GNOME project isn't willing to support basic interoperability with other software, and instead wants to make a GNOME-exclusive ecosystem.
Does it, though?
"My way or the highway" fits very well in this context. "My way or the highway" can also be interpreted as "we don't give a single shit about other software and other people, and we don't care about interoperating with them".
Basically GNOME is living in and pushing a world where there's only GNOME.
And this is where things get tricky and I feel for the supposed "haters": so now you (GNOME) are a big project and you're pushing your own incompatible and non-interoperable stuff. Some projects will adhere, some won't, for any reason.
So now if I'm using anything not GNOME my desktop experience is broken, because software that assume GNOME is running won't work well (if at all) in other environments.
It just wasn't this bad before GNOME3 and this mentality shift.
- QUrprUd1nCeicw 4y ago>Basically GNOME is living in and pushing a world where there's only GNOME. No, that's false. I can't see why you'd even think that. GNOME wouldn't be using Wayland at all if that were true. GNOME uses standards where they make sense, this one optional non-standard part of Wayland just happens to not make any sense for GNOME. They don't have any issue with the rest of Wayland.
- chris_wot 4y agoIt’s not false. Not supporting decorations actively causes problems for non-GNOME software.
- QUrprUd1nCeicw 4y agoNo. How would that even make sense? If you have no GNOME-related software on your computer at all then it won't affect it.