Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A conspiracy to kill IE6 (2019)

blog.chriszacharias.com

Post reply on HN
Print view View original

11–20 of 113 posts

Re: A conspiracy to kill IE6 (2019)

#11

Post by shadowgovt »

rekttrader wrote: post #7

So what you’re saying is you helped your billion dollar mega-corp use their monopoly position to destroy another monopoly and ensure chromium would be the next IE.

Browsers have a tendency to consolidate. I think "there is a dominant browser used by N-times-% of the userbase relative to the second-most-popular" is a feature endemic to the ecosystem.

Much like "You can switch off Google search any time you want, but people will keep using it as the default until there's another clear better option, and then most people will switch to that instead." If browsers are pretty interchangeable, why not use the best?

Re: A conspiracy to kill IE6 (2019)

#12

Post by bigstrat2003 »

rekttrader wrote: post #7

So what you’re saying is you helped your billion dollar mega-corp use their monopoly position to destroy another monopoly and ensure chromium would be the next IE.

That's a pretty wild take, considering that the author specifically said they randomized the order of suggested browsers. They didn't push Chrome, they pushed "anything but IE6".

Re: A conspiracy to kill IE6 (2019)

#13

Post by bitvoid »

LordDragonfang wrote: post #8
yjftsjthsd-h wrote: post #5

Earlier quoted context omitted.

> One of the worst things that's happened is nearly everyone converging on using webkit to render everything. Feels like slowly stepping backwards into the days when everyone writes for webkit rather than a more open internet. WebKit and Blink are separate engines.

Yes, but the latter is a fork of the former's core components.

It was forked over 10 years ago now. I doubt their shared past is even recognizable now.

Re: A conspiracy to kill IE6 (2019)

#14

Post by duskwuff »

rekttrader wrote: post #7

So what you’re saying is you helped your billion dollar mega-corp use their monopoly position to destroy another monopoly and ensure chromium would be the next IE.

That seems like a fairly disingenuous take, given that the upgrade banner on YouTube also suggested upgrading to IE8 or Firefox.

If anything, Microsoft was probably grateful that the YouTube announcement pushed so many users to upgrade to a newer version of MSIE.

Re: A conspiracy to kill IE6 (2019)

#16

Post by randomdata »

LordDragonfang wrote: post #8
yjftsjthsd-h wrote: post #5

Earlier quoted context omitted.

> One of the worst things that's happened is nearly everyone converging on using webkit to render everything. Feels like slowly stepping backwards into the days when everyone writes for webkit rather than a more open internet. WebKit and Blink are separate engines.

Yes, but the latter is a fork of the former's core components.

And WebKit is a fork of KHTML, so...

Re: A conspiracy to kill IE6 (2019)

#17

Post by Octoth0rpe »

I and every single other webdev I've known from the early aughts would immediately offer to buy this person a beer upon hearing this story in person. Those claiming that safari is the new chrome just don't understand how bad IE was at the time.

Re: A conspiracy to kill IE6 (2019)

#18

Post by coding123 »

bigstrat2003 wrote: post #12
rekttrader wrote: post #7

So what you’re saying is you helped your billion dollar mega-corp use their monopoly position to destroy another monopoly and ensure chromium would be the next IE.

That's a pretty wild take, considering that the author specifically said they randomized the order of suggested browsers. They didn't push Chrome, they pushed "anything but IE6".

I mean what he wrote is even less "wild" than the title of the post.

Re: A conspiracy to kill IE6 (2019)

#20

Post by duskwuff »

Octoth0rpe wrote: post #17

I and every single other webdev I've known from the early aughts would immediately offer to buy this person a beer upon hearing this story in person. Those claiming that safari is the new chrome just don't understand how bad IE was at the time.

Especially IE6, which was eight years old at the time, two major releases behind, and extremely buggy.
Post reply on HN