I don't know, I'm using Flutter just fine for all that you're saying.
Ask HN: Write once, run anywhere front ends failed. Thoughts?
21–26 of 26 posts
Re: Ask HN: Write once, run anywhere front ends failed. Thoughts?
#22Web 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! It can be depressing that you have 20 electron applications running to put icons in the tray but heck... everybody wants…
I agree but to go further, for an MVP: Just release a regular web app that does a decent PWA!
In Chrome you can turn any page into an taskbar iconned app from the menu now. Tell your users to do that. Actually an easier “install”. Web APIs do so much and you can integrate with Dropbox/OneDrive for file access (or use the apis if you want).
Offline is available using service workers. Camera, location, touch, gyro, etc. are all available.
Re: Ask HN: Write once, run anywhere front ends failed. Thoughts?
#23Do 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. 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’ve been working on a complex desktop WPF application and I’m happy with the results.
Re: Ask HN: Write once, run anywhere front ends failed. Thoughts?
#24For some things, uxn/varvara will do; it is simple enough that it can run anywhere.
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.
For some things, C will do, especially command-line stuff, but also is possible to use SDL, etc.
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)
Re: Ask HN: Write once, run anywhere front ends failed. Thoughts?
#25Web 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! It can be depressing that you have 20 electron applications running to put icons in the tray but heck... everybody wants…
I agree but to go further, for an MVP: Just release a regular web app that does a decent PWA! In Chrome you can turn any page into an taskbar iconned app from the menu now. Tell your users to do that. Actually an easier “install”. Web APIs do so much and you can integrate with Dropbox/OneDrive for file access (or use the apis if you want). Offline is available using service workers. Camera, location, touch, gyro, etc…
[deleted]
Re: Ask HN: Write once, run anywhere front ends failed. Thoughts?
#26My 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.
It's worth looking into. I hope you find something that works :)