4 ms·

> "which to this day still doesn't provide a proper experience to anyone that cares about graphics programming and usable UI/UX tooling." Genuinely curious wha

> "which to this day still doesn't provide a proper experience to anyone that cares about graphics programming and usable UI/UX tooling." Genuinely curious what doesn't work in IE Ubuntu 21.04 for you? Not one of those raving Linux zealots (don't really care that much about privacy), I've just had positive experiences on Linux -- not using it masochistically for ethical reasons, but because it worked very well for me. So I would be interested in hearing the other side of the coin, since you've been around the block a time or two.

blep-arsh 5y ago
I'm not the person you were replying to, but here's the straw that broke this multilingual camel's back: unless Gnome is running under Wayland, switching the keyboard layout steals the input focus away from the foreground window briefly, causing focus-loss event handlers to fire. This might seem an easily fixable minor issue but it's actually a decade-old hairball which significantly harms the experience and can't be fixed cleanly under X.
- yyyk 5y ago
  I don't recall this ever happening to me in KDE under X, at least not in a way I've noticed.
  - blep-arsh 5y ago
    It's a Gnome-specific thing
- e12e 5y ago
  Isn't Wayland standard in 21.04? So it's already fixed? Ed: > it's actually a decade-old hairball which significantly harms the experience and can't be fixed cleanly under X. This is literally the whole argument for Wayland - things that can't be fixed under x11?
  - blep-arsh 5y ago
    I didn't notice Wayland becoming the default, tbh. Thanks for mentioning this. As for the specific bug, it was introduced by the implementation of a non-essential feature (the languague switch HUD) which was then left in place, likely because the Wayland transition was juuust around the corner. While Wayland does address many architectural issues, I don't think X users should deal with regressions caused by Wayland-optimized features just yet (and definitely not 8 or so years ago).

blep-arsh 5y ago

I'm not the person you were replying to, but here's the straw that broke this multilingual camel's back: unless Gnome is running under Wayland, switching the keyboard layout steals the input focus away from the foreground window briefly, causing focus-loss event handlers to fire. This might seem an easily fixable minor issue but it's actually a decade-old hairball which significantly harms the experience and can't be fixed cleanly under X.

yyyk 5y ago
I don't recall this ever happening to me in KDE under X, at least not in a way I've noticed.
- blep-arsh 5y ago
  It's a Gnome-specific thing
e12e 5y ago
Isn't Wayland standard in 21.04? So it's already fixed? Ed: > it's actually a decade-old hairball which significantly harms the experience and can't be fixed cleanly under X. This is literally the whole argument for Wayland - things that can't be fixed under x11?
- blep-arsh 5y ago
  I didn't notice Wayland becoming the default, tbh. Thanks for mentioning this. As for the specific bug, it was introduced by the implementation of a non-essential feature (the languague switch HUD) which was then left in place, likely because the Wayland transition was juuust around the corner. While Wayland does address many architectural issues, I don't think X users should deal with regressions caused by Wayland-optimized features just yet (and definitely not 8 or so years ago).