Live data from Hacker News

A Conspiracy to Kill IE6

blog.chriszacharias.com

241–250 of 386 posts

Re: A Conspiracy to Kill IE6

#241

Earlier quoted context omitted.

IE6 was pretty awesome when it was released... not having to support IE4.x and NN4.x when it hit sufficient market share was really nice. Eventually it became the next boat anchor. IE10-11 is the current boat anchor, and will probably cycle out within the next year. Already have internal apps with no IE support at all, and only the most recent Edge release. The perspective on outdated (insecure) browsers is becoming…

Our enterprise app (not internal) has 80% of users on IE11 :/

How is that even possible? Are they not allowed to use something else?

Re: A Conspiracy to Kill IE6

#242
post #226

Earlier quoted context omitted.

Our enterprise app (not internal) has 80% of users on IE11 :/

Did older versions of your app require IE? If so, their admins may have added your site to Enterprise Mode[0] so that it opens with IE. https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-...

Nope, this is a modern react/es6 app that's only about 5 years old.

Re: A Conspiracy to Kill IE6

#243

Earlier quoted context omitted.

Something that stuck out to me was how concerned Google was that even while recommending other browsers next to Chrome, that putting Chrome first in the list could rankle antitrust regulators. Fast forward to 2019 and Windows 10 makes you fight multiple menus and "suggestions" just to switch your default browser away from Edge.

Your comment is demonstrably nonsense. Windows 10 only suggests Edge if you make IE11 your default browser. If you choose Firefox or Chrome it never suggests that you should switch to Edge. Microsoft’s lawyers are not stupid.

I setup a new PC for my Dad over Easter weekend - Windows 10 prompted me to switch to Edge when I tried to set default browser to Chrome for him.

Re: A Conspiracy to Kill IE6

#244

Earlier quoted context omitted.

Our enterprise app (not internal) has 80% of users on IE11 :/

I'd suggest that comes down to the type of client/users you have... it's definitely not a common case. I'd also be willing to guess that most of those users also have a different browser installed. IE11 is pretty capable, but requires a lot of shims/shivs for modern code transpilation.

The customers have weird IE security tools/firewalls and are not allowed to use anything else.

For some reason they think that IE with very expensive tools to lock it down is more secure than a modern browser.

Re: A Conspiracy to Kill IE6

#245
post #66

Earlier quoted context omitted.

Yes. I love the story, and if I had been in charge I don't see how I could do anything but fire the whole lot of them. Although... the number of people involved in the "OldTubers" backdoor seems to have been pretty substantial, I don't know if they could really have fired all of them... But who is anyone to say if doing anything is "right"? We're all equally qualified to have a moral compass.

I'd keep them on board but I'd get rid of that backdoor and encourage them to adapt to the new situation, for a number of reasons: - 'OldTubers' vs. the new Googlers is a clear us v. them thing. Bad for culture, especially when you get privileges on top. - Their plan was actually successful so there must have been a thing or two to learn on the product side, even if it's as simple as accepting engineering input and u…

They’d quit and you’d kill morale. Something Yahoo would do.

Re: A Conspiracy to Kill IE6

#246

Earlier quoted context omitted.

Our enterprise app (not internal) has 80% of users on IE11 :/

How is that even possible? Are they not allowed to use something else?

Yes. The 20% not on IE only left after we convinced their it department to switch.

Re: A Conspiracy to Kill IE6

#247

This is the first example I've ever heard of where a browser-upgrade banner worked . Every time I've tried it on sites I've worked on, the "please upgrade" banner does nothing. Years ago, we even tried turning it into an intrusive pop-up for a percentage of users. They just clicked through the pop-up, presumably without reading it. I wonder if it worked in this case because it started a movement? > Between YouTube, G…

> I wonder if it worked in this case because it started a movement? I think this is the answer. Most people at the time weren't on IE6 out of choice. The fact that youtube (or more likely google docs) had this banner, gave disgruntled employees a better excuse to force IT to upgrade than "I don't like this browser"

The web was also a bit of a different place back then. I think there were people who were "power users" who used Firefox and Chrome and others who used IE because it was bundled with their browser.

Re: A Conspiracy to Kill IE6

#248

This is the first example I've ever heard of where a browser-upgrade banner worked . Every time I've tried it on sites I've worked on, the "please upgrade" banner does nothing. Years ago, we even tried turning it into an intrusive pop-up for a percentage of users. They just clicked through the pop-up, presumably without reading it. I wonder if it worked in this case because it started a movement? > Between YouTube, G…

> I wonder if it worked in this case because it started a movement? It was continuing a movement and giving it visibility outside web developers. The youtube banner happened mid-2009, web developers around the world had soured on IE6 and actively trying to kill it off since 2005~2006. What the youtube banner provided was a way to finally get the word out, and an argument to give PHBs: it became much easier to sell br…

I was stuck suppporting our biggest customer who ran IE6 until like...2013? Bleh.

Re: A Conspiracy to Kill IE6

#249
post #129

This is the first example I've ever heard of where a browser-upgrade banner worked . Every time I've tried it on sites I've worked on, the "please upgrade" banner does nothing. Years ago, we even tried turning it into an intrusive pop-up for a percentage of users. They just clicked through the pop-up, presumably without reading it. I wonder if it worked in this case because it started a movement? > Between YouTube, G…

IE6 was insanely bad. Later browsers worked somewhat.

We had a program that drew a map + path along the map... one customer complained about it taking 3 minutes to draw the path. Customer had an AMD 1400+ or something that was like 8 years old at the time. Threw my hands up in the air when they showed the system properties over a remote session.

We installed Firefox 4 and it ran at a perfectly fine speed...

Re: A Conspiracy to Kill IE6

#250

Anyone that started developing in the IE9 era or later cannot comprehend how painful it was to develop for IE6. You simply have no frame of reference whatsoever. Any gripes you have about IE9 or later sound like a joke in comparison. Even IE8 was a huge improvement.

Yeah agreed, although you could almost say the same thing about devs who started in the early Firefox era and how they have no frame of reference for the awful Netscape 4.x pain that IE 4-6 made go away...
Post reply on HN