>coordinates are fixed at 16 bits

when i fricking want it for any reason, butthole.

>t. doesn't know about the ubiquitous present-day use of subpixel rendering in fonts, rendering, compositing
Boy you're really dumb!

Literally just did, moron. Read it again but slower this time so your brain can keep up.

lol - post proof that subpixel rendering is used in font rendering? look harder at your screen or type 2 words into google you dumb lazy homosexual.
how about you prove that you're a human with a brain and not some shitty bot or a literal child, otherwise i'll just go ahead and accept your concession and hope the jannies sweep you up in an underage ban run soon.

>im just gonna ignore anything else you reply to me
you need to irrefutably prove this claim in a court of law before i'll believe you and you're legally wrong until then

>a bug caused from this issue
>a bug caused by subpixel accuracy
???
do you even know what subpixel rendering is? i don't think you do. you should stay out of discussions you don't understand, babe.

>you can't post a quantifiable bug or issue raised from the issue you're getting angry about
because you're not asking a valid question, you're asking something nonsensical that showcases your deep ignorance on this topic and any related topic. every time you say this you look stupider to anyone with more than 2 braincells.
having subpixel addressing is necessary for, at minimum, anti-aliased font rendering, a prerequisite of essentially all font rendering systems used in modern computing.
you are not being rational because you're either ignorant or are straight-up a robot.
goodbye.

>having subpixel addressing is necessary for, at minimum, anti-aliased font rendering, a prerequisite of essentially all font rendering systems used in modern computing.

>having subpixel addressing is necessary for, at minimum, anti-aliased font rendering, a prerequisite of essentially all font rendering systems used in modern computing.

irrelevant, the question is what real uses subpixel addressing has.
and also, apparently, the question is what "bugs or issues" do the general concept of "subpixel addressing" .. introduce? create? create in absence? not clear because the anon asking doesn't understand what they're talking about.

Quantifiable bug/issue from a project outside of self-defined text still not provided

>anti-aliased font rendering, a prerequisite of essentially all font rendering systems used in modern computing.
still, homosexual. that's still the answer. it's a correct answer, but you might be too stupid to understand it, even though it's extremely simple.
you're asking for something as sensible as "how many squares fit into the taste of a raspberry"

>Subpixel rendering is a way to increase the apparent resolution of a computer's liquid crystal display (LCD) or organic light-emitting diode (OLED) display by rendering pixels to take into account the screen type's physical properties. It takes advantage of the fact that each pixel on a color LCD is actually composed of individual red, green, and blue or other color subpixels to anti-alias text with greater detail or to increase the resolution of all image types on layouts which are specifically designed to be compatible with subpixel rendering.

https://en.wikipedia.org/wiki/Subpixel_rendering

How does FreeType2 perform Subpixel rendering on X11 if it doesn't support it?

https://wiki.archlinux.org/title/font_configuration#Subpixel_rendering

you can render with whichever accuracy you want, moron, than you have to apply it to grid which is compatible with the fricking monitor. And guess what. They do not fricking have 1/10 pixel you fricking genetic mistake

you seem moronic even as a troll
are distros which use xorg monochrome?

>if indirectly, which would require the system be capable of addressing their individual values on an internal model of some kind
But not at the display server level. Fonts are rendered using freetype (on loonix) and that's where you need to do it.

The display server doesn't render fonts. On X they're often *drawn* using XRender, but it only blits and blends buffers together drawn into some buffer/pixmap by something else (in this case freetype), similar to what a compositor does (and some compositors do indeed use XRender to do their job).
If you want subpixel accuracy you just render your shit using subpixel accuracy. There is no reason for the display server to get involved with this because even if it let you position things at subpixel granularity everything would look like shit unless the covered subpixels were taken into account. Imagine drawing a subpixel sized straight line vertically. It would look like a fricking rainbow if you tried moving that around. So no, that would be useless.

looking at porn but you want to hide the dick and only see the girl

I want to.

To move a window around freely without changing its dimensions. The #1 best use of a GUI. Duh.

I don't care where it was invented you fool. MIT abandoned it a very long time ago. It has been developed mostly by hobbyists since then. And a few companies like Red Hat, like you said. But mainly hobbyists.

