7 ms·

I haven't hit any for probably a decade now. Bugs in the window manager or shell (both shipped by KDE) are somewhat more common, but even if they are crashes,

by o11c 1y ago

I haven't hit any for probably a decade now. Bugs in the window manager or shell (both shipped by KDE) are somewhat more common, but even if they are crashes, due to X11 being better-designed for isolated faults they are easily recovered-from without loss of session.

jsheard 1y ago
X11 not supporting modern display technologies is arguably a bug, and it's not likely to get resolved at this point (e.g. it can't do mixed DPIs, or VRR with multiple displays, or HDR in general).
- o11c 1y ago
  I don't care about any of those things, since computers are about productivity for me. But I'm pretty sure at least half of them actually do work under X11, it's just that some UI libraries refuse to use it on the grounds of "X11 is outdated, I won't support features even though it does". (also, having played around with DPI stuff on Wayland, it's pretty broken there in practice)
  - whatevaa 1y ago
    Well and others do care, and no, bunch of stuff straight up doesn't work on Xorg, or is jank fest.
    - superkuh 1y ago
      Yep. I feel the same about all the various wayland compositors. Even 15 years on none of them have managed to implement accessibility support for existing linux applications. No screen readers support on any but GNOME's compositor and that doesn't work with existing applications; GNOME invented 2 new incompatible protocols that only their compositor works with (which doesn't work with existing applications). No HDR or high DPI is an annoyance. Not supporting accessibility is real deal breaker. Especially for commercial settings where things like Americans with Disability Act compliance matters. And even more for me with my retinas slowly tearing apart and losing my eyesight: the entire waylands ecosystem is extremely inconsistent and buggy.
  - TiredOfLife 1y ago
    > I don't care about any of those things, since computers are about productivity for me. All of those are productivity things
  - skeezyboy 1y ago
    >I don't care about any of those things, since computers are about productivity for me. I guarantee you spend more time "configuring" linux than actually being "productive" with it.
- ryao 1y ago
  I suspect X11 can do mixed DPI and VRR with multiple displays if you do 1 display per xscreen, but nobody uses that configuration. I suspect HDR support could be added if someone were to retrofit it like how VR support was added, but no one really wants to work on that.
  - bitwize 1y ago
    No. HDR will never come to X11. This is because the X protocol defines a pixel as a CARD32, that is an unsigned 32-bit integer. So the highest depth you could theoretically go is R10G10B10, and forget about floating-point HDR. Fixing this would require rewriting the entire protocol. Which has effectively already been done; it's called Wayland. Perhaps people ought to listen to the Xorg devs when they say X11 is broken and obsolete, and you should be using Wayland instead. Every single one of them says this.
    - o11c 1y ago
      All sorts of things in X11 are "defined" as a particular thing in the base standard, then changed in protocol extensions. You really shouldn't be writing raw pixels anyway (and most people don't since breaks if your monitor is using 8-bit or 16-bit, for example).
      - whatevaa 1y ago
        Amazing standard you got there.
        yxhuvud 1y ago
        To be fair, the same is very true with Wayland - you can't do much without extensions.
      - skeezyboy 1y ago
        > You really shouldn't be writing raw pixels anyway (and most people don't since breaks if your monitor is using 8-bit or 16-bit, for example). what are you talking about?
- bee_rider 1y ago
  I guess we’d have to see what the argument is. But, that looks more like a lack of features to me.
- hulitu 1y ago
  > X11 not supporting modern display technologies is arguably a bug, X maintainers said it is a feature they do not want to implement. Because "we work on Wayland now, Wayland better".
  - E39M5S62 1y ago
    You're free to submit patches and features to X.org.
    - nairboon 1y ago
      Not really, that is OP's point. Xorg maintainers don't really want to enhance X11 and add new features, only critical bug fixes. That is one of the reason there are now X11 forks like Xlibre.
      - ryao 1y ago
        That is a misconception. They added VR support to the Xorg server long after people started saying this. New features need to be well written and not break existing things, which is hard to do. The entire premise of Wayland was to make a clean state to avoid having to worry about existing things. However, they are not opposed to having new things added, as long as adding new things does not break existing things.
  - ryao 1y ago
    This guy does not work on Wayland: https://www.x.org/wiki/AlanCoopersmith/ https://www.x.org/wiki/AlanCoopersmith/ That said, he has not volunteered to implement HDR.

