8 ms·

Not from inertia, but from the overwhelming hubris of those who aimed to supplant it with something new. IPv6 and Wayland have a lot in common.

eikenberry 4y ago
Wayland seems more in line with Python3 than IPv6. With Valve now helping with the development and nearly all other issues addressed... seems it will be the default on all major distros within the next few years.
- stonogo 4y ago
  X runs on so many more platforms than Wayland, even if every single Linux distribution switched tomorrow there would still be good reason to support X. Python3 is strictly an improvement on every platform, I don't think they're analogous because there really is no good reason to keep Python2 around.
  - kirbyfan64sos 4y ago
    > X runs on so many more platforms than Wayland [...] Python3 is strictly an improvement on every platform, I don't think they're analogous because there really is no good reason to keep Python2 around X runs on more platforms than Wayland because...it was ported to them. Just like things use Python 3 because they were ported to it. This is also understating the reach of X I think: it's widely used in the embedded world, is seeing increasing support in BSDs, and has even been used on macOS (https://github.com/owl-compositor/owl https://github.com/owl-compositor/owl). People have even used it to embed an entire compositor inside a GTK app (https://github.com/alexlarsson/wakefield https://github.com/alexlarsson/wakefield). That isn't to say that libwayland has a lot of Linux-isms in it, but afaik they're not really structural as much as there is lack of interest to generalize things more. Heck, the protocol-oriented architecture would even make it easier for anything Linux-esque to be removed in favor of alternative protocols.
    - kaba0 4y ago
      Wayland is actually much better for embedded use cases and is actively used by several car companies in their car displays.
      - anthk 4y ago
        Framebuffer+kms+SDL2 (or embedded QT) would be better.
yyyk 4y ago
IPv6 maybe, but Wayland's protocol choices were IMHO caused by that part of the UI stack getting nigh zero resources. So every iteration from XFree86 ended up deprecating and removing features, and Wayland turns not having features into a 'feature'; Actual standards move into Desktop environments where (some) investment was happening. The standard following economics, as it were.

eikenberry 4y ago

Wayland seems more in line with Python3 than IPv6. With Valve now helping with the development and nearly all other issues addressed... seems it will be the default on all major distros within the next few years.

stonogo 4y ago
X runs on so many more platforms than Wayland, even if every single Linux distribution switched tomorrow there would still be good reason to support X. Python3 is strictly an improvement on every platform, I don't think they're analogous because there really is no good reason to keep Python2 around.
- kirbyfan64sos 4y ago
  > X runs on so many more platforms than Wayland [...] Python3 is strictly an improvement on every platform, I don't think they're analogous because there really is no good reason to keep Python2 around X runs on more platforms than Wayland because...it was ported to them. Just like things use Python 3 because they were ported to it. This is also understating the reach of X I think: it's widely used in the embedded world, is seeing increasing support in BSDs, and has even been used on macOS (https://github.com/owl-compositor/owl https://github.com/owl-compositor/owl). People have even used it to embed an entire compositor inside a GTK app (https://github.com/alexlarsson/wakefield https://github.com/alexlarsson/wakefield). That isn't to say that libwayland has a lot of Linux-isms in it, but afaik they're not really structural as much as there is lack of interest to generalize things more. Heck, the protocol-oriented architecture would even make it easier for anything Linux-esque to be removed in favor of alternative protocols.
  - kaba0 4y ago
    Wayland is actually much better for embedded use cases and is actively used by several car companies in their car displays.
    - anthk 4y ago
      Framebuffer+kms+SDL2 (or embedded QT) would be better.

yyyk 4y ago

IPv6 maybe, but Wayland's protocol choices were IMHO caused by that part of the UI stack getting nigh zero resources. So every iteration from XFree86 ended up deprecating and removing features, and Wayland turns not having features into a 'feature'; Actual standards move into Desktop environments where (some) investment was happening. The standard following economics, as it were.