I use Windows btw

  • LuckyLu@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It’s definitely less resource-intensive, but that hardly matters on modern hardware unless you’re doing insanely fast computations and need every spare resource.

    As for more efficient, that heavily depends on what you’re doing. It’s mostly suited to programmers and maybe some writers, but if you’re looking to do graphic design, animation, anything like that… fuck no. Just no.

    • mafbar@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      That’s true though, if I use any modern hardware, I’m not really going to suffer performance penalties whether I’m using GNOME or KDE as compared to LXQt or XFCE.

      I’ve actually never used a tiling window manager, so I don’t really know how unsuitable it is for a creativity-based workflow like needing to design graphics or animation or video editing. Can you tell me why it’s troublesome to use TWMs (or any WMs?) for that kind of work? This is just out of curiosity though, since I don’t do that kind of work.

      • LuckyLu@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I have barely used them, so I’m not the best at explaining, but for me it boils down to a number of things.

        First, TWMs are meant to work with keyboard shortcuts more than with any mouse input. Easy for those to conflict with the shortcuts of your app.

        Second, compatibility might be an issue if your TWM doesn’t use a normal compositor. I don’t know how well something like Blender would render its UI on a TWM.

        Third would be that a lot of creative apps are not meant to be tiled by the system and have their own solutions for window management, which could conflict with the TWM.

        I’m sure there are more reasons. I can’t think of them just now.