6 votes

Topic deleted by author

2 comments

  1. streblo
    Link
    I work in embedded linux and one thing we've begun to notice is that most SoM manufacturers are moving away from x11 or even framebuffer support towards Wayland with their distributed Yocto...

    I work in embedded linux and one thing we've begun to notice is that most SoM manufacturers are moving away from x11 or even framebuffer support towards Wayland with their distributed Yocto layers. It's definitely easy to see which way the wind is blowing and I would expect contributions to increase as more companies get pushed into Wayland. On a personal note, I myself have been using Wayland on the desktop for the last two years without much hiccup. I can see why BSD folks are having a hard time -- the ecosystem does feel pretty attached to linux at the moment.

    1 vote
  2. vord
    Link
    The author brings up some good points regarding current Wayland implementations. But since Wayland is a stripped down protocol, it should (in theory) be easier to write alternative implementations...

    The author brings up some good points regarding current Wayland implementations. But since Wayland is a stripped down protocol, it should (in theory) be easier to write alternative implementations which are still compatible.

    While not directly related to the post, it always feels like the people deriding Wayland for excluding features that were present in X11 are also are the ones deriding systemd for being more than just an init system.