this post was submitted on 22 Mar 2024
250 points (81.4% liked)

linuxmemes

20880 readers
2 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
250
Bell curve with no bell curve (sh.itjust.works)
submitted 7 months ago by [email protected] to c/[email protected]
78 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Shareni 7 points 7 months ago (1 children)

Imagine using a so called modern protocol that leaves you unable to change a WM in a DE

Who needs xorg bloat when you can make compositor devs reimplement it instead and bloat their own codebase lol

[–] [email protected] 7 points 7 months ago (2 children)

There isn't such thing as a WM under Wayland. There are only compositors which make up everything such as the WM, Effects compositor, io etc. To standardize things for smaller compositors things like wlroots exist. Creating a basic compositor using that is around 100 lines of code

[–] Shareni 7 points 7 months ago (1 children)

Yeah, and that was my point: Wayland turns DEs into inflexible monoliths. You trade modularity, customisability, and stability for better scaling, high-end monitor support, and theoretical security.

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

The theoretical security part is what got me "huh 🤨" as well... like "ok, but all of this is planned... or in the works... or it should work... when does the "it does work" part kick in 🤨".

[–] [email protected] 3 points 7 months ago

There are only compositors which make up everything such as the WM, Effects compositor, io etc.

That's the thing i don't like about Wayland.