Chuck Anderson wrote:
On Mon, Feb 22, 2016 at 07:19:25PM -0600, Michael Catanzaro wrote:
> On Wed, 2016-02-17 at 19:57 +0100, drago01 wrote:
>> Why would they have to do that? The X session isn't going anywhere
>> can just login into X.
> This is a really good point... I was thinking "how many users will we
> piss off if they cannot use feature XYZ," when I should have been
> thinking "how many users will want to stop using Wayland because
> feature XYZ is not implemented?" and "how serious a PR problem would
> this be for us if not implemented?"
One of the reasons to change the default is to get more exposure and
attention on Wayland so that bugs can be fixed, improvements made,
However, the downside to that is there will be LESS exposure and
attention paid to X11. If there are too many feature regressions in
Wayland compared to X11, some users who have no choice but to run X11
to get the features they require may experience bugs that may not be
fixed in a reasonable time since "everyone else has moved on and is
This has happened over and over again with big changes. The old stuff
gets left behind. Nobody wants to work on it anymore.
I think that is one reason why there is resistence to changing the
default until the new thing has feature parity with the old thing.
This is true with accessibility as well, though even worse. An example
of this is vte2. Some older terminal emulators use it, such as
mate-terminal, lxterminal, and xfterm. There are serious accessibility
issues in vte2 library which prevents orca from reading some terminal
contents. This has been fixed in vte3 but when I ventured a request to
have them backported the response I got was a flat and somewhat smug no.
Have the other terminal emulators switch over to vte3, was my only
option. Easier said than done. This is also true for gtk2.0. There are
some, though fortunately not a lot, of accessibility bugs that have been
fixed in gtk3, plus lots of new features. Though gtk2 is still being
updated, I believe, please feel free to correct me if I'm wrong, that
gtk2 is in maintenance mode. This means that some of the bugs in the
mate desktop are fixable but aren't getting fixed because no one is
committing a11y fixes to gtk2. It's a sad situation I'm not sure how to
resolve without getting up on my soap box, which I really hate to do. So