3 ms·
One thing I've noticed is another niche that doesn't quite fit into the "corporation blocking updates" bucket. VMs. I've used a few services at work that run on
by apaprocki 15y ago
One thing I've noticed is another niche that doesn't quite fit into the "corporation blocking updates" bucket. VMs. I've used a few services at work that run on auto-started VM images and IE8 is installed on those images. It isn't that someone is blocking updates necessarily, it is just that it takes a human to actually go and update the main VM image and update the browser on it. This seems to make it persist longer than it should because VMs are either updated on some long time horizon or there is not a push to proactively change it if the current situation "just works".
- akie 15y agoI see your point, but wouldn't that concern vanish the moment IE updates silently, in the background, without the user even noticing? If that would be the case, they would start out with an outdated IE, but be automatically updated to the most recent version as soon as they connect to the internet.
- apaprocki 15y agoWell usually the VM images are completely locked down because they are throwaway. Every time one starts up, it starts up from the master and the master has the original IE8. So even if the VM did allow updates, it would silently create a new problem.. a potentially massive amount of waste as all the random VM images are always downloading/updating IE whenever they start up.