Screaming an argument repeatedly just shows that it's wrong. X is maintained by talented professional teams.

moron

u mad

I'm a masculine gigachad, cope.

>I'm a masculine gigachad, cope.

Point to even one troony working on Wayland.

u are

u mad

Nah, just make the middleman library also provide the old library's symbols too. That means all it would need is a rebuild.

Who said anything about changing the function arguments? It takes the same shit but inside the new library you do the voodoo to turn into what you need.

Don't link the old library anymore. Link the new one. The new one provides exactly the same functions with the same arguments but inside those functions they do the coordinate transformation.

That's where the internal bookkeeping of that compat library comes in.

Nobody's gonna use your stupid troonyland.

I will once I start using 8 4k displays or whatever the frick the number is.

Focusing on useless features is one of the reason your precious troonyland won't see widespread adoption.

>troonylander wants to add features nobody will need for decades instead of adding something useful now
Well that checks out.

>the feature is already added
Where is the Discord push-to-talk then?

> did you know that old programs when you move their windows past pixel like 32 thousand they wrap around to negative space
> whoa really?
> yeah lemme show you on my big screen
> wow
> yeah basically the x developers are incompetent
sounds like x gets you laid

They would probably use it for ads so I'd say X wins in that case.

Did your mom drop you on your head when you were a child? Because I don't see how anyone could equate hating ads with being a commie.

>I need to be told what to buy because I am incapable of finding products that I want on my own

10 years ago: the coordinates on my screen don't work. lemme report this and get famous for advancing tech
today: that's deprecated you absolutely have to use gayland now

i-it'll still work on my smart TV

Nope. It's still the standard. It's also done, so no amount of IBM / Red Hat troonery can take it away.

Wayland is smooth, has good scaling, and doesn't keylog. KDE Wayland is the best gaming setup.
It's not political, it's just better.

Bullshit. 150% scaling on KDE Wayland looks perfect and outcompetes any alternative anywhere else to me.
Also Wayland has pixel scrolling while xorg doesn't.

I remember using KDE Wayland and it was by far the least blurry.

There is no changes to the font rendering?

Not him, but no, Wayland isn't slow. You don't give a frick about slow. We all know you're b***hing about vsync despite the fact that you're apparently using A FRICKING 4K DISPLAY that doesn't feature freesync.

Sounds more like you have a GPU problem that can't actually handle the task you're giving it.

>oh it's the classic wayland cope of "you have the wrong GPU bro you gotta buy this exact one for wayland"
Yes. There's something wrong with your setup as you're describing it and you're blaming it on some software that literally doesn't have mouse movement so slow that you can let go of the mouse and watch the cursor move.

I have a Vega 56 and I don't give a shit if I'm using X or Wayland, I just use distro defaults. What you're describing is you, not Wayland.

i'll note the taskbar can be resized down in wayland, of course, but it's set to the same value as on X right now, and the setting persists... so i left it, not wanting to clean up the mess when i return to X

Open issue on gitlab.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/47

>Same bullshit.
Very different bullshit.
>So it looks like you're wrong about the thing you're talking about so you're trying to move goalposts.
I just proved that just because "everybody" is happy with bullshit doesn't mean it's not bullshit.
Different anon, btw.

>You have a you problem and nobody thinks otherwise.
sounds like you're taking me not having a problem by way of not using your meme shitware pretty badly bro

>OP's argument is bad faith and his criticism isn't valid
>argument is literally "OP is lying" and "monitors don't exist"
meds
i'll keep saying it until you take them

bad faith, meds and cope

>someone mentions a usecase you didn't think of
>you're lying you're lying
>someone elaborates on that use case
>you're lying you're lying that doesn't exist lalalallalalalalala everything i think is great and you are wrong
>someone tells you to chill the frick out
>you're lying you're lying you're lying you're lying you're lying you're lying you're lying you're lying you're lying you're lying bad faith bad faith bad faith
anon, it should be fricking obvious to anyone reading this that you need to take the meds and calm down

>you're lying you're lying that doesn't exist you're lying you're lying you're lying you're lying you're lying that doesn't exist
bad faith, take your meds

>https://gitlab.gnome.org/GNOME/gtk/-/issues/3787
kek
gnome developers are truly cut from the same cloth as wayland developers

