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
    6
    arrow-down
    7
    ·
    27 days ago

    @possiblylinux127 It is touted as a replacement for X-windows but the PRIMARY ADVANTAGE of X-windows is that you can run a program on one machine and display it on anther making Wayland completely useless in a networked context.

    • Possibly linux@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      3
      ·
      26 days ago

      It is not trying to be a one to one replacement. It is a totally different thing. You are wanting a motorcycle to replace your 2002 pickup truck.

      Also X forwarding is broken for most stuff. It probably will work but it will run poorly and use lots of bandwidth. This is because there are layers and layers of work arounds to make modern hardware and software work on it. The X protocol was intended for mainframes in the 80’s. It should’ve died long ago.

      • nanook@friendica.eskimo.com
        link
        fedilink
        arrow-up
        1
        ·
        26 days ago

        @possiblylinux127 I agree with you, it’s not, but people here keep touting it as such and that is my issue. X-forwarding works great for me, I use it daily. I use it to access servers in my hosting service from my home office. I can fire up x2go if I need a remote console but most of the time a terminal and an app is quicker. I have no issues with lag, I’m sorry for those that do but it is just not a problem for me.