in reply to Re^2: Gtk image from memory
in thread Gtk image from memory

The thin client idea is fine if the user is on a thin client (only) device. If however they're not, and they have local data they want to work on, the thin client idea would require them to first upload their data to the mainframe (that's what a web app is, sort of), which can be tricky. Just as with software engineering itself, there are no silver bullets.

Replies are listed 'Best First'.
Re^4: Gtk image from memory
by cavac (Prior) on Feb 24, 2025 at 15:56 UTC

    I totally agree that, yes, there are no silver bullets. But regarding UI, modern web browsers come quite close in my opinion. And you can avoid lots of system administration work, especially when you have a large number of users.

    Didn't look into it for some time, but there are multiple approaches to handle this transparently.

    • The File System Access API: simplifying access to local files
    • Building an App that uses a Web browser internally. Using something like Flutter, you can probably compile it for Windows and Linux. This would still minimize doing a lot of OS specific stuff, but would give your the ability to add custom JS interfaces for things like file access. Since most of the logic is delivered from the webserver, you hardly ever need to update the local app.

    Of course, you could just bundle the Perl application and all required tools into a docker container and run it on the users computer. And still use the webbrowser as the UI, letting the boffins as Google figure out how the users OS does multimedia.

    PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP
    Also check out my sisters artwork and my weekly webcomics