Live data from Hacker News

Internet Explorer 11 (IE11) to be retired on June 15, 2022

blogs.windows.com

171–180 of 304 posts

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#171

Earlier quoted context omitted.

I think that's what happens when your root is in enterprise software or at least some of your heritage is in enterprise. I have no great love for MSFT but I agree with you about their willingness to support things well past their expected expiration. IIRC they even went so far as to detect programs that used some "bugs" in earlier versions of Windows and emulated those same buggy behaviors just for those programs.

Too lazy to look but I believe someone in a vm went from windows 1.0 to windows 7 (with all upgrades in between) and some of their personalization options from 1.0 (or maybe 3.11) were still present in 7. Insane!

Windows 1 to Windows 7: https://www.youtube.com/watch?v=vPnehDhGa14 (set colour schemes disappear at XP, but programs continue to work)

Follow up - Windows 1 to Windows 10: https://www.youtube.com/watch?v=PH1BKPSGcxQ

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#172

I smell a lot of nostalgia in this thread, and rightfully so! IE has been a terrible browser, but it was our terrible browser. But fear not! Outlook still uses the HTML parsing engine from MS Word (!) to display your HTML emails, and it's not going anywhere.

"but it was our terrible browser."

Don't you dare include me in "our" 8)

My first browser was telnet (1992ish) From 1993 onwards it was all a bit weird in internets land.

For me the golden time for wwwbly_internets was around 2000-5 or so. /. was still (just) worth reading, FB was still a bulge in MZ's trousers. Google was cool, Amazon was clever, Apple was cool. The www was still interesting - US frontier like.

I am of course joking. Today's www is not the same as that in say 2000. Google is not cool, Apple is not cool, Facebook is unpleasant, Amazon is not cool and quite odd.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#173
The one thing I regret about this is that IE11 was stable. By 'stable' I don't mean 'not crashing', but rather stable as in 'fixed feature set'.

These days, sites and apps that support FireFox/Chrome tend to test only on latest versions. Which come out frequently and can and do break things. Supporting IE11 means it works in IE11. Supporting FF/Chrome means it mostly works in the latest tested version.

If devs were more aware of Firefox ESR version and tested against it, we could have more stability again.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#175

I smell a lot of nostalgia in this thread, and rightfully so! IE has been a terrible browser, but it was our terrible browser. But fear not! Outlook still uses the HTML parsing engine from MS Word (!) to display your HTML emails, and it's not going anywhere.

"but it was our terrible browser." Don't you dare include me in "our" 8) My first browser was telnet (1992ish) From 1993 onwards it was all a bit weird in internets land. For me the golden time for wwwbly_internets was around 2000-5 or so. /. was still (just) worth reading, FB was still a bulge in MZ's trousers. Google was cool, Amazon was clever, Apple was cool. The www was still interesting - US frontier like. I am…

eBay has changed very little since then if that helps, however PayPal might as well be unrecognisable.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#176
post #155

Earlier quoted context omitted.

There are good reasons to reject a lot of it. You don't want JS running in an email for example. Or even some of the fancier CSS abilities.

By "I wish that emails could just work like everything else on the web" I meant modern web HTML/CSS - I was replying to the GP - not the full set of browser capabilities such as Javascript. I suppose it's possible you'd also want to exclude certain CSS abilities, but at that point you're now diverging from the web CSS spec which isn't ideal either.

Web standard is continuously evolving but email don't need most of them. I think whitelist approach is better than blacklist for email.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#177

I smell a lot of nostalgia in this thread, and rightfully so! IE has been a terrible browser, but it was our terrible browser. But fear not! Outlook still uses the HTML parsing engine from MS Word (!) to display your HTML emails, and it's not going anywhere.

If they took the Edge rendering engine (which is really like Chromium or some close approximation of it now) and put it in the IE UI instead of the opposite, I think that would get a lot of praise from me and probably many others including all the Google-drunk web developers. Those who like IE and prefer it to other browsers are doing so despite its horrible rendering engine.

I doubt such users had used Chrome frame instead of Chrome.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#178
post #85
post #80

Earlier quoted context omitted.

When Outlook becomes a PWA (currently in test, I think it's probably two-three years from stable), it'll be rendering mail with all the functionality of Blink. Which depending on your point of view, means a sigh of relief or time to buy more RAM. https://www.windowscentral.com/project-monarch-outlook-web-u...

More RAM or worse performance? I doubt it, given the COM addons my employer stuffs in my Outlook client. Zipmail among others.

If you want to switch to this, PWA install is available for Outlook Web App right now (just sign into outlook.office.com and click on the plus button that appears in the address bar in Edge or Chrome). If you don't have any crazy mail needs it works fine.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#179

I am just waiting to hear back from a customer on a support ticket request where functionality in my app is not working as expected. They sent me a screenshot of what should be a form in a modal but the modal has failed to load so it has loaded just the form in a new page looking pretty unstyled. The JS for the modal uses fetch() so possibly why it broke. I'm 95% sure that the browser in the screenshot is IE10. I poi…

Not accusing you of this, but the primary reason people run outdated software is a really problematic insistence, mostly by front-end people, on using the new-and-shiny instead of the tried-and-true. Breaking changes galore - so people stick with the past as much as possible. Example: Office 365 OWA doesn't work well on modern browsers other than the latest version of Edge on Windows. But it does work fine on browser…

Pretty sure the primary reason people stayed stuck in IE for so long was that Microsoft shipped it by default until very, very recently (even in home editions of windows).

You can add on top of that the rebranding they went through. If they had just done what they did now, and shipped the old rendering engine inside the new one as some kind “legacy mode” that sites could request then everyone else could have moved forward years ago and not had to deal with a stagnant browser.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#180
post #15

By moving to Microsoft Edge, you get everything described above plus you’ll be able to extend the life of your legacy websites and apps well beyond the Internet Explorer 11 desktop application retirement date using IE mode. Internet Explorer mode in Microsoft Edge will be supported through at least 2029. While IE11 as an independent program is going away, the rendering engine is still around for 8+y. Here's hoping th…

We have a critical 3rd party business app that absolutely requires IE11 (actually it requires IE11 to be in compatibility mode for IE5 or something). We currently use Internet Explorer only for this app and I think we will welcome the change to IE11 mode in Edge. Luckily it only to last another year or so before we replace this product. Some people don't understand the cost and effort required to replace some of thes…

[deleted]
Post reply on HN