this explains so much holy shit
the same people who removed the ability to change desktop background modes and use solid colors as a background are in charge of designing the "next generation" of display server kek
no wonder basic shit doesn't work. any real utility is "out of scope"

>On Wayland you can do neither the drop-down thing, nor the hotkey thing! No OSD-like stuff, either. It's hilariously deficient.
This is absurdly wrong and easily verifiable with a simple google search.
https://extensions.gnome.org/extension/1411/quake-mode/
https://extensions.gnome.org/extension/3780/ddterm/
https://apps.kde.org/yakuake/
X11 shills have to resort to lying, as usual.

>load a terminal emulator into his compositor to make this work
Except that isn't what happens.
>You can do anything if you inject it right into the compositor
You're so close to figuring out why X11 is bad. Like, so close.
>None of those things you posted are limited to using Wayland interfaces.
Why would they limit themselves to only using Wayland interfaces? Wayland is not a terminal emulator protocol.
>Show me a compositor-agnostic drop-down terminal that works on any compositor, or at least uses some nonstandard extension other compositors could easily implement.
Moving the goalposts. Why do you need this? Give one valid usecase.

>"I want a drop-down terminal" is a valid use case.
And you already have one.
>Explain why you think you can arbitrate what software other people "need" on their computer. Give one valid reason.
Because I am writing the code and you are not. That is not just a valid reason, it is the *only* valid reason.

It makes no difference to me what the gallery of rubes thinks. If you were qualified to write this code, you would be writing it, and not me. You would have written it 20 years ago. But you didn't. You picked up someone else's old trash and pretended it was gold.

>Except that isn't what happens.
So it uses some proprietary IPC mechanism/interface that lets it sidestep Wayland's deficiency? If some shitty GNOME extension is allowed to do this, why not any other app? What's the point, then?
>You're so close to figuring out why X11 is bad. Like, so close.
It lets you do what the frick you want to?
>Why would they limit themselves to only using Wayland interfaces? Wayland is not a terminal emulator protocol.
Because we are talking about Wayland as a display server protocol, not GNOME or KDE specifically.
>Moving the goalposts. Why do you need this? Give one valid usecase.
You can shove that goalpost up your ass and keep it.

>So it uses some proprietary IPC mechanism/interface that lets it sidestep Wayland's deficiency?
No, it uses wayland.
>If some shitty GNOME extension is allowed to do this, why not any other app?
Any app can do it given the appropriate privileges.
>What's the point, then?
Gnome extensions are privileged functions inside the security boundary of the compositor. Your app is not.
>It lets you do what the frick you want to?
You're so, so very close. Just an inch closer.
>Because we are talking about Wayland as a display server protocol, not GNOME or KDE specifically.
GNOME and KDE implement the Wayland display server protocol. There are some other implementations but they're irrelevant.
>You can shove that goalpost up your ass and keep it.
Then you admit you don't need this. I thought so. Did you know that most computer users on other operating systems can accomplish everything they need to do without some meme terminal? Crazy, right?

>Which protocol?
special gnome protocol.
>What's the mechanism to ask for those privileges?
being a central gnome developer.
>Not only *my* app. *ANY* app I wish to use.
distinction is irrelevant, no such apps work in this circumstance so 'your app' vs 'any app' is the same empty set.
>Show me a drop-down terminal that works on both.
he cannot
>push-to-talk
he will argue ceaselessly that nobody actually needs push to talk before he admits this is a clear deficiency

>what actually happened is: Your code is shit
Hadn't even gotten to the point of sharing my patch yet. I was asking about the nature of the a particular internal function they used, and if changing it to one used in my patch could- in their opinion- cause unexpected results elsewhere or if I'm just being paranoid and I should push it along.
He took this as a personal attack instead of answering the question, which - as far as I can tell - could have been done with "no that should be fine. looks like that was an oversight!"
Worthy of no effort moving forward.

>Who are you talking to? Nothing in your post has anything to do with me.
i'm talking to you.
my post describes you.
you are worthless except, possibly, for your contributions to a failing display server.
you cannot see how valueless you are.

