853
be rule (lemmy.nz)

transcription: be me, closeted transfem, have computer science degree, family constantly bothering me with tech problems, always dumb shit like not restarting computer or googling error messages, lightbulb.jpeg, come out to family, get disowned as expected, they never contact me again, dont have to deal with their dumb it problems anymore, mfw, should have done this years ago.

you are viewing a single comment's thread
view the rest of the comments
[-] Jankatarch@lemmy.world 39 points 1 week ago* (last edited 1 week ago)

Hii! trans girl here who messed with libwayland and x11 a bit before. Wayland has the compositor and server combined so there's less overhead.

Here's the X11 architecture.

3 X clients connected to the X server, a seperate compositor is too, and a box with KMS, evdev, and kernel are also independently connected

Let's say you pressed the fullscreen button with your mouse:

  1. First the evdev driver will get your mouse input and send to X server.
  2. X server tells the X client that someone just clicked so-and-so coordinates. X server HAS to assume which client because windows may be on top of each other, and only compositor (our renderer) calculates those. Often server assumes wrong tho so has to try everyone one by one.
  3. The X client re-arranges everything after fullscreen, sends X server what changed.
  4. X server calculates which area the change was in, sends to compositor asking they render that area again.
  5. Compositor calculates that all windows fall behind the fullscreen window, renders the one on top, sends X server what changed.
  6. X server does the graphics displaying part from there.

Now here's Wayland architecture

Box containing KMS, kernel, and evdev connected to Wayland compositor connected to 2 wayland clients

  1. You press fullscreen with mouse, evdev sends it to Wayland compositor
  2. Compositor knows what windows are where, knows which client was clicked. Sends it to them.
  3. Client realizes they are being fullscreened, they reareange AND render their own changes themselves too. Client also directly writes to a shared buffer they have with the compositor to not waste time sending their render results.
  4. Compositor already has the changes in shared buffers, recomposes the screen based on all the clients' new rendering.

So now some redundant steps are gone, and also the shared buffer is nice too. Overall, wayland uses less resources for more work.

Technical writing if you'd rather read that. Also source of the images too. Hope this helps! (Sorry for my poor English if I made any mistakes)
https://wayland.freedesktop.org/architecture.html

Note: In defense of x11, I heard someone on lemmy mention it has more accessibility features supported currently.

[-] tf1@sopuli.xyz 7 points 1 week ago

also the x11/xorg (don't know which) codebase is a big mess, and the people working on it wanted to start from scratch

[-] Ephera@lemmy.ml 7 points 1 week ago

Damn, I was already on the Wayland train, because slightly smoother, but I didn't know X11 was so wonky...

[-] edinbruh@feddit.it 3 points 1 week ago

I heard someone on lemmy mention it has more accessibility features supported currently.

For now. But both GNOME and KDE are working on it

this post was submitted on 03 Nov 2026
853 points (99.1% liked)

196

7219 readers
2953 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 2 years ago
MODERATORS