I have some thoughts on the future of #UI on non-mobile devices and the role that #FLOSS can play.

1. It seems that all proprietary software companies are de-prioritising their desktop OSes, in terms of focus and resources. Microsoft is doing weird tablet hybridisation and Apple is just porting iOS junk back from the iPad.

This creates a vacuum, as there is no modern desktop UI. Nothing's been done since roughly OS X. It's been 18 years. More than my whole adult life.

2. There will be very little financial incentive to fill this vacuum. Desktop OS:es only sell to the enterprise, which has different requirements, and Microsoft has that market cornered anyway.

No-one who is making software purely for money would be able to do this. Well, we, the FLOSS community, aren't, and so we can.

3. In order to do this, we need to experiment. A lot. And most of these experiments will probably fail.

For that to happen, the cost of development in terms of time and cognitive load must go down. Much like Rust seems to have enabled a wave of new command-line tools that are faster and much less boring than the traditional Unix tools. Making a GUI app must be roughly as complicated as making a CLI app.

4. This requires languages AND frameworks. The languages need to remove the incidental complexity in dealing with the concurrent situation that is a modern UX app. The frameworks need to encapsulate common patterns and remove boilerplate.

The languages are mostly there, I would argue, and the patterns are somewhat implemented (functional reactive programming, Excel, etc), but the frameworks are not just a little behind.

5. We also need to train FLOSS people in design AND recruit design-oriented people who may or may not code. This might also entail developing our tools for communication and infrastructure to also capture common workflows in design. I don't know, I'm not a designer.

@albin Agreed. We do experiment a bit, i.e. GNOME 3, but then that generates a lot of heated discussions etc.

I think we have fairly decent desktop UIs now. They should keep evolving for sure, but what we should focus most of our energy on is a Mac like developer experience for desktop aps, i.e. developing an unified set of APIs with lots of complex functionality prepared as part of a SDK for developers to tap into. On Mac, there's AppKit, which is why all the independent desktop apps are Mac.

@MatejLach I have tried app development on the Mac and found it unbearable, but I agree, sort of. It’s a trade-off between exploring new things and improving the ones we have, but I don’t think they are in fundamental conflict.

@albin Agreed. I tried it too and didn't like it, but that's mostly because there's a lot of legacy stuff back from NEXTStep days, (a lot of APIs are even still named NS), which is not idiomatically integrated with Swift as ObjC doesn't really fit that model. But that wooudn't really be a problem with Linux if said frameworks were build from scratch. The point is, bellow the cruft, Mac has the most complete set of APIs to tap into for desktop dev, (in terms of functionality, not elegance of use)

@albin The reason why the likes of Sketch, Scrivener etc. are on the Mac is because of all that ready-made functionality you can tap into, which there's no real equivalent on #Linux. #KDE's trying it a bit with their split into frameworks, but that's largely tied to C++ because of Qt a bit too strongly and also tends to be specific to the KDE ecosystem.

If you look at all the functionality here, developer.apple.com/documentat - Linux does have most of it, but not nicely documented or unified.

@MatejLach @albin There's certainly all the libraries you could need though, so really it's just a matter of bundling those together into useful groups.

@alcinnz @albin

Yep. It might be as easy as making a simple 'orientation index' of what's available, because a lot of devs coming from integrated experiences like on the Mac are simply not sure where to look for the stuff they'd expect when developing for Linux.

I also happen to think we need a secondary choice/alternative to program in - something a bit more accessible to people than C/C++.

Qt now has official Python bindings so I think it would be useful for KDE to adopt it as well.

@alcinnz @albin

GNOME/GTK/GObject has Vala, but they seem to have shifted towards Rust now, so hopefully it'll become a first class citizen in their docs as well soon.

@MatejLach @alcinnz WHAT?! They are going with Rust? OMG I didn't know. That's AMAZING!

@MatejLach @albin I'm glad to see them moving towards dropping their ugly GObject system and towards a language that's offers what they neeed.

That said Rust won't be a simple transition and I'm sure it'll take a while, it's interpretation is a fair bit different from what they based their APIs on. Until then I may continue to see Vala as the best choice for developing GTK apps.

@alcinnz @MatejLach @albin wait, what? GObject is not ugly (if cumbersome to write out in C), and no way they're going to drop it

@bugaevc @alcinnz @albin

I think they've invested too heavily at this point in GObject to simply entirely drop it, it's far more than a OO system at this point. I think what they're going to do is to have wrappers around it that hopefully make it a more pleasant experience to write and maybe build Rust-native parts for the new libs etc. that will feel even more idiomatic.

@MatejLach @bugaevc @albin I can't disagree. And Vala fills the need for those wrappers very well.

Definitely will be an interesting transition to watch!

@alcinnz @MatejLach why are you talking about it as if there was some grand decision to transition from GObject to Rust?

As far as I understand it, some GNOME folks ( @federicomena, @slomo, @alatiera, ...) are interested in Rust, use it in some projects (librsvg, GStreamer plugins) and are working on ways to use GObject-based libraries *from* Rust (gtk-rs) & write GObject-based libraries *in* Rust (gnome-class); and that's it.

@bugaevc @MatejLach @federicomena @slomo @alatiera Fair enough, I still need to watch the linked talk. And probably should be more sceptical when hear of "grand decisions" from GNOME.

@alcinnz @bugaevc @MatejLach @federicomena @alatiera

Where did you get that part about "grand decisions"? There's no CEO of Gnome who decides that everything's going to be done *that* way now :) People do the work they want to do (or are paid to do), and that's how things move forward.

@alcinnz @slomo @MatejLach @federicomena @alatiera @bugaevc I just want to add my 50c:
as an ex-iOS dev I can say that developing for Apple is a pain. AppKit is such a nightmare, they're porting UIKit to macOS. No one sane even wants to touch default database, what are the super APIs you're talking about. There are desktop apps for mac because people who use mac are used to pay and a lot and UI people use it

@charlag @alcinnz @slomo @federicomena @alatiera @bugaevc

See i.e. sketch.com/support/requirement

"Due to the technologies and frameworks exclusive to macOS that Sketch has been built upon, regrettably we will not be considering supporting Sketch on either of these platforms."

I am not saying they're pretty to work with, but there's no denying that AppKit, Cocoa etc. provide a large set of functionality to tap into that while available on other platforms as well, is only really unified on macOS.

Follow

@MatejLach @charlag @alcinnz @slomo @federicomena @alatiera @bugaevc PS. Ex-macOS Sketcher, now very happy with a subscription to Gravit Designer on Linux – it’s rather excellent ;)

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.