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.
7-ish. I think one of the important value propositions of good FLOSS is precisely that it isn’t market-oriented. It can target segments that are not profitable, but more importantly it can offer software as democratic participation, or, if you can bear the Marxism, non-alienated computing. Doesn’t mean it always does, but it can, and should.
It’s one of the few cases where @doctorow’s Walkaway principle, which only works in the presence of abundance, probably works for real.
@doctorow It doesn't have to be market-oriented, but still product-oriented. As in: the whole package of functionality, design, quality assurance, documentation, user support, release planning, community management and public communication has to be consistent and clear. The best FOSS projects are run like commercial products. But most aren't.
@Sturmflut I didn’t see this at first but I think I, am avid Marxist, would agree. The core difference I see is in participation and influence.
@albin all great points. I would add “platform independent” and “language agnostic”. Don’t try and invent yet another language, there are plenty already that are very good at what they do. and a way to make money/get funded wouldn’t hurt, provided it’s not the primary goal.
@Tryphon absolutely, but those are different and perhaps even harder problems, though I suspect things like Patreon and/or app subscriptions could work. I suspect people would be much happier paying a recurring fee for software where they feel like a part of its community and can see its ongoing development
NOTICE: Registration on scholar.social is open to anyone who is willing to abide by our Community Standards. Email scholar dot social at protonmail dot com if you want an invite!
Scholar Social is a microblogging platform for researchers, grad students, librarians, archivists, undergrads, academically inclined high schoolers, educators of all levels, journal editors, research assistants, professors, administrators—anyone involved in academia who is willing to engage with others respectfully.
We strive to be a safe space for queer people and other minorities in academia, recognizing that there can only be academic freedom where the existence and validity of interlocutors' identities is taken as axiomatic.
"An academic microblog that you can be proud to put on the last slide of a presentation at a conference"
(Participation is, of course, optional)
Scholar Social features a monthly "official" journal club, in which we try to read and comment on a paper of interest.
Any user of Scholar Social can suggest an article by sending the DOI by direct message to @firstname.lastname@example.org and one will be chosen by random lottery on the last day of the month. We ask that you only submit articles that are from *outside* your own field of study to try to ensure that the papers we read are accessible and interesting to non-experts.