4 ms·
I'd normally agree, but "embedded device" in this situation means "network router" (which are reasonably powerful computers in their own rights), and the applic
by ANTSANTS 13y ago
I'd normally agree, but "embedded device" in this situation means "network router" (which are reasonably powerful computers in their own rights), and the application is not mission critical with hard deadlines and strict memory requirements, but just a web interface that is rarely active and can take as long as it wants running in the background. It doesn't seem unreasonable to me to set aside some portion of memory for the web interface, give the PH7 process low priority, and hire some PHP web devs that actually know what they're doing to make the interface for them. More sense than letting the firmware developers hack something together in C anyway.
- geon 13y agoI'd say the better way would be to develop the entire GUI with static HTML + JS files talking to the embedded device through a REST-ish interface. That way you can get a clean separation of the front and back ends, and the web developers get to work with exactly the tech they are used to.
- ANTSANTS 13y agoI'm not a web developer, but that sounds pretty sane to me. However, the important part of their decision, I'm guessing, was not so much the PHP part, but the "get people who actually know about the web to do this for us." Someone has to build the site either way, and I'm guessing the embedded engineers they had working on it didn't really know how to go about that. EDIT: Another possibility is that they already had PHP devs working on their corporate site or whatever, and they wanted to use them instead of hiring another team.
- donut2d 13y agoI am a web developer and the static HTML + JS with a RESTful API sounds excellent.
- nly 13y agoThis is exactly what LuCI does on OpenWRT, except they use Lua, which is a sane language designed for embedded environments.