by o11c 1y ago

jsheard 1y ago

X11 not supporting modern display technologies is arguably a bug, and it's not likely to get resolved at this point (e.g. it can't do mixed DPIs, or VRR with multiple displays, or HDR in general).

o11c 1y ago
I don't care about any of those things, since computers are about productivity for me. But I'm pretty sure at least half of them actually do work under X11, it's just that some UI libraries refuse to use it on the grounds of "X11 is outdated, I won't support features even though it does". (also, having played around with DPI stuff on Wayland, it's pretty broken there in practice)
- whatevaa 1y ago
  Well and others do care, and no, bunch of stuff straight up doesn't work on Xorg, or is jank fest.
  - superkuh 1y ago
    Yep. I feel the same about all the various wayland compositors. Even 15 years on none of them have managed to implement accessibility support for existing linux applications. No screen readers support on any but GNOME's compositor and that doesn't work with existing applications; GNOME invented 2 new incompatible protocols that only their compositor works with (which doesn't work with existing applications). No HDR or high DPI is an annoyance. Not supporting accessibility is real deal breaker. Especially for commercial settings where things like Americans with Disability Act compliance matters. And even more for me with my retinas slowly tearing apart and losing my eyesight: the entire waylands ecosystem is extremely inconsistent and buggy.
- TiredOfLife 1y ago
  > I don't care about any of those things, since computers are about productivity for me. All of those are productivity things
- skeezyboy 1y ago
  >I don't care about any of those things, since computers are about productivity for me. I guarantee you spend more time "configuring" linux than actually being "productive" with it.
ryao 1y ago
I suspect X11 can do mixed DPI and VRR with multiple displays if you do 1 display per xscreen, but nobody uses that configuration. I suspect HDR support could be added if someone were to retrofit it like how VR support was added, but no one really wants to work on that.
- bitwize 1y ago
  No. HDR will never come to X11. This is because the X protocol defines a pixel as a CARD32, that is an unsigned 32-bit integer. So the highest depth you could theoretically go is R10G10B10, and forget about floating-point HDR. Fixing this would require rewriting the entire protocol. Which has effectively already been done; it's called Wayland. Perhaps people ought to listen to the Xorg devs when they say X11 is broken and obsolete, and you should be using Wayland instead. Every single one of them says this.
  - o11c 1y ago
    All sorts of things in X11 are "defined" as a particular thing in the base standard, then changed in protocol extensions. You really shouldn't be writing raw pixels anyway (and most people don't since breaks if your monitor is using 8-bit or 16-bit, for example).
    - whatevaa 1y ago
      Amazing standard you got there.
      - yxhuvud 1y ago
        To be fair, the same is very true with Wayland - you can't do much without extensions.
    - skeezyboy 1y ago
      > You really shouldn't be writing raw pixels anyway (and most people don't since breaks if your monitor is using 8-bit or 16-bit, for example). what are you talking about?
bee_rider 1y ago
I guess we’d have to see what the argument is. But, that looks more like a lack of features to me.
hulitu 1y ago
> X11 not supporting modern display technologies is arguably a bug, X maintainers said it is a feature they do not want to implement. Because "we work on Wayland now, Wayland better".
- E39M5S62 1y ago
  You're free to submit patches and features to X.org.
  - nairboon 1y ago
    Not really, that is OP's point. Xorg maintainers don't really want to enhance X11 and add new features, only critical bug fixes. That is one of the reason there are now X11 forks like Xlibre.
    - ryao 1y ago
      That is a misconception. They added VR support to the Xorg server long after people started saying this. New features need to be well written and not break existing things, which is hard to do. The entire premise of Wayland was to make a clean state to avoid having to worry about existing things. However, they are not opposed to having new things added, as long as adding new things does not break existing things.
- ryao 1y ago
  This guy does not work on Wayland: https://www.x.org/wiki/AlanCoopersmith/ https://www.x.org/wiki/AlanCoopersmith/ That said, he has not volunteered to implement HDR.