I can’t believe that these arguments never mention one of the central tenets of engineering: don’t fix what ain’t broke. And Wayland breaks a bunch of what ain’t broke.
I’m complaining it sucks because it breaks “things”.
Also, it’s a “desktop widget”, so this awesome thing that’s so much better should be able to handle compatibility for a simple desktop widget and not keel over and die, right?
Don’t fix what isn’t broken, don’t break what is working.
X is broken in many different ways. It has a huge codebase made to support a poor design that was optimized for machines 40 years ago. No one wants to touch the code base since it is so incredibly fragile plus the original developers are much older now.
In all fairness, it did work for way longer than anyone expected. I doubt the original designers of the X protocol anticipated it lasting this long.
@possiblylinux127@Skullgrid protocol itself is mostly OK. Yes, it have many limitations, but it covers much more desktop needs than wayland/mir/surfaceflinger/etc.
But implementation is really broken.
For example, the way how some extensions override vtable is terrible: overriding functions usually should restore base function in vtable before calling it and and restore back after. Breaking this would break call chain and override function will never be called again.
I think, this is a reason why devs switched to wayland. Nobody want to reimplement x11 from scratch, but exisiting implementation is borked
How much do you k ow about computer graphics and X? The protocol is indeed not ok. It has tons of hacks and is incredibly janky. Doing basic graphics with X is so incredibly awful as you need to jump though tons of hoops.
I can’t believe that these arguments never mention one of the central tenets of engineering: don’t fix what ain’t broke. And Wayland breaks a bunch of what ain’t broke.
Yeah it’s newer etc. people don’t care.
X was broken as fuck and held together by duct tape and zip ties, as long as no one looked at it wrong.
That’s great, now run birdtray.
The shit that relied on it to run, do not work correctly on wayland. Breaking existing shit is what I’m talking about.
It’s a…mail notification??
You’re complaining that Wayland sucks cause it isn’t backwards compatible with your favorite desktop widget?
OK.
I’m complaining it sucks because it breaks “things”.
Also, it’s a “desktop widget”, so this awesome thing that’s so much better should be able to handle compatibility for a simple desktop widget and not keel over and die, right?
Don’t fix what isn’t broken, don’t break what is working.
X is broken in many different ways. It has a huge codebase made to support a poor design that was optimized for machines 40 years ago. No one wants to touch the code base since it is so incredibly fragile plus the original developers are much older now.
In all fairness, it did work for way longer than anyone expected. I doubt the original designers of the X protocol anticipated it lasting this long.
@possiblylinux127 @Skullgrid protocol itself is mostly OK. Yes, it have many limitations, but it covers much more desktop needs than wayland/mir/surfaceflinger/etc.
But implementation is really broken.
For example, the way how some extensions override vtable is terrible: overriding functions usually should restore base function in vtable before calling it and and restore back after. Breaking this would break call chain and override function will never be called again.
I think, this is a reason why devs switched to wayland. Nobody want to reimplement x11 from scratch, but exisiting implementation is borked
How much do you k ow about computer graphics and X? The protocol is indeed not ok. It has tons of hacks and is incredibly janky. Doing basic graphics with X is so incredibly awful as you need to jump though tons of hoops.
That that completely ignores the security issues.