>how many X11 users in this thread wrote Xorg display server code
We don't need to. It works fine as-is for 99.9% of people without needing to patch a ton of bugs introduced by sloppy developers every week.
And when patches are needed, they get in easy. A few days later, "display scaling with this unique hardware combo" is in upstream and getting tested, ready to roll out. No three-year bikeshedding debates about the magnification and coordinate planes and how it can be technically correlated to objective metrics of quality.

>Show me the API that lets you do this.
There is no API. You just enable it.
>How?
Go in GNOME extensions and enable the extension.
>Where is that boundary?
In the compositor. Just like X11 has boundaries in the X server.
>And how?
Have a GNOME extension or Plasma extension.
>That's not moving the goalposts.
Yes it is. You added that requirement on after the fact after you were proved wrong. Heinously wrong, I might add. So wrong that you should be embarrassed, but you're not because X11 copelets are inhuman beasts and feel no remorse, shame or guilt.
>It's reasonable to expect a Wayland application to work on any compositor.
No it isn't. Who said that? Where were you told that?
>If not, then it's deficient and has to be worked around with compositor specific hacks.
Why is that deficient? Some X11 programs only work with some WMs and require WM specific hacks. Is X11 also deficient?
>How can an app register a handler for a key binding?
Why do you need an app to do it? You just register the key binding yourself.
> I'm not even asking for it to bind it anywhere, just to let the compositor know there is something to bind to.
Why does the compositor need to know that? It doesn't. Just register the key binding yourself.
>If it's GNOME specific it's not a Wayland app.
No? It runs on Wayland, it's a Wayland app.
>A drop-down terminal will work the same on Xming, Xdarwin, etc.
Actually no it won't, a lot of fricky X programs like that will horribly break on rootless X servers.

>it only runs on Gnome
Yes, GNOME uses Wayland.
>It's a Gnome app that uses Wayland
Or you could say it's a Wayland app that uses GNOME.
>If you can't start it in another DE and have it run the same way, it's obviously not something that Wayland supports.
Yes you can. Wayland supports it on GNOME. Not hard to say.

>There is no API. You just enable it.
Of course there is an API. How else would it tell the compositor where to place the window?
>Have a GNOME extension or Plasma extension.
But how do you do it with Wayland?
>No it isn't. Who said that? Where were you told that?
So shit's not inter-operable? Sounds proprietary to me.
>Why is that deficient? Some X11 programs only work with some WMs and require WM specific hacks. Is X11 also deficient?
Yes, obviously. Just less so than Wayland.
>Why do you need an app to do it? You just register the key binding yourself.
How do you do this without letting apps be "keyloggers"? Or do you want people to type in some cryptic command line to inform some app that a binding has been invoked?
>Why does the compositor need to know that? It doesn't. Just register the key binding yourself.
How do you bind binding A to action B in app C? You can't do this unless the compositor knows about action B in app C because app C is not a keylogger. So it needs support from the compositor.
>No? It runs on Wayland, it's a Wayland app.
If they were Wayland apps they'd run on any conforming Wayland compositor. Why wouldn't they?
>Actually no it won't, a lot of fricky X programs like that will horribly break on rootless X servers.
Xming isn't strictly rootless. It can run in a window that acts as root window. Dunno about Xdarwin though.

look, i understand that you write display server code, and that you have no job, no friends, no relationships, and no constructive hobbies. i understand that writing display server code exclusively defines you as an individual, and thus your whole world-view is centered around display server code. i get it, i really do.
the thing is, healthy, normal people.. they don't give a shit about what you do. you think it's valuable but it's really, really not. you and your whole project could be deleted tomorrow and basically nobody in the real world would care.
display servers aren't supposed to be important. they're not supposed to be noticeable. if they are, that's a bug. for most people, we want the thing that you can pick up and use. wayland is extremely noticeable. this makes you feel good but means you've written absolute shit code. X is not very noticeable. this makes it better than what you make. sorry bud!

>And you already have one.
None of these use Wayland. They're written against nonstandard, proprietary protocols. Basically EEE-style lock-in.
>Because I am writing the code and you are not
The code I have to patch to make it work right, yes.

>Wayland devs would merge your patch
if i allowed them to.
after the initial author of the bug causing my cursor issue referred to me in some denigrating terms for insinuating "his" code was broken, i withdrew any support for the project. i have a working fix for one (of a great many) lingering wayland issue and i will never provide it to them because of the developer's approach to communication with another volunteer contributor.

