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

Is Chrome the New IE? (2023)

magiclasso.co

Post reply on HN
Print view View original

101–110 of 316 posts

Re: Is Chrome the New IE? (2023)

#101

Post by bawolff »

alganet wrote: post #95
darepublic wrote: post #94

Earlier quoted context omitted.

Babel/vdom is not necessary for web dev. Can't blame chrome for electron.

If something uses DOM and JavaScript, to me it's web enough to be called web, even if it is rendering outside of regular browser expectations (some React Native stuff or similar). The whole premise of this tech is to approximate app development to web development. Anyway, it's not about _blaming_. Web technologies are being laid in a landscape by multiple parties, it's about understanding that landscape.

Sheesh, the existence of libraries does not mean standards have failed.

Re: Is Chrome the New IE? (2023)

#102

Post by lxgr »

_fat_santa wrote: post #88

One issue I keep see cropping up with various corporate websites is they will only allow Chrome and will block any other browser. I would say in 9/10 cases, this isn't because the site uses features not supported in other browsers but rather, developers restrict it to Chrome because that's all their QA's test on.

Absolutely. I'm still not sure what annoys me more: Sites that break on non-Chrome, or sites that won't even let me try behind a cookie agent blocker.

Re: Is Chrome the New IE? (2023)

#103

Post by lxgr »

wslh wrote: post #100
_fat_santa wrote: post #88

One issue I keep see cropping up with various corporate websites is they will only allow Chrome and will block any other browser. I would say in 9/10 cases, this isn't because the site uses features not supported in other browsers but rather, developers restrict it to Chrome because that's all their QA's test on.

It's clear that Net Neutrality and web standards are close to a myth. Security-wise, I trust Google over Mozilla though.

That's a different layer of the stack. I could get behind "web neutrality" as an initiative, though!

Re: Is Chrome the New IE? (2023)

#104

Post by gtk40 »

MBCook wrote: post #11

Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…

I manage websites for a couple of non-profits. A very high percentage of traffic is from Safari (mostly on iOS) -- 40% on one site. Only testing in Chrome seems like a bad idea.

Re: Is Chrome the New IE? (2023)

#105

Post by bawolff »

wannacboatmovie wrote: post #9
curtis3389 wrote: post #6

Mobile Safari is the new IE. Random idiosyncrasies that are poorly documented dictated by the whims of a single corporation. Apple has broken stuff multiple times in the past few years.

Then it would be quite different from IE. Microsoft was so averse to breaking backwards compatibility, that IE stopped innovating and stagnated.

I don't think that is true. They stopped developing it full stop. Keeping back compat was not the issue.

Re: Is Chrome the New IE? (2023)

#106

Post by lxgr »

intellix wrote: post #23

Safari, the browser that claims to support standards but always comes with caveats, like saying they support transform/transitions and then everything with box shadows flickering

It's also very slow to support new standards, in my experience.

Web push notifications literally took years to make it from macOS to iOS, for example. (Yes, these are commonly abused for spam and other user-hostile things; no, I don't think that's a valid reason to withhold them from the only acceptable browser on their OS entirely.)

Re: Is Chrome the New IE? (2023)

#107

Post by lxgr »

threeseed wrote: post #45
est wrote: post #2

The only problem with Chrome: It's controlled by an advertising company.

And you see evidence of this influence throughout Chrome. For example, Apple simply blocked third party cookies which are almost exclusively used for tracking. Chrome waited years until they could add their Advertising Sandbox feature first.

You can see it much more clearly in the lack of an extension API on Android.

Chrome on Android is an absolute nightmare for one reason alone: No adblock.

Re: Is Chrome the New IE? (2023)

#108

Post by Y-bar »

wseqyrku wrote: post #15
MBCook wrote: post #11

Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…

> If it works on Chrome, no one cares or even tests for other things. We've been through an extensive standardization pass for this to not happen. Anything not matching the specification whether in Chrome or any other browser should be considered a bug. This is not at all the same as IE, where it just went its own way.

As I wrote in a similar thread a year ago: Whenever I point out that some bug which happens in Firefox my colleagues usually responds with some variant of "we tested in Chrome, and that is the standard", or "can you ask the customer to use Chrome instead". Even if Firefox or some other browser may be using a proper standards implementation and the Chrome one being the one with some quirk.

Re: Is Chrome the New IE? (2023)

#109

Post by perardi »

curtis3389 wrote: post #63
wannacboatmovie wrote: post #9

Earlier quoted context omitted.

Then it would be quite different from IE. Microsoft was so averse to breaking backwards compatibility, that IE stopped innovating and stagnated.

I was thinking more of every web app needing one or more "if isIE() {} else {}" blocks somewhere in its codebase. Now we have the wondrous pleasure of doing the same for Apple.

There are so many little bits of…weird in Safari.

https://developer.mozilla.org/en-US/docs/Web/CSS/WebKit_Exte...

Just this morning, I had to go down the WebKit pseudo-element rabbit hole to fix a layout bug in a very standard date-of-birth field.

Re: Is Chrome the New IE? (2023)

#110

Post by alganet »

bawolff wrote: post #101
alganet wrote: post #95

Earlier quoted context omitted.

If something uses DOM and JavaScript, to me it's web enough to be called web, even if it is rendering outside of regular browser expectations (some React Native stuff or similar). The whole premise of this tech is to approximate app development to web development. Anyway, it's not about _blaming_. Web technologies are being laid in a landscape by multiple parties, it's about understanding that landscape.

Sheesh, the existence of libraries does not mean standards have failed.

Sometimes it does.

Would normalize.css exist if the standards were more specific around default styles?

Would jQuery/sizzle exist if CSS selectors were available as a DOM API in the first place?

Would vdom exist if DOM was faster?

Post reply on HN