erotador
196transcription: 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.
I hope you also sent them this meme as a last message.
Modern problems require trans solutions
Being yourself is the perfect filter for people who doesnt fit :D
closeted transfem
computer science degree
Why saying the same thing twice?
https://i.sciencehumor.io/2025/06/cd09914c60b4bbc2446300a8e949bad71b45b1d3fb21bcffd88cd0f524adb3ba.jpeg
Some of them are not closeted?
Fair lol
To any trans girls who decided to peek into the comments:
What's actually the difference between X11 and Wayland? I always hear the latter is the more modern standard and that I should be switching to it, but also it feels like X11 is just way more stable and well supported, why can't I stay on there just a while longer?
Calling x11 well supported at this point is like calling a 1977 Pontiac firebird trans Am. Well supported
It's liked, there's lots of information about it. But any real support died for fucking ever again. And the only people claiming otherwise have their heads buried deep in the sand.
Even calling it stable has a lot of ifs to it at this point. If your on a old system, only doing basic things, with a well trodden and documented track record. Then yeah it's more solid then a block of solid rock.
But half the reason it's "stable" is because it's a duct taped mess that is basically a bat shit insane house of cards one bad day from falling apart.
But we know every fault, trick, and piece of duct tape. So the chance of it falling apart is almost zero.
Waylands problem tends to be it just refuses to hurry the fuck up and actually get any real work done. But what does get done tends to get done more right then x11 and quickly fixed up as issues come up.
So long as the gnome team shuts the fuck up and doesn't interject. If they do then all bets are off.
I think the main stability issues that people encounter with Wayland are because of one of two reasons:
- Dogshit nvidia drivers that dont support Wayland
- Wayland has added security features, and the program you're using doesn't support them.
The main security features people get hung up on are:
- screen sharing
- clipboard
- stealing window focus
There's some other problems, some more stupid than others
- GNOME refuses to support clientside decorations, the Wayland specification doesn't require it, so any software that wants to work in a window and support all major DEs needs to have code to draw its own titlebar
- I think screensharing still has some problems that haven't been settled yet, not sure if there's a way to capture an application and only its audio, might work worse for preserving capture configuration across restarts
- Global hotkeys have a somewhat stupid issue, and OBS refuses to support them - the issue is that OBS supports having multiple profiles and wants to be able to have different hotkey bindings for every profile, and there's no good way to do that right now.
- Global hotkeys also have a controversial side in that there's no consistent way for applications to know what keys are bound to hotkeys, and application developers want to display hotkeys inside application settings and allow users to change them there. And that's an issue because Wayland developers want to ensure Wayland isn't restricted to only typical keyboard, mouse, gamepad setups, and things like global hotkeys can be bound to things like touchscreen gestures without needing workarounds like emulating keypresses.
- Another issue in a similar vein is window positioning. Some software opens multiple windows, and its developers want to be able to position those windows in a layout. On the other hand, Wayland developers don't want to limit software to rendering on rectangular 2D screens, and don't want software to be positioning windows with 2D coordinates like that, and instead have a way for software to indicate to the compositor more semantically how windows are meant to be laid out. I don't think they've worked out a solution yet.
I respect Wayland trying to avoid backing itself into a corner where expanding future support is going to be a mess because they rushed to get something out, but it does take a long time, and we're not there yet.
On a somewhat random note, I have a screen with probably crappy HDR support, and previously on Plasma I tested it a couple of times for fun, but there wasn't much support from software and the colors were off. Recently I hit some weird bug where my colors were just off (on SDR), looking greenish, decided to try turning HDR on and off to see if it'd help. After turning it on, I realized the colors look fine, after running the calibration it looked the same as it would in SDR, but just with HDR support. I tested it on YouTube videos, not sure how to tell how well it's working, but it's a nice "huh, guess we got there" moment, where there's another thing that now just seamlessly works for me.
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.
Let's say you pressed the fullscreen button with your mouse:
- First the evdev driver will get your mouse input and send to X server.
- 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.
- The X client re-arranges everything after fullscreen, sends X server what changed.
- X server calculates which area the change was in, sends to compositor asking they render that area again.
- Compositor calculates that all windows fall behind the fullscreen window, renders the one on top, sends X server what changed.
- X server does the graphics displaying part from there.
Now here's Wayland architecture
- You press fullscreen with mouse, evdev sends it to Wayland compositor
- Compositor knows what windows are where, knows which client was clicked. Sends it to them.
- 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.
- 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.
I heard someone on lemmy mention it has more accessibility features supported currently.
For now. But both GNOME and KDE are working on it
Damn, I was already on the Wayland train, because slightly smoother, but I didn't know X11 was so wonky...
also the x11/xorg (don't know which) codebase is a big mess, and the people working on it wanted to start from scratch
X11 is a decades old protocol. People kept saying "can you please support this one new hot thing?" and the devs were like "fuck, let me think of something. [furious duct taping] There, it works! Kinda."
Yes, it's "stable", by some definition of stable anyway. Also with loads of technical debt. You can keep extending it, but it's a painful, janky process every single time.
Wayland is a clean break from all of that with a more modern approach. But, of course, it's newer, and with a clean break you want software to be ported over to best utilise Wayland, and there's going to be a lot of work until you can finally drop the X11 compatibility layer.
But I don't think there's anything wrong with the idea of X11 backwards compatibility at the moment. Or staying with X11 until Wayland runs on your hardware. But when the app toolkits eventually support both, I think targeting new software exclusively for X11, or further development of X11 itself, is starting to look less and less sensible as time goes on.
One of my personal gripes is no protocol-level equivalent to headless, multi-monitor VNC. With X11 it just worked regardless of DE, on Wayland this functionality seems to have been thrown downstream to DE's to implement, making the current landscape a nightmare.
Not a trans girl but Wayland and x11 are display server protocols. A display server is the program that draws windows and stuff on the screen (plus, does some other things related to desktop environments), and these protocols are how the applications control their windows.
X11 is very old and based on obsolete ideas. It is a less efficient protocol than Wayland, and has many security issues. The most prominent one is that any unprivileged program can read the entire screen and record any input. X11 development has for a long time revolved around a single display server that everyone used, called x.org, this is partly why it developed so fast. However the codebase is a mess because it started so long ago and developed so fast, so it's almost untouchable. That's why modern features like hdr and real multi display support will never arrive.
Wayland is the modern protocol that will replace x11. It is built from the ground up to avoid the mistakes made by x11. Because of this, development is often stuck discussing esoteric scenarios, to make sure everything is perfect before adding it to the protocol. Unlike x11 there is not a single Wayland server, and this is why you will see differences between implementations. Unlike x11, Wayland is designed around modern computers.
Unless you are using something that specifically only works on x11, you should use Wayland.
Not a trans girl but Wayland and x11 are display server protocols.
Found the egg!
Fun fact: a suspiciously sizeable amount of the people working on mesa, freedesktop, and the linux graphics stack in general, are trans or at least queer.
Is it graphics that makes people trans, or are the trans people who make graphics? We might never know
That's just great, as a transfem I now feel I have to drop my current plans, to stop and contemplate if I enjoy making 3d game art because I'm trans, or if 3D game art somehow made me trans. It's not the programming side, but is still the visuals and graphics...
I am 99% sure, if it had to be one of those options, it would be the former. I doubt it's either of the two... And yet, how will we know.
So now I am cursed to I sit and ponder the possibilities
Mystery! And how do the furries fit in?
They are in the airports
And the CIA, NSA, FBI, DHS and any security focused gov op
I mean depending on who you ask I'm sure they'd consider furries to be at least one definition of queer.
I mean, furries are mostly just a fandom of people, maybe therians can be included as queers(?) I do not know enoigh about therians to be 100% sure
I was making a wordplay joke using the "older" meaning for queer where it meant "strange" rather than what it's come to mean today. Not necessarily putting furries under the queer umbrella.
That said if I didn't literally know a cis straight furry I'd think they didn't actually exist because every one of the like dozen others that I know is gay or trans.
X11 users are pee drinkers Wayland users are based and awesome that is the gist of it
The other comments explained the differences quite well. I just wanted to mention that whilst, yes, Wayland is the future, and it works great for me, it does still lack some important features. AFAIK, accessibility is considerably worse on Wayland so far, which is why e.g. visually impaired folks fare better with X11. (at least it was that way not too long ago)
Not a trans girl but I can answer. Wayland is just a library with simple interaction with the display. X11 is a suite of programs for displaying the desktop environment. A Wayland compositor has to implement every utility from X11, that is why it can feel less supported.
X11 has some underlying problems like keypresses being served to every application which makes it exploitable for a keylogger.
Trans girl here. I vouch for this.
Also not a trans girl, but Wayland go brrrr. X11 is problematic for me when I game
The biggest benefits Wayland has currently (at least obvious ones to end users) is multi monitor fractional scaling and HDR
why can’t I stay on there just a while longer?
You totally can, though. AFAIK, the security-relevant scenarios where Wayland makes a difference are super esoteric, the performance differences are slight and on most desktop environments it doesn't have anywhere near feature parity, so it's more about which desktop environment you like and how far along it is with developing a Wayland version (if it does so at all).