>Except that isn't what happens.
So it uses some proprietary IPC mechanism/interface that lets it sidestep Wayland's deficiency? If some shitty GNOME extension is allowed to do this, why not any other app? What's the point, then?
>You're so close to figuring out why X11 is bad. Like, so close.
It lets you do what the frick you want to?
>Why would they limit themselves to only using Wayland interfaces? Wayland is not a terminal emulator protocol.
Because we are talking about Wayland as a display server protocol, not GNOME or KDE specifically.
>Moving the goalposts. Why do you need this? Give one valid usecase.
You can shove that goalpost up your ass and keep it.

>you know, now that you mandate it, i have always enjoyed the idea of eating bugs

do you think of underage little girls often, anon?
i just want the nature pics i took to not get stretched, but gnome-daddy decided i should eat bugs and use the centrally-mandated unsplash or whatever instead

this is a pretty funny take from my perspective, because i'm actually a total homosexual (as in gay) who thinks anime is for children. i might throw up if some e-girl anime trash ended up on my desktop.
as usual you're so wrong

Unironically yes, it's not our problem. You have an actual you problem, not a Wayland problem, and you're whining about it. And everyone can see that. That's why you apparently keep hearing about these you problems, because they're you problems.

Posting from Linux Mint on X, btw, you're an actual homosexual and you're STILL wrong.

Take solace in the fact that their shitty project will never come to fruition.

>changing the type of a function argument is an API break
That depends on the change you're making; there are tricks you can do. (You need different tricks in C++.)

I don't care where it was invented you fool. MIT abandoned it a very long time ago. It has been developed mostly by hobbyists since then. And a few companies like Red Hat, like you said. But mainly hobbyists.

>X11 is a hobby project
you fricking moronic zoomers i swear to god

Unix is a toy OS
https://www.pbm.com/~lindahl/real.programmers.html

He was talking about Unix, are you unable to read?

>I am correct anyway.
It's nobody else's fault but yours that you are wrong. Seethe harder; it amuses us to watch your self-justifications writhe on the rack of truth.

> so i will accept this as a concession that you are wrong and have no idea what you're talking about
Nope it's not. Linux is a hobby OS that some industries use sometime. It's still a hobby OS. If I take your fork and attempt to use it to pound nails, it doesn't magically become a hammer even if I manage to pound a few. It's still a fork.
>then you can determine that the entire project and its ecosystem is useless and has an overinflated sense of self-worth, which allows any intelligent person to promptly dismiss it as an option.
Yes that's what I'm saying. Both X and Wayland are useless hobby projects. Glad we could agree.

Stop moving the goalposts. Regardless:
>libraries
xcb is just a wrapper over the X11 network protocol. Again, this was invented at MIT and extended over time, mostly by companies that found a part of the protocol lacking for their proprietary UNIX offering.
>drivers
Usually maintained by the company that produces the graphics chip. AMD maintains xf86-video-amdgpu, Intel maintains xf86-video-intel, NVIDIA does their own thing, etc...
>test suite
Part of the server...
>documentation, specs
X11 is very well documented. Please elaborate.

>xcb is just a wrapper over the X11 network protocol. Again, this was invented at MIT
The core protocol and some extensions were invented at MIT. Many extensions were not invented at MIT. XCB was not invented at MIT.
>mostly by companies that found a part of the protocol lacking for their proprietary UNIX offering.
Many extensions were not written by proprietary UNIX companies.
>Part of the server...
No. Wrong.
>X11 is very well documented. Please elaborate.
Who is maintaining that documentation right now?

>Stop moving the goalposts.
literally the only thing he's capable of doing, since he has no point except to be antagonistic.
stop replying to and feeding this obvious troll, he will take literally anything you say and turn it against you with no regard for rationality.
wayland apologists have absolutely no integrity.

>he will take literally anything you say and turn it against you with no regard for rationality.
That would be X11 apologists who do that. They turn everything against you that they possibly can unless you praise X11 as the holy second coming of Jesus.
>wayland apologists have absolutely no integrity.
I'm not a wayland apologist so you're thinking of something else.

