• window manager: niri
  • theme: Adwaita (gtk3/4), Breeze (qt5/6)
  • icons: Papirus
  • x74sys@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    8 days ago

    Honestly I don’t really understand what’s wrong about calling them that, I do prefer calling them compositors as well, but to the untrained eye window manager is much more clear, and it’s the existential goal of a compositor anyway (in most cases at least). Just because a spec sheet doesn’t call a game engine a 3D renderer doesn’t mean a game engine is not a 3D renderer, because unless it only renders 2D, it is also a 3D renderer, if you get what I mean.

    • Scoopta@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      7 days ago

      I guess what I’m trying to get at is, a game engine contains a 3D (or 2D) renderer, but that’s not its sole focus. There are other projects which are just that, a game engine is a lot of other things too, physics simulator, audio engine, UI framework, etc. A compositor is similar, it’s a compositing window manager, a Wayland display server, an input handler, etc. It does far more than manage windows. When we look at X11 all a window manager does is manage windows, composition was a separate application, although sometimes the window manager would handle it, input handling was managed directly by the X server. Basically a Wayland compositor is a compositing window manager, and display server combined into one, it’s like a game engine, calling one a 3D renderer is missing out on the vast array of other responsibilities.