←back to thread

Is Chrome the New IE? (2023)

(www.magiclasso.co)
281 points bentocorp | 6 comments | | HN request time: 0.333s | source | bottom
1. crowcroft ◴[] No.42175843[source]
Yes, Chrome is the de facto standard, and often the only browser thoroughly tested against. Even now though it isn't as dominant as IE at its peak though.

No, Chrome isn't significantly behind on adopting new standards compared with other major browsers (I'm looking at you Safari). IE6 to IE7 was about five years!

replies(2): >>42176193 #>>42180676 #
2. ericwood ◴[] No.42176193[source]
I see so many ideological arguments around "X is the new IE" that neglect one of the worst pieces of IE 6's reign of terror: the stagnation. Working around all of its quirks and non-standard behavior had an extremely long half-life; the venn diagram of things that worked correctly across all major browsers at the time was very complex and messy. Even with the release of IE7 it took many years for people to adopt it, and IE7 was hardly a saint either.

There's a part of my brain I'll never get back devoted to all of these workarounds. So many hours lost to weird corporate networks that had quirks mode enabled, different box models (before the advent of the `box-sizing` CSS attribute), random omissions of standards (no `:hover` on elements besides `a`), etc.

replies(1): >>42177819 #
3. JimDabell ◴[] No.42177819[source]
> one of the worst pieces of IE 6's reign of terror: the stagnation.

This is the thing that I think developers today don’t seem to be able to get their head around. There was a fourteen year time period between Internet Explorer 6 being released and when it dropped out of usage worldwide. Even if you only had to support the USA, it was still eleven years. People could go their entire careers without ever knowing what it was like not having to support it. It paralysed front-end development for more than a decade.

replies(1): >>42178346 #
4. ericwood ◴[] No.42178346{3}[source]
Deprecating it if your site had much traffic was like pulling teeth! I worked at a company that had IT professionals as its main demographic in 2011 and it was a constant struggle. Lots of corporations were locked into IE6 because they had developed internal applications that relied on ActiveX controls or other non-standard APIs. IE7 was still pretty terrible, and it took even longer to drop support.

CSS was pretty bad but at least well-documented; debugging JS was a whole other hell. There was no such thing as dev tooling, and you got a small alert in the status bar when the page had errors, which opened a pop up that gave you the line number and very little other information. Supposedly you could connect it to VisualStudio and get a full debugging experience, but I never had the luxury. Lots of guessing and checking. Firebug was a huge deal when it launched.

replies(1): >>42179488 #
5. crowcroft ◴[] No.42179488{4}[source]
Oh man, the days of no dev tools. Man it really is incredible to think how far things have come.
6. troupo ◴[] No.42180676[source]
Which standards is Safari significantly behind on?

Note: you have to refrain from listing Chrome-only non-standards. You also have to refrain from listing standards that Chrome shipped years before actual APIs got standardized.