>Real industrial uses of Linux do not use X or Wayland.
Except they do, albeit less often. Linux on the desktop is used in some niches like scientific computing and film (DaVinci Resolve, Fusion, Nuke, etc). Wayland, as shit as it is, is already being deployed in appliances like smart TVs, where its limitations are not an issue.
>X.org is only one component of X. You need to look at all X code. That includes the libraries, utilities, drivers, basic clients, test suite, documentation, specs, everything.
You have no idea what you are talking about.

>You have no idea what you are talking about.
Please tell me then what all the other repositories in the xorg git are? Those are just there for shits and giggles then? Maybe people keep them as something like, you know, a hobby? And what don't I know what I'm talking about? Explain it in detail.

It's the wayland schizo. He's a permanent no-coder that can only make up things in IQfy threads.

>So how many lines of code for X11 did you write?
not relevant to any discussion, and also i did not ask you.

literally have not asked you

>No, you're thinking of someone else
Nobody would get you confused with anyone else. Trust me.

>continues to act like a schizo
>confused when confronted

>mentally ill patient thinks he's made a single technical argument
Keep it coming.

Stop moving the goalposts. Regardless:
>libraries
xcb is just a wrapper over the X11 network protocol. Again, this was invented at MIT and extended over time, mostly by companies that found a part of the protocol lacking for their proprietary UNIX offering.
>drivers
Usually maintained by the company that produces the graphics chip. AMD maintains xf86-video-amdgpu, Intel maintains xf86-video-intel, NVIDIA does their own thing, etc...
>test suite
Part of the server...
>documentation, specs
X11 is very well documented. Please elaborate.

>wayland apologists have absolutely no integrity
I don't think that's what's going on. You could easily make the same stupid argument for Wayland ("hurr durr wlroots is maintained by hobbyists!").

I mean wlroots excluded a good chunk of the market for a while because it wouldnt work with nvidia's driver. I found this out when I wanted to do a gpu passthru for a gaming vm thru kvm/qemu. I shouldn't have to know what an eglstream is to play video games. Drew Devault you sweaty fricking nerd.

>Real industrial uses of Linux do not use X or Wayland.
Except they do, albeit less often. Linux on the desktop is used in some niches like scientific computing and film (DaVinci Resolve, Fusion, Nuke, etc). Wayland, as shit as it is, is already being deployed in appliances like smart TVs, where its limitations are not an issue.
>X.org is only one component of X. You need to look at all X code. That includes the libraries, utilities, drivers, basic clients, test suite, documentation, specs, everything.
You have no idea what you are talking about.

> Using 1/2 scaling on 8 4k Displays running side by side
Usecase for that: none!

but 3*3840*2=23040

That would be an API breakage, I think.

>accuses others of bad faith arguments
>argument is literally "monitors don't exist"
meds

>accuses others of bad faith arguments
>argument is literally "you're lying" and "monitors don't exist"
meds
the only thing x11 shills seem to think actually exist are nvidia cards with one output for a gaming monitor

>X is decades old and still can't handle vsync in a window correctly
Xorg can do this correctly.

>same leeway to Wayland, which you won't
which i can't. wayland doesn't allow the flexibility to do a quarter of what one can do with X, which naturally limits its usability in any environments with even minor deviations from the developer's expected "norm".
as a result, X will always be the correct choice for any systems that aren't daily driver alienwares running a stable release OS for a neckbeard living in his parent's basement.

You are either doing something in fullscreen or you're using extensions 20 years ago. X still can't handle vsync correctly in windowed programs.

>You are either doing something in fullscreen or you're using extensions 20 years ago. X still can't handle vsync correctly in windowed programs.
GLX is over two decades older than Wayland. It works perfectly fine in windowed programs. So does PRESENT.

>Gaming is, by percentage usage, one of the biggest things in computing
No it isn't and your bias is showing. Gamers should be banned from this board. You are all insufferable and think your shit is the most important and can't fathom that someone would use their computer for anything besides gaming 24/7. This isn't IQfy, go away.

And anyway Valve thinks X11 is shit and is investing in Wayland, they even wrote their own Wayland compositor.

>they even wrote their own Wayland compositor.
kek
yeah, the UI runs in a wayland compositor, but it specifically uses a nested X session to run all the things that matter - the games. the games don't touch the wayshit at all. they're using it like a glorified drm wrapper, like the trash it is.

