From: nunojsilva@invalid.invalid   
      
   On 2025-12-27, rbowman wrote:   
      
   > On 27 Dec 2025 08:29:46 +1000, Computer Nerd Kev wrote:   
   >   
   >> That's fine, you want to write an application in a web browser, you can   
   >> do that. I won't use it because I think it's a wasteful and fragile   
   >> approach, but I'll find/write a native program instead.   
   >   
   > Real world scenario: The legacy system consisted of several Motif based   
   > GUIs, plus many backend daemons. For updates or bug fixes the GUIs have to   
   > be copied to several workstations in the dispatch center.   
   >   
   > It doesn't end there. In today's world every police car, fire engine, and   
   > ambulance has a laptop running applications. For bug fixes or updates with   
   > native programs you have to cycle each of those laptops through the shop,   
   > potentially a couple of hundred updates.   
   >   
   > Enter the web app. It runs in the browser, and is distributed from a   
   > central server. Update or make a bug fix on the server, all the client   
   > apps are automatically updated.   
   >   
   > Which is more resource intensive, has the most downtime, and has the   
   > potential for outdated native programs?   
      
   This still leaves the browser and the system to be updated. And HTTP(S)   
   caching.   
      
   I think the most sensible approach here could actually be the   
   purpose-specific non-web-application with versioning, so that several   
   versions can be run in parallel.   
      
   --   
   Nuno Silva   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)