I think the idea of one programming language everywhere has sailed, for a while at least.<p>It looked like JavaScript was going to be able to do it. React and React Native were very promising.<p>But since we now have Swift/SwiftUI and Kotlin/Jetpack, each platform has a language and framework specifically tailored for it. Except for Windows which is still a shit show.<p>Attempts to abstract this in a cross-platform layer are becoming more and more difficult, and offering less marginal value (e.g. we now have declarative frameworks natively whereas before we only had React).<p>Each platform has a recommended way to do everything, and we should follow the conventions of each platform.<p>I would be interested to hear if anyone has actually had successful though with frontend code sharing...
Web applications. If it is at all possible to make it a a web application why mess around with anything else? The other day I was struggling with "How the hell do I tell Android users how to find a QR code that really works in the play store" and then it hit me... Web based QR code reader and done!<p>It can be depressing that you have 20 electron applications running to put icons in the tray but heck... everybody wants to stuff icons in your tray and most of those x-platform frameworks can't make a tray icon. I did an evaluation of a whole bunch of x-platform frameworks and they all sucked, though I do like JavaFX best of all. There's a reason why Electron is as big as it is.
JavaScript has accomplished this, though. It's just that React Native/Phone Gap isn't as performant as native. I'd argue though that the web is a "run anywhere front end" given that pretty much everything has a web client these days, even TVs.<p>The main issue around this is that there's not a great interface to use native functionality on the web, hence all of these compilation attempts.
My partner and I run a small video game studio and we wanted a bytecode format we could run on every device we owned, so we made a 100ish lines VM spec, and implemented these thin emulation layers for the different platforms. My wiki, our games, the compilers, linters and type checkers are all written in that same language, assembling to rom files that will run equally well on a GBA, Playdate, RPi, Thinkpad, PSP and so forth.<p>It's worth looking into. I hope you find something that works :)<p><a href="https://100r.co/site/weathering_software_winter.html" rel="nofollow noreferrer">https://100r.co/site/weathering_software_winter.html</a>
For some things, uxn/varvara will do; it is simple enough that it can run anywhere.<p>For other things that can run by internet, a subset of telnet and terminal codes might do; however, that is only good for remote services and not for stuff that is more useful to run locally.<p>For some things, C will do, especially command-line stuff, but also is possible to use SDL, etc.<p>You do not need so much extra stuff that just makes it slow and takes up more memory and makes it difficult for the user with program working together; for this reason, UNIX pipes are useful because you can put any program together by pipes. (Like, another comment also mention something similar)
I have been on two projects now that use web frameworks to ship complex management applications and both were nightmares. The cost of doing even simple changes was not small. React has been way worse than angular on this front too. People do not understand it. They do not think "<i>the react way</i>". They invariably code something that doesn't consider reacting to change properly and now you have a complex component that is refreshing all the time
Do you have thoughts and opinions on the various options for Windows desktop development? I would be curious to know, I am starting to work on a Windows desktop app. I am assuming that the first, MVP-style, attempt will be using Electron.<p>But I am also wondering if Maui will end up being a better option, or if I will be able to have an excuse to use the Avalonia framework for F#
I will poison my own well and state that I don't think my opinion is a good one but I've come to admit the reasoning behind suckless-type software.<p>Might not even be adjacent to the topic of this thread but I remember the one time I accidentally found out about UNIX pipes in a bioinformatics course. I didn't know you could use computers in a way that would help you get things done gracefully and without GUIs. I didn't know I could just type in `curl wttr.in` and get the weather results instantly. I didn't even know about vim. I didn't know that an OS could occupy less than 1GB RAM on idle and still let you fully <i>operate</i> and do all the work that you need to do.<p>You can't just keep abstracting things to work with ways of computing that are just more painful to work with. At one point the end-user has to adapt and simplify for his/her own sake. I wish I did sooner.