3 ms·

Honestly, if what you're doing works, go for it. Using javascript/html as an internal tool for UI building seems like a fairly decent use-case. You could write

Honestly, if what you're doing works, go for it. Using javascript/html as an internal tool for UI building seems like a fairly decent use-case. You could write your UI in some sort of native toolkit like QT/Gtk/etc but then you're pumping dev cycles into making something that already exists and works fine...for what? If everyone who uses your UIs already has a browser, then you've hit a sweet spot: your client software is already pre-installed on all the machines you need it to be, and the rest is serving HTML/javascript. The alternatives for you are probably pretty time-intensive for you and probably annoying for your users ("hey, install this program/app/etc"). I'd say if you want to rely less on JS and use more server-generated HTML, PHP might be the simplest option for you. People around here shit on PHP, but PHP was "serverless" before it was cool and has a lot of tools to do exactly what you're doing. But again, ask yourself what you gain by switching to another technology.

pdimitar 7y ago
PHP is definitely an awful recommendation for a RPi 4 though. There are lighter weighted options that optimise for minimum latency and minimum CPU overhead.
- orthecreedence 7y ago
  If it's an rpi serving 400 req/s, yeah you're probably right. If we're talking more about maintenance by a handful of people and a few hundred internal users, PHP is fine and an rpi can handle that load just fine. What minimal alternatives would you suggest given the constraints?
  - pdimitar 7y ago
    As mentioned in a sibling comment of mine, there are some alternatives: - Elixir's Nerves: https://nerves-project.org https://nerves-project.org - Golang: + https://github.com/tinygo-org/tinygo https://github.com/tinygo-org/tinygo + https://gobot.io/ https://gobot.io/ + https://github.com/golang/go/wiki/GoArm https://github.com/golang/go/wiki/GoArm - Rust I suppose you can just directly compile for any SoC like the RPi.

pdimitar 7y ago

PHP is definitely an awful recommendation for a RPi 4 though. There are lighter weighted options that optimise for minimum latency and minimum CPU overhead.

orthecreedence 7y ago
If it's an rpi serving 400 req/s, yeah you're probably right. If we're talking more about maintenance by a handful of people and a few hundred internal users, PHP is fine and an rpi can handle that load just fine. What minimal alternatives would you suggest given the constraints?
- pdimitar 7y ago
  As mentioned in a sibling comment of mine, there are some alternatives: - Elixir's Nerves: https://nerves-project.org https://nerves-project.org - Golang: + https://github.com/tinygo-org/tinygo https://github.com/tinygo-org/tinygo + https://gobot.io/ https://gobot.io/ + https://github.com/golang/go/wiki/GoArm https://github.com/golang/go/wiki/GoArm - Rust I suppose you can just directly compile for any SoC like the RPi.