It’s the software that reads a sensor and lifts a railroad drawbridge.
You don’t lift bridges without a confirmation from the network after scheduling has made sure that there’s no trains coming. Most serious SCADA systems have a web front end. Whether an embedded system that’s accessible by a web front end constitutes ‘web-programming’ is a different question; I’d say most such systems have a web interface to their open architecture, rather than being web-applications. Just because the web is pervasive doesn’t really equate to all programming being web programming.
It’s the daemon that processes millions of payments in the middle of the night in a server room hidden away and is only accessible by command-line.
IME that’s quite rare. Lots of businesses want SOA ( whether or not it has merit ) and integrated enterprise systems, even if it’s just something which dumps the daemon’s configuration files in the right place for it to pick up that night.
It’s an HMI interface 400 feet up in an industrial crane lifting 40-foot containers off a container ship.
Do you really think that such systems aren’t automated and networked? How does the data get to the customer tracking a container?
It’s the daemon that tracks products walking out of a store that haven’t been paid for.
Again, the trend is to network such systems and collect their information, and the data for such networked devices ends up on the web. If your company is only offering non-web enabled daemons but your competitor offers web-enabled daemons - and given the trend of point of sale systems to be browser based, that’s a fairly obvious offering - you’re not competative.
It’s the java component that activates that little buzzer telling you your table is ready at your favorite fancy restaurant.
I’ve not seen these, but again, the point of sale system triggering it is likely to be “web-based” - networked and running on browser UI.
Where is the web in all of that? Huh? Where? The web is the niche.
Most of the systems I’ve worked on have had a web interface. Typically that’s been about one day’s effort on a six month project ( a REST API rather than a UI ), though I’ve also created quite complex SVG and JavaScript UI for non-web distributed applications ( using XMPP rather than HTTP ); there’s a fine line between a distributed application using SVG and a desktop application using XAML.
I don’t think that ‘web programming’ is a particularly useful term, as most of my programming in technologies that originated on the web - Java, XML, XHTML, JavaScript, XUL, SVG, RDF - have not been on ‘web sites’, and the programming I’ve done which has been on and of the web has been trivially easy compared to the bulk of the system. Adding a REST interface to a simulation of missile flight dynamics isn’t rocket science, but is ‘web programming’. Creating a good user experience ( whether on a web site or a stand-alone application ) isn’t ‘web programming’ - “learning to program has as much to do with writing interactive applications as learning to touch type has to do with writing poetry”.