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.

  • Possibly linux@lemmy.zipOP
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    10 hours ago

    This feels more like long time Linux guy digging in there heals because they like the old days

    • nanook@friendica.eskimo.com
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      10 hours ago

      @possiblylinux127 @loutr I like to get work done, some tools are helpful to that end, Rust for example, superior to C in as much as it makes it much more difficult to make mistakes with memory allocation without resorting to the grossness of garbage collection, but when new things only detract from work flow, then yea I prefer the older things that work. When new things benefit it, Rust for example, or the latest kernels in terms of efficiency, then I use them. I don’t like change for changes sake, I like change when it improves things, in my use case, Wayland does not do that.