I like the Linux [standard system] on a phone idea specifically because it promises the ability to run desktop-class applications.
Conversely I think (touch, but not exclusively) desktop usability will greatly benefit from interfaces that are more universally, thoughtfully and efficiently built due to screen space, power and touch controllability requirements.
These benefits will however be greatly reduced to almost nonexistent, besides being a gigantic needless duplication of resources, if code is not shared.
When I'm on the desktop I want to use an app that is nice, simple and has the festures I need, which can at times be quite complex.
The priorities may shift on the phone, but the requirements are still fundamentally the same.
I don't want to learn a new program with a different feature set, different bugs to fix and quirks to get accustomed to switching platforms.
Yes, I just explained the concept of #convergence, which is not too unpopular.
Yet even in the Linux (specificallly #KDE) ecosystem, which I consider the most potentially convergent, it seems like there's a bit of an itch to reinvent things unnecessarily.
Probably it often makes sense to write things anew, but let's just keep one thing at the end.
Let's not have Plasma and Plasma Mobile and Dolphin and a Plasma Mobile file manager, but just ... Plasma and Dolphin.
@solarkraft Plasma and Plasma mobile share a lot of code. The difference are mostly the default widget installed, some KWin plugin added or removed and a difference system setting application (but the module are the same). Index (the Plasma Mobile file manager) is build specially around touch UI and convergence, maybe in the future it will replace Dolphin or maybe not.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!