← Home ← Back to /g/

Thread 106369707

5 posts 8 images /g/
Anonymous No.106369707 >>106370097 >>106370667
>Wayland is intended to solve X11's problems. The X11 architecture requires a lot of messaging. The X server sits between the clients and the Window Manager. It also sits between everything and---via the kernel---the graphics hardware. The volume of messaging can lead to latency and a laggy, jumpy visual experience.

>There's a large code base too. There's the server application, the Window Manager application, and the X11 library that clients use. The larger (and older) your code base is, the harder it is to maintain , and the more you will struggle with legacy code.

>By changing the architecture, Wayland has modernized and streamlined the code base, giving performance benefits and improved security.
Anonymous No.106370097
>>106369707 (OP)
If Wayland had a Window Manager concept we would have switched by now
Anonymous No.106370111 >>106370199
So does the codebase magically get harder to maintain over time? Do you need to do 5 more CAPTCHAs for every year old a codebase is?
Anonymous No.106370199
>>106370111
uhm lost technology o algo
Anonymous No.106370667
>>106369707 (OP)
> messaging, fixed?
None of that is true.
Wayland is all about messaging, which never worked over waylands lifetime, and only half-assed fixed recentlyโ€ฆ. Itโ€™s not there now, never will be, snd rapidly getting worse.