13 ms·
I feel like you aren't reading my replies so I'll keep this short. - We know Java Applets don't work on non-IE11 browsers and mobile devices, that's why we've
by Someone1234 7y ago
I feel like you aren't reading my replies so I'll keep this short.
- We know Java Applets don't work on non-IE11 browsers and mobile devices, that's why we've spent the last three years migrating to modern web standards, that's why we have mixed legacy/modern content, which incidentally exactly the scenario IE Mode was invented to solve. Thus the entire point of this feature and my post.
- If you ONLY have Java Applets IE Mode does nothing for you. It is a migration helper.
- Our time management system is from a popular vendor and uses modern web technologies, it isn't relevant here.
- No "proprietary IE technology" is used. The website has Java Applets built using Oracle's technology on it. IE11 supports Java Applets. Edge, Chrome, Firefox, Safari, and others do not.
- Companies have invested tens of years into now defunct technologies. Suggesting they migrate tens of years of investment in an eighth of the time isn't at all realistic or constructive. It is an ongoing process. We'll be stuck mid-migration for another five-ish years (thousands of man hours still to go).
- Thank you for telling me what the company should have done 12 years ago, and 8 years before I joined. Very constructive.
- close04 7y ago> If you ONLY have Java Applets IE Mode does nothing for you Well that's the whole point. MS is forcing your company's hand into doing something about that site that's very important for you but somehow was ignored for years. Everyone knows most companies won't move a finger without external pressure. MS is providing that pressure. The only alternative would be to build support for Java applets into a modern browser. Which is exactly what everyone tried to get rid of. So expecting IE mode to fix that issue for you makes no sense. I don't understand how this could even be a complaint.
- Someone1234 7y ago> MS is forcing your company's hand into doing something about that site that's very important for you but somehow was ignored for years. You just replied to a post that said verbatim: "we've spent the last three years migrating" with this. So, no. If you had read the previous posts in the thread you'd know that already.
- scarface74 7y agoThe point I’m making is waiting until 2016 to move away from Java applets is about like waiting until December of 1999 to be sure your system is y2K compliant. I was working with companies in 2008-2010 to move away from Java applets. Everyone saw the writing on the wall a decade ago when it came to depending on plug ins.
- deleted 7y ago[deleted]
- scarface74 7y ago1. No "proprietary IE technology" is used. The website has Java Applets built using Oracle's technology on it. 2. IE11 supports Java Applets. Edge, Chrome, Firefox, Safari, and others do not. Those two sentences don’t go together. For all intents and purposes using Java applets in a browser is “IE only”. Companies have invested tens of years into now defunct technologies. Suggesting they migrate tens of years of investment in an eighth of the time isn't at all realistic or constructive. The industry has been moving away from Java applets since the introduction of the iPhone in 2007. Java applet deprecation is not a new or unforeseen development.
- Someone1234 7y ago> Java applet deprecation is not a new or unforeseen development. Not really a point of contention. Also not really relevant to this discussion. The whole "12 years ago a company [I didn't even work at] should have done X Y Z" isn't constructive, or remotely relevant to a discussion of IE Mode today and how it operates.
- scarface74 7y agoIt’s not about you. It’s about how should Microsoft move forward, and how long should they support older tech because companies don’t prioritize migrations from older technology. One of the major issues with Windows has always been that they have hack on top of hack to keep backwards compatibility. You can read Raymond Chen’s MSDN blog to get an idea of how bad it is. The answer has to be somewhere between Apple - not long enough to be appropriate for the Enterprise - and too long in the case of Microsoft where it slows down development, causes an increase security vulnerability surface, and causes Windows to be a resource hog compared to other operating systems.