I think the problem with btrfs is that it entered the spotlight way to early. With Wayland there was time to work on a lot of the kinks before everyone started seriously switching.

On btrfs a bunch of people switched blindly and then lost data. This caused many to have a bad impression of btrfs. These days it is significantly better but because there was so much fear there is less attention paid to it and it is less widely used.

  • Nanook@friendica.eskimo.com
    link
    fedilink
    arrow-up
    2
    ·
    6 hours ago

    @hummus273 Waypipe would involve a lot of userland / kernel exchanges avoided by using the kernel based mode setting Xserver. It happens to work well with my hardware. And I don’t see any noticeable latency issues and not all apps work with Wayland hence I have no motivation to change to Wayland and every motivation to avoid it. Sorry if that gets someone’s panties in a wad.

    • hummus273
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 hours ago

      Waypipe has nothing to do with the kernel mode setting driver. The X server code does not run in the kernel. Wayland compositors use kernel modesetting for mode changes, so not sure what your point is? Not saying you need to switch to Wayland, just saying that it covers the use case you described as impossible with Wayland.

      • Nanook@friendica.eskimo.com
        link
        fedilink
        arrow-up
        1
        ·
        6 hours ago

        @hummus273 Yes actually in my case it does. The kernel has an X-server built in but ONLY for Intel graphics and I happen to have Intel graphics. Sorry if you’re not familiar enough with X or the kernel to know that but that is a fact.

        • hummus273
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          If that is the case, then you can probably easily find the X server code in the Linux kernel and send a link? Spoiler: it is not there