Thought I’d create a distinct thread from the previous one asking about daily use, because I really do want to hear more on people’s pain points. Great to know people are generally sounding pretty positive in those posts who recently switched, but want to know your difficulties as well! This way old and new users can share their thoughts, hopefully to inspire a respectful discussion.
@Sprocketfree @cm0002 the problem is not that they don’t exist it’s that they barely have apps.
linux and the DEs dont make it easy to write apps for, this is a compositor/window manager/de issue to solve.
Want to write an for gnome? Javascript or c++. Enjoy libadwaita. Want to write for kde? C++ only. Dont want to write js and you only know kotlin/swift/java/objc? Tough fucking shit, get fucked. Want to write rust? Not supported by kde or gnome ootb, the learning resources are bare etc. Oh and for kde you have to learn QT as well have fun:)
Itd be cool if rust was the baseline standard for writing apps and was fully supported by the major DEs. I honestly cannot be bothered to learn C++ just to make a tiny app for my desktop, I will never use it again in my life because it is dying.
@dreadbeef C bindings can be used on Rust so Gnome should be easier. I find QTs lack of AT-SPI to be a non starter. Also nothing says you need to use gnome or it if you’re making your own mobile first compositor.
right, but popular (and valid imo) complaint about mobile on linux is the lack of apps. GUI applications either have to bring their own GUI toolkit (slint/qt/etc) or use the one provided by the host (the DE on linux). Like all of linux, its very fragmented at the moment, and theres no clear leader
@dreadbeef super valid point. I do believe having a Wayland compositor that just reformatted the app via ST-API would be a massive first step. It would force accessibility and dynamic sizing. Given only Gnome has ST-API built in. Qt is just a mess for accessibility
I know… And I’m sad