Post B5zpqJYsT8DJRA0dai by collappsar@fediverse-lite.com
 (DIR) More posts by collappsar@fediverse-lite.com
 (DIR) Post #B5zoenFSAWOO4zrlVQ by crunklord420@clubcyberia.co
       2 likes, 2 repeats
       
       I find it kinda crazy when people put on this whole show about how Xorg is deprecated or whatever but in reality it's works perfectly fine.Meanwhile Wayland has objectively, measurably and significantly worse latency than Xorg. Not to mention buggy.Like, I'm just gonna keep using Xorg. This isn't a political stance. It's just better, objectively so, I don't what else to say.
       
 (DIR) Post #B5zpqJYsT8DJRA0dai by collappsar@fediverse-lite.com
       0 likes, 0 repeats
       
       @crunklord420 You and everyone else who isn't retarded who has tried Wayland. Seven buhjillion years of development and it's shit. XLibre is the future.
       
 (DIR) Post #B5zqk6j5NSelqUO8ES by Spooke@detroitriotcity.com
       0 likes, 0 repeats
       
       @crunklord420 do you think you'll end up switching to xlibre later when the xorg team finishes their final lobotomy on x11?Since I believe they plan on removing a ton of code written by the head of xlibre when he was trying to save x11 before he just made his own fork.
       
 (DIR) Post #B5zqk7WiOwM6KPblaa by crunklord420@clubcyberia.co
       1 likes, 0 repeats
       
       @Spooke I look at xlibre every once in awhile. I see a lot of code clean up. I just don't see anything that is an objective reason to switch.If they took the time to profile and benchmark their code versus Xorg, showing a perf difference, I'd switch. It might be faster simply by reducing cache misses.There's nothing wrong with the direction mutex is going (clean up) but as an end user it doesn't really mean much. Xlibre is important for the ecosystem.Wayland is clearly not the solution. It might be the biggest, longest, failure in FOSS, ever. Just an utter waste of effort. It's never going to get there. It's flawed architecture, flawed design choices. It was written in an era of implicit sync and now, 20 years later, is objectively antiquated by the hardware. "It's just a protocol" is also a massive failure decision.
       
 (DIR) Post #B5zr8sy5fNK6PpDns0 by Inginsub@clubcyberia.co
       0 likes, 0 repeats
       
       @crunklord420 @Spooke xlibre supposedly solved the screen tearing issue, but i haven't seen any screen tearing in 10 years of using xorg + nvidia
       
 (DIR) Post #B5zr8tF6e6vzGbBOOO by crunklord420@clubcyberia.co
       0 likes, 0 repeats
       
       @Inginsub @Spooke screen tearing is a future. Literally, Wayland adding tearing as a feature. Too bad it only works in exclusive full screen mode. So you can't enable tearing on a desktop. The cursor sprite is also baked into the framebuffer. That's why the cursor always feels soupy on Wayland.
       
 (DIR) Post #B5zr9kq9N73dUpvDzU by crunklord420@clubcyberia.co
       0 likes, 0 repeats
       
       @Inginsub @Spooke feature*
       
 (DIR) Post #B606T1QFRTwvjvS5Eu by mike@libertynode.net
       1 likes, 0 repeats
       
       @crunklord420 my web browser randomly stopped launching under Wayland last fall and, despite my best efforts, I still can’t figure out why. Nothing I do solves the issue — including completely removing the browser and reinstalling. So I’m using Xorg. It works great.
       
 (DIR) Post #B606Y8rrBjOEHLo6me by crunklord420@clubcyberia.co
       0 likes, 0 repeats
       
       @mike it's literally just like that, and then they'll gaslight you telling you Wayland is "ready". They're just lying to people telling them that it's "the standard" and has fixed all the problems, it isn't, and they haven't.