Global Feed Post Login
Replying to Avatar ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

can you actually tell me what exact things that wayland does that X doesn't?

as far as i have been able to surmise from years with this shit there is one thing:

scaling UI according to display

this is actually a problem with the UI library, and not with X

literally wayland can't do night mode properly, because it doesn't have this feature

suprise information for you dickwads, in-memory tty (aka socket) is , you know, fast as memory, which is way faster than your screen pumps pixels (it's how fast your CPU can copy memory around, which is over 14gb/s, last i tested it about 5 years ago)

there is NO technical reason for wayland, at all, they just made this shit up and split the whole FOSS dev community to waste their time on either side of this divide for a protocol that is 6 of one and half dozen of the other

you may be surprised to learn that ios and android don't use wayland

no, really!

Avatar
HERMETICVM 1y ago

Of course iOS doesn’t use Wayland, it’s a completely different kernel/architecture/OS. Android’s window server is SurfaceFlinger, written in Java, no Wayland/Xorg here either.

Wayland has native support for input handling, does direct compositing, is GPU optimized, HiDPI + multi display support out of the box.

If you think there’s no technical reason for Wayland, you’re wrong.

Reply to this note

Please Login to reply.

Discussion

No replies yet.