Wayland-Protocols 1.7 Breaks XDG-Shell Backwards Compatibility

[phoronix]

Phoronix: Wayland-Protocols 1.7 Breaks XDG-Shell Backwards Compatibility

It was just days ago that Wayland-Protocols 1.6 was released with the additions of XDG-Foreign and Idle-Inhibit. Arriving this Monday morning is Wayland-Protocols 1.7...

http://www.phoronix.com/scan.php?page=news_item&px=Wayland-Protocols-1.7

[starshipeleven]

countdown to flames coming on wayland too because it is breaking stuff that worked fine before "for no reason" so it is evil just like Systemd and PulseAudio and Microsoft has... started.

[duby229]

countdown to flames coming on wayland too because it is breaking stuff that worked fine before "for no reason" so it is evil just like Systemd and PulseAudio and Microsoft has... started.

You're such a moron. You are the one equating wayland to pa and systemd. Idiot. In reality they are very different concepts. So you go right ahead and throw your flamebait, but you are the one that doesn't even understand how the flamebait makes no fucking sense.

[ssokolow]

who cares about breaking backward compatibility who one uses Wayland for real world user case ... but sure for the future we need the best wayland we can get

From what I remember, Sailfish OS and Tizen IVI both use Wayland... but then they're not desktop platforms, so XDG-Shell isn't relevant to their UIs.

[starshipeleven]

who cares about breaking backward compatibility who one uses Wayland for real world user case ... but sure for the future we need the best wayland we can get

Ehm, we are supposed to move to wayland in a (possibly near) future, breaking backwards-compatibility is going to have some effect, if not now, then wen we make the switch.

I was mostly pointing out one of the reasons future trolls will use to say Wayland is bad and evil, though.

I personally think that breaking backwards-compatibility is preferable to keeping turd implementations that affect everyone just because SOME legacy crap can still run. So yeah, if they thought it had to go, so be it.

You're such a moron. You are the one equating wayland to pa and systemd. Idiot. In reality they are very different concepts. So you go right ahead and throw your flamebait, but you are the one that doesn't even understand how the flamebait makes no fucking sense.

Oh hi there! Here, read how systemd adheres to Unix philosophy too and you will understand why I'm saying that http://0pointer.de/blog/projects/the-biggest-myths.html

[boxie]

Breaking backwards compat in an extension marked experimental... kinda what the experimental thing is all about

[makomk]

Honestly, people probably should be flaming them over this. XDG-Shell is the API that desktop applications are meant to use in order to create and manage their windows. They're breaking backwards compatibility for the most basic, fundamental application-facing functionality of a desktop compositor. Of course, XDG-Shell itself duplicates the entire functionality of the core wl_shell API because apparently they had to do that in order to add exotic features like minimizing windows. (Which, given that the justification for Wayland is that X has ended up as a mess of extensions duplicating core functionality, is a little ironic.) Wayland's extensibility story is looking like a huge mess, one that might make EWMH look almost elegant by comparison.