Philips Hue Bridge v1 online services will be shut off after April 2020
Imagine you are designing the web server for some hardware like this.<p>You might write it in Go, dockerized and hosted it in Kubernetes in Google Cloud.  You might use a hosted mongo db and 3rd party auth service.<p>Now in 30 years time, Google Cloud will probably no longer exist, your database API will have changed beyond recognition, and your auth service has closed down.  IPv4 no longer exists and your hardware depends on it so you have to build all kinds of compat layers.  You won't be able to get hold of all the packages for your server side code.  The Go compiler probably won't even run on an OS 30 years from now.   Your staff have retired, and nobody new wants to learn a programming language from 30 years ago.<p>Maintaining a server side API, even a really simple one, pretty much costs 1 fulltime person forever.<p>This hasn't always been the case.  If you had written your code as a self-contained DOS executable back in 1990, you could still run it bare metal on some of today's hardware, or on any hardware without too much hassle in a VM. Hardware from 30 years ago running in a cupboard probably has a 50/50 chance of still being alive today, and if you had set up 2 backup machines at the time, you'd probably have something working now even with nobody touching it for 30 years, sans the occasional office move.