It’s pretty crazy how their “solution” is “discord should have talked with us” no the fuck they shouldnt. Should they involve KDE and the Mint team as well then?
Should they involve KDE and the Mint team as well then?
Yes. That’s what Wayland is all about, desktop, toolkit and application developers coming together to define standards for features they need.
Sebastian’s comments lack empathy and understanding a lot, but he is mostly right. This attitude that you need to work around the OS provider might be necessary with Apple or Microsoft, but it’s (generally, with a few exceptions) severely misplaced in the open source world.
Exactly this. When I was writing up discover overlay i saw their stance “make it an extension” and decided I didn’t have time to rewrite from scratch to appease Gnome. There’s a workaround or nothing.
I do wonder what the “end result” of this is going to be. Plenty of people use GNOME, most of who don’t know anything about this bullshit.
At some point I expect Wayland or other random projects to just get loads of people complaining shit doesn’t work with GNOME. But what are they going to do then? Keep (rightfully) blaming the GNOME team and tank all the complaints, or actually try to tailor a fix for GNOME?
Personally I hope they don’t, but then I don’t use GNOME either.
It’s pretty crazy how their “solution” is “discord should have talked with us” no the fuck they shouldnt. Should they involve KDE and the Mint team as well then?
Just properly implement the spec ffs.
Yes. That’s what Wayland is all about, desktop, toolkit and application developers coming together to define standards for features they need.
Sebastian’s comments lack empathy and understanding a lot, but he is mostly right. This attitude that you need to work around the OS provider might be necessary with Apple or Microsoft, but it’s (generally, with a few exceptions) severely misplaced in the open source world.
As I have understood there already is a spec for that: https://wayland.app/protocols/wlr-layer-shell-unstable-v1
I think the KDE team is against the spec because of security issues, but they still implemented it.
Exactly this. When I was writing up discover overlay i saw their stance “make it an extension” and decided I didn’t have time to rewrite from scratch to appease Gnome. There’s a workaround or nothing.
I do wonder what the “end result” of this is going to be. Plenty of people use GNOME, most of who don’t know anything about this bullshit.
At some point I expect Wayland or other random projects to just get loads of people complaining shit doesn’t work with GNOME. But what are they going to do then? Keep (rightfully) blaming the GNOME team and tank all the complaints, or actually try to tailor a fix for GNOME?
Personally I hope they don’t, but then I don’t use GNOME either.