Xorg might as well not exist as a dedicated display server. Basically all of what made X11 into what it is has been abstracted to the point of meaninglessness. Mouse input is shared with Wayland through libinput. Keyboard input is shared with Wayland through XKB. Video output is shared with Wayland through DRM. Rasterization is shared with Wayland through EGL. All that remains is a bunch of thin wrapping separating the two.X11 is already dead, we just don't know it yet.
Wayland is perhaps even more niggerlicious than systemd.
>>110361347gaylanduse tinyx,xlibrefbdev will live forever in embeddedor go deepthroat fagdesktop consortium
>>110361356Niggerlicious is voodooXorg is voodoo, it's a mudhut skyscraper of engineering
>>110361928it just works
for me it's whatever comes with my distro by default (x11)
Wayland and X both suck
>>110361347You're describing why wayland might as well not exist
Wayland sessions support basic modern features.
>>110361347Isn't the mouse (cursor) support on Wayland still much worse due to a stupid design that can't be changed?
>>110361347Wayland has mandatory compositing, x11 does not.
X11 is trash engineering-wise and kwin-wayland already outperforms anything X11 ever had. More than half the people shitting on Wayland probably are clinging to their autismo WMs. Wayland isn't perfect but it's poised to be faster and much simpler
>>110361356Because it just works?>>110361938Except for sometimes.
>>110362842It can't be "faster" because of compositing and it can't be "simpler" because its design that enforces diversification and fragmentation.
what is window maker
>>110362878You don't want compositing? What year is this? There's a protocol for toggling VSYNC. You can still run like embedded stuff straight on DRM/KMS for those cases.Fragmentation, yes, but that will be solved with a library a bit more generic than wlroots. Right now it's 95% (wlroots, kde, gnome)
>>110361347ok but im still using it hehe
>>110362842Why should I switch WMs for some nebulous bullshit?
>>110362909>You don't want compositing?No
>>110362935WMs are for people new to Linux, or tistics
>>110362909I don't care about compositing. I would rather not have it. I don't want some zesty program going transparent or whatever other stupid shit compositing enables.>>110362947Yes, I'm autistic.
>>110362963>Yes, I'm autistic.Might want to get some meds for that, buddy.
>>110362974No thanks. My WM soothes my soul however.
>>110362982You realize autism is a disorder, right? It's not a "difference", it's a problem.
>>110362992So what?
>>110362799At this point just reverse engineer WDDM
>I want tearinglmfao
>>110365249Its not about the tearing its about the latency. vsync = lag
>>110361347x11 is a network centric desktop bus enabling personal distributed computing
>>110362842>clinging to their autismo WMswndow management policy belongs in specialized daemons the users write in their snowflake languages
Wayland has been "replacing" X11 for 15 years now. In that time they could have done a full code audit of X11 and bring it up to scratch and had a decade to spare.
>>110366324No tearing is better than tearing on your desktop. There is no scenario on your desktop where a buffered frame is meaningfully affecting your usage unlike tearing. This isn't anything to do with x11 or Wayland either.
>>110361347You know that AI is dying because we are going back to Wayland vs X slapfights.
On wayland if 1 of your program runs at 3fps your whole desktop runs at 3fps
>>110366473When I click my mouse of type a letter on my keyboard I don't want the computer waiting around to draw it sometime later. I want it on the screen as soon as possible. Compositing is an abomination, if my application executes a drawing command in response to my input I want that drawing command executed immediately. Vsync something an application should ask for, not something forced upon it.
>>110361938This. I'll switch to Wayland when everything just works no matter which WM I'm using.
>>110362842Go open Libreoffice or Kicad in Wayland. It's fucking unusable.It's designed for running Android apps and nothing else.
>>110362842Test Wayland vs Xorg on a 20 year old laptop and your "Wayland is faster" lie falls apart immediately. You need absurd levels of parallel compute power run Wayland.
>>110366555>uses 20 year old laptopYou need help
>>110366587>it's not slow buy a new computer
>>110366555I think Gnome used to be slower on Wayland if that is your benchmark.
>>110366521You aren't affected by a buffered frames worth of latency when using your desktop. There are zero tasks in existence where this is impacting you in any humanly observable way. Tearing however is immediately perceptible and isn't beneficial to anyone. If you can think of some scenarios you're welcome to demonstrate it.
>>110362909> You don't want compositing?Exactly.> What year is this?2026. Compositing is still useless eye-candy, yes.> There's a protocol for toggling VSYNC. Tearfree in xorg.conf. Bye.
>>110366973>Tearfree in xorg.conf. Bye.Mom cancel my meetings.
>>110361347What you are describing sounds more like wayland issue than xorg issue.
>>110362799use xorg until arcan is ready (two more years)
>>110366383>Wayland has been "replacing" X11 for 15 years now.18 years, so actually it’s closer to 20 years failing to do so>>110366383>There is no scenario on your desktop where a buffered frame is meaningfully affecting your usage unlike tearing.you say that because you never need your latency to be lower>>110366777>You aren't affected by a buffered frames worth of latency when using your desktop.you aren’t me so you don’t know thatand I don’t need to justify what I want my computer to doMY COMPUTER SHOULD DO WHAT I WANT AND I DONT WANT IT TO COMPOSITE ANYTHING PERIODX allows me to control my computer the way I wantWayland does not>Tearing however is immediately perceptible and isn't beneficial to anyone.LMAO go play some FPS games uncanything that benefits from faster output benefits from tearing, because tearing means having the image displayed to you at the same time it’s being drawn
>>110367090>you aren’t me so you don’t know thatPost some results from human benchmark and demonstrate that to me. >LMAO go play some FPS games uncYou can play games with complete frames without tearing and buffering frames you tech illiterate retard.>>If you can think of some scenarios you're welcome to demonstrate it.I explicitly asked you for some examples where having buffered frames on a desktop has some perceptible impact and you couldn't think of a single one.You may now continue your spergout.
>MOOM CANCEL MY MEETINGS>XORG BROKE AGAIN>IN THE END IT DOESNT EVEN MATTER
>>110362799wayland is 18 years old, we need to start from scratch
>>110362799Mir
110367153110367024samefag making shit up like a trans woman from india
>>110362842X11 without a compositor is still smoother than any wayland compositor, even in fullscreen games
>>110365249The xorg server enabled TearFree option by default 4 years ago
>>110371336There is zero difference between Xorg and Gamescope from all the testing I have done. All other Wayland compositors do have flaws, though.
>>110361347When Wayland can restore windows where I left them in the previous (right screen and position), which X has been able to do for at least 10 years, I'll consider switching
>>110372293>There is zero difference between Xorg and Gamescope from all the testing I have done.Proof?Also isn't gamescope just DRM/KMS, that doesn't use Wayland at all. In theory it has lower latency than Wayland and X11.
>>110367153>*mpc still playing linking_park.flac in console because it doesn't need graphics*
>>110372564this one is so fucking annoying, holy shit
>>110366479Fucking finally
>>110361356fpbp>>110361900Unfortunately Xlibre has failed. The Tango-Artix debacle was the final nail in the coffin.I'm setting my sights on Phoenix. His only mistake so far is being autistic enough to host the code on a personal cgit instance.https://git.dec05eba.com/phoenix/about/
>>110361928>implying wayland isn't voodoo despite being fully dependent in freedesktop's garbage software and systemd to properly work
>>110373505what abouthttps://github.com/joske/yserver
>>110371347TearFree and Wayland both flip on vblank. There is no difference.
>>110361347yep. it's just inferior wayland at this point.why waste the indirection?
>>110376074Yep, thats what im saying.
>>110372600>Proof?I have a Pixel 8 that can record 240 FPS and accurately measure latency from mouse click to photons.>that doesn't use Wayland at allYou can force Wayland, but it uses XWayland by default.
>>110373505>The Tango-Artix debacle was the final nail in the coffin.I didn't even know Artix existed until that happened.
>>110378258Which shit hole is this?
>>110378357That's a weird way to say SOVL.
>>110378393>>110378357But to answer your question, it's a country in the Mediterranean with a blue and white flag whose people historically underwent a genocide that is estimated to reach a kill count of 7 digits.
literally developed by the same niggasstop with the retarded tribalism
>>110362842> outperformsIt’s the opposite. Wayland doesn’t outperform anything.
>>110378258Vgh... Soul
>>110361347having switched to wayland a year ago, it's much better for my gaymen. however, i'm still incredibly disappointed in how (((freedesktop))) deliberately held back development in favor of wayland in an attempt to silently kill Xorg off. for people that need it and want to keep supporting Xorg, I think Y Server and XLibre are great projects. I may even switch back someday depending on how some of the modernized rewrites go.
>>110378913> much better for my gaymenYou’re not a gamer. You’re also illiterate.What does “better” mean? Both wayland and X11 expose rectangular areas on the screen which GPUs use to display graphics. Wayland does no compositing here and is unaware and uninvolved in this process. Just like X11.
>>110375840Honestly my kneejerk reaction would be to spit on this garbage but if it promotes alternative X11 implementations I'm all for it.