>this is decidedly a you problem, not an us problem.
No it affects ALL LINUX DISTROS except for maybe SteamOS because that is the only real "gaming distro". But again, Valve said X11 is shit and they want to switch to Wayland.
>i'm sure you've had this experience, since you're a hack of a developer
This is the experience of ALL X11 DEVELOPERS. Ask them and they will agree with exactly what I'm saying. It is a huge giant pain in the ass to push out an X11 release. There are like 2 people on the planet who fully know how it works and know how to fix the test suite, and they don't want to look at it anymore after 30 years of pain.
>but your unpleasant personality gets you in the door with wayland.
If you think I'm unpleasant, you really don't want to talk to X11 developers when they have to do a release.
>not really as extreme a liability as having it just not work anywhere in the first place in its base form
It's the same liability or worse. Because remember, X11 ALSO DOES NOT WORK ANYWHERE IN THE FIRST PLACE.
>you're just whining because you encountered a YOU problem, probably an insufficient intelligence issue pertaining to your setup
No. This is ALL SETUPS on ALL LINUX DISTROS.

[...]
Option "TearFree" "on"

That affects the X server itself, and only with some drivers. It does not stop all clients from tearing.

>No it isn't and your bias is showing.
Yes it is and your bias is showing. Gaming is one of the biggest things in computing.

lmao you're trying to avoid saying that servers or some other bullshit is more important but you know X and Wayland are both irrelevant there so you're trying to avoid the topic entirely.

>Gaming is one of the biggest things in computing.
Not as big as REAL FRICKING WORK.
>but you know X and Wayland are both irrelevant there so you're trying to avoid the topic entirely.
That's even more reason for X and Wayland developers not to give a shit about you. Gaming is primarily done on Windows. Not Linux.

>they even wrote their own Wayland compositor.
kek
yeah, the UI runs in a wayland compositor, but it specifically uses a nested X session to run all the things that matter - the games. the games don't touch the wayshit at all. they're using it like a glorified drm wrapper, like the trash it is.

They are looking to drop that nested X as soon as they can.

No it does not. Here you are with your "works on my machine" shit again. Enough. It's shit, it's trash, you would be banned from the X11 issue tracker immediately if you pulled that.

Prove it? Did you check with every:

- Driver
- GPU
- Client
- WM
- Compositor
- X server version
- Xlib version
- Mesa version
- Kernel version

And all permutations of them? I will need to see the full test matrix.

sure. i'll provide that once you provide me with the first-asked-for proof that wayland will even start without any trouble with every:

- Driver
- GPU

oh wait i already listed at two things that have obvious huge exceptions that will cause wayland to shit the bed and the maintainers to just tell you to buy another computer

>They are looking to drop that nested X as soon as they can.
post proof

not assume you're a complete liar.
but you can't provide proof now, can you?
because you're a complete liar.

>gaming is the most important graphical aspect of computing,
No it's not. It's most important to YOU because YOU are a IQfy tourist who installed Linux just to LARP as a hacker. Shoo.

Yup, works on all of them.

Show the full test matrix? And post the code to run it, we need to reproduce your results.

>No it's not.
Yes it is. It sells the most computers. It sells virtually all of the high end personal computers. It pushes graphical technology forward. It's the most demanding graphical aspect of computing and is also at the same time the most consistent, meaning it's the most relevant by any measure because it's what gets hardware made for it and determines what computers will look like as the years go by.

You are unironically the larper hacker. Any computer that prioritizes graphical display should prioritize gaming unless you're literally talking about some specific use case like some specific company hiring for some specific use case in their specific marketshare, of which only Apple still exists outside of the real general market.

>ALL LINUX DISTROS
>ALL X11 DEVELOPERS
>X11 ALSO DOES NOT WORK ANYWHERE IN THE FIRST PLACE.
>ALL SETUPS
>ALL LINUX DISTROS
this is sounding more and more like a problem that only you have that you're trying to paint as universal because you're insecure about your bargain-bin braincells

No it does not. Here you are with your "works on my machine" shit again. Enough. It's shit, it's trash, you would be banned from the X11 issue tracker immediately if you pulled that.

