E1Q6Y57O

5 ms·

1.
by E1Q6Y57O 3y ago
>Hacks are often the correct way to do things. In this case, it's not the correct way. >I'm telling you "it works for my professional use case on X11 and doesn't on Wayland" and you keep trying to gaslight me
2.
by E1Q6Y57O 3y ago
Like everything else in XCB, those are just stubs autogenerated from the wire protocol definition. The client has to actually implement the protocol semantics including duplicating a lot of logic that's already present in Xlib. There&#
3.
by E1Q6Y57O 3y ago
Yes, I know what it is. Here are some corrections. 1. XCB is a low level binding to the X11 protocol. It doesn't really replace Xlib. Originally that was the intention, but it's non-trivial to take an Xlib program and port it to X
4.
by E1Q6Y57O 3y ago
Replying again because you edited your comment. xbacklight, xcalib, xcape, xmodmap, xrandr, xset: These are utilities specific to configuring the X server. They're needed on non-X11 window systems. xbel: I don't know what this is.
5.
by E1Q6Y57O 3y ago
This comment makes no sense, XCB isn't a toolkit. You might be thinking of something else with a similar acronym. But anyway, any solution that tells users to only use a small subset of compatible clients is about as disruptive as just
6.
by E1Q6Y57O 3y ago
>Also they are mostly developed by full time paid employees with zero community involvement. No. Both of them have a good mix of community contributors to do the fun stuff, and paid employees to do the annoying tasks no one wants to do f
7.
by E1Q6Y57O 3y ago
Which X clients are these? You didn't name any so let's just look at some of the popular and recent flathub apps: https://flathub.org/ I see a lot of games, chat apps, text editors, photo apps, office apps. These
8.
by E1Q6Y57O 3y ago
No it actually doesn't, I've heard tons of complaints about X clients not scaling correctly. Sure it might work for the subset of clients that are reading the DPI value the way you intended, but in doing so you've silently br
9.
by E1Q6Y57O 3y ago
>Looking over the part where you imply that the MacOS App Store is the standard way to install Applications on MacOS That is the standard way. An app that has its own custom installer or patcher/updater is by definition, using a non
10.
by E1Q6Y57O 3y ago
No. Even the X.org developers disagree with you here. Messing with the DPI will cause lots of clients to break even further. See this merge request for more info on this: https://gitlab.freedesktop.org/xorg/xserver&#x2F
11.
by E1Q6Y57O 3y ago
This is incorrect, apps installed through the macOS App Store have required sandboxing since 2012. Since 2018, Microsoft is also attempting to get developers to sandbox more apps, see more about that here: https://news.ycombinato
12.
by E1Q6Y57O 3y ago
That's the same limitation as XQuartz or any other rootless X server. And you have this exactly backwards. The majority of X clients that users care about are ordinary programs, not window managers or xdotool.
13.
by E1Q6Y57O 3y ago
If this works for you, cool. But this is... not good in any way, and it's still not going to work for clients that use a different toolkit or text renderer than the ones you've configured. I hope you can see how it's unaccept
14.
by E1Q6Y57O 3y ago
>X11 is one of the few APIs that had a really long run and that everybody in the community agrees upon Outside of a very small niche of obscure window manager developers, this isn't true. GNOME and KDE have been trying to get rid of
15.
by E1Q6Y57O 3y ago
Are you actually suggesting that most Linux desktop users only use the same 4 programs you do and will never use or install anything else? If that's the case then why bother with a display server or package managers? We can hardcode th
16.
by E1Q6Y57O 3y ago
No, xrandr isn't sufficient. It still doesn't have scaling information, only size information. Changing the reported physical size of the monitor is a bad idea as it can break other things.
17.
by E1Q6Y57O 3y ago
That article is horrible. What it describes is yet another hack where clients attempt to guess the DPI and then rescale themselves, and the server and compositor know nothing about DPI. That method only exacerbates the problems where client