Recent searches
Search options
@dgchrt@mastodon.social On Gnome I am always installing Dash to Dock, Blur my Shell, No Overview on Startup and something to deal with notifications and clipboard history.
On KDE I don’t need any of this and just run trusted upstream code.
I am usually activating minimise via tweaks, since a lot of programs, Gnome and non-gnome, don’t have as proper session management as something like the Gnome Text Editor... Christian Hergert just writes exceptionally good software.
Part 1 of 4… sorry 
@dgchrt@mastodon.social 2/4
I prefer the design language of Gnome, having a much simpler UI than KDE. It’s not so overwhelming at first, but I prefer that KDE isn’t as flat and it got better.
Furthermore GTK and Adwaita integrate very well with everything from Rust, C, Go, Haskell, JavaScript, Python, OCaml, Lua and basically every language, due to GObject introspection. Our build system of choice, Meson, is just simple, compared to the abomination that is CMake and everything is GPL and LGPL.
@dgchrt@mastodon.social 3/2 as for Apps, I love the rich ecosystem that Gnome has and especially Ptyxiz (terrible name) and the focus on Flatpak are just lovely.
Our focus on accessibility is great and I love the people I have contact with. However, I have to admit that some devs don’t have the best appearance in something like the Wayland working groups and free desktop in general.
@aral that’s fair, but @matt is working on improving the situation and afaik their work is founded by the @sovtechfund. If I remember correctly, they have a fork of booth GTK and Orca screen reader that already works :D
Accesskit is being integrated into GTK and a lot of Rust UI toolkits are integrating it as well. Xilem, Slint and Iced / COSMIC are good examples of this.
@janvhs @dgchrt @matt @sovtechfund Yep. But I see very little in the way of introspection or new policies to ensure something like that cannot happen again. Not one major distribution has apologised for shipping with a broken screen reader or explained what steps have been taken to ensure it doesn’t happen again. Accessibility is simply not a showstopper or part of the regular development process for Linux distributions and that must change.
@aral sure policies would be great and I suspect they will come, because the EU has put regulations for accessibility in place for 2025. I don’t now more than you, but I suspect Redhat, Canonical and SUSE will need to invest into a11y, when they want to sell their desktop Linux.
However, I don’t see a reason for apologising. This is mostly free labour and FOSS, what’s not there, can’t be supplied.
@janvhs @dgchrt @matt @sovtechfund Redhat (IBM), Canonical, and Suse are all either billion-dollar or hundred-million-dollar corporations.
@aral @janvhs @dgchrt Please remove me from this thread. I think it would be appropriate to remove @sovtechfund as well. This argument has already been had. I'm already doing what I can, and so is STF. I, for one, don't want the noise of rehashing this argument.