>Here you are with your "works on my machine" shit again.
well, it does. you know, the same way wayland allegedly works on your machine. but i've yet to see any proof of this so i think you're possibly just projecting your insecurities and incompetencies everywhere wildly.
this, of course, makes it even more of a YOU problem kek

>Nope. I'm quoting X11 developers.
oh, then surely you can post the source of the quotes.

>This is the experience of ALL X11 DEVELOPERS
Keith Packard doesn't agree with you.

GLX is some horribly broken deprecated crap. It does not work. Even the X11 developers will tell you to stop using it and use EGL.

Works on my machine.

>No it doesn't.
Yes, it does. Vidrel.

>And he makes no commits.
That is false.

>Actually I'm on X11.
i highly doubt that. after all, you were just talking about how X doesn't actually work for anybody.
if you were on X11, it would require you to have the intelligence to set it up.

>H-H-Hello v-v-virgins
>I swear!! Stop laughing!! I do Compuper Vision IT'S REAL!!!
>MOM they're not believing me!!!! make them believe me!!!

>haha mom look i said the c word on IQfy

>Shows up to work 1 hour per year
>HE DIDN'T QUIT! HE DIDN'T QUIT!
I really hope you never become the boss at any company

Still doesn't negate the fact that he hasn't quit like you said, he still commits, and that working on an open source project is not equivalent to employment at a company.
You're just coping to an unimaginable level to avoid the fact that you were completely wrong. The cope might work for you, but it's really transparent to the rest of us.

No. Linus at least responds to emails. Keithp does nothing. He quit. He works somewhere else. He doesn't work on this anymore.
>working on an open source project is not equivalent to employment at a company.
Haha that's hilarious. You expect a grown man with 40 years of industry experience to work for fricking FREE? On your stupid gamer bullshit so you can wait for him to get one thing wrong and then you yell at him to cope and seethe? Everyone knows your game Anon, it's not new.

>This is an obvious lie
No. Ask him yourself.
>Prove that he does nothing
Prove wiener size and bench first. Also get keithp to do it too.

>Keithp does nothing
He has several open MRs right now lol

>several open MRs
They are not being worked on by anybody.

>Keithp does nothing
He has several open MRs right now lol

>X11 is why I can admit it's broken
Yet you prefer it over some Wayland compositor. I wonder why?
>That is one client with one driver, actually it is a pretty useless demo client.
No, that is *7* clients, all of them using GLX and vsync. I tested using both intel and nouveau, with and without compositor (picom).
>Hello virgins. I'm gonna need proof of at least mega chad, giga chad or kilo chad.
>he took the kilo chad pill

>You don't know what I prefer
yeah, i really do
>No it is the same client run 7 times.
nope, it's 7 different clients doing the same thing
>Try with several REAL clients and not the demo program. Also try with some EGL clients.
they're real enough for me
>That is about 0.0000001% of the things you need to test.
that is 100% of what i need to test
>Proof of wiener size
speaking of what you prefer, it's obvious you prefer homosexuality

>I would have :(.
i'll accept a picture of your wiener anon
not for any weirdo proof reason though
i just like giving complements to friends

>Looks incredibly choppy, I wouldn't call that "working".
this is funny because it seems choppy to you due to being on wayland

>Describe what "real work" it is
Computer vision, machine learning
>provide proof that you do it.
First you provide proof that you are a real person and not a gpt3 bot. Also prove that you have at least a 10 inch wiener and can bench 150kg, I only give proof to mega chads, giga chads or above. Yes I am serious about this, no homo.

>First you provide proof that
kek. so no proof then, got it.
so you do "computer vision" and "machine learning" ooh, is that so. well mister definitely-not-full-of-shit guy, tell me one thing about the nature of your work that doesn't use text copied from wikipedia or some other trivially accessible webpage. maybe you can salvage yourself from appearing like a 12 year old lying about his canadian girlfriend with increasing urgency as tears well in his eyes

>Looks incredibly choppy, I wouldn't call that "working".
Of course it's choppy, I had to limit the frame rate to fit it into the size limit.
Try finding a single tear in any frame. I'm waiting.

>Keith packard is not an X11 developer. He quit.
He literally has owner access level on xorg's gitlab.