Legacy system modernization is a process that requires planning and accounting for the future. Ideally, your approach to important terminal applications will give you the tools to stay running in the future, making it easy to introduce new devices and browser environments built off of old preferences. Solutions that run apart from plugins and other messy downloads give you the freedom to integrate directly with the latest options for long-term sustainability.
One reason to consider a web-based approach is to keep a continuous workflow as new technological demands arise. With the expectations of "always on" internet, businesses could be more reliant on dashboards and other systems that are linked and primed for consistent development. Optimization relies on keeping disruption to a minimum and safeguarding interactions between systems new and old.
Another concern is the declining relevance of languages like Java, once prominent in web development but now becoming less prevalent for coders. In some cases, those with a background in Java are having to learn newer languages to adapt to tech changes, with the results being a slow trickling out of older ways of coding.
Finally, the worries around proper enterprise app management extend to workflow. Companies focused on equal screen access for their web services will have less of a problem with "funneling" different kinds of data through the one system and user that can process them.
With these and other changes affecting all major organizations with IT needs, the question becomes how ready administrators are to keep running their emulators into next year and beyond.