←back to thread

Is Chrome the New IE? (2023)

(www.magiclasso.co)
281 points bentocorp | 8 comments | | HN request time: 1.725s | source | bottom
Show context
asddubs ◴[] No.42169280[source]
Just to (mostly) preempt this because the exact same discussion is had every time this sentiment comes up: Isn't safari the new IE?

Answer: They both are like IE, for different reasons:

Chrome: Pushes proprietary extensions onto the web, which due to their absolute dominance others are somewhat forced to adopt, people develop for it and don't test in any other browser, just like IE

Safari: is coupled to operating system version, lags behind on implementing new features, thus single handedly slowing down when everyone can use new features. Has weird quirks that other browsers don't, just like IE (though not nearly as bad as IE)

So which is like IE? It just depends on what you mean when you say "like IE", the label applies to both because IE was bad for more than one reason

replies(5): >>42169318 #>>42169382 #>>42169462 #>>42169792 #>>42171127 #
dwaite ◴[] No.42169318[source]
If I understand - Chrome is like IE for pushing proprietary extensions, and Safari is like IE for not implementing those proprietary extensions?
replies(4): >>42169330 #>>42169332 #>>42169433 #>>42170312 #
do_not_redeem ◴[] No.42169330[source]
Safari is like IE for not implementing standards everyone else has agreed on and implemented.
replies(5): >>42169342 #>>42169380 #>>42169424 #>>42169441 #>>42169483 #
1. marxisttemp ◴[] No.42169342[source]
Did “everyone” agree on and implement them, or did Google implement them and force everyone else in the WHATWG to play catch-up since they’re dominant?
replies(1): >>42169408 #
2. do_not_redeem ◴[] No.42169408[source]
Maybe there are specific examples of that? But I can't think of any, and it certainly doesn't strike me as common. Random example:

https://caniuse.com/input-inputmode

Firefox: 2013

Chrome: 2017

Safari: Any decade now, I'm sure of it

replies(1): >>42169878 #
3. fingerlocks ◴[] No.42169878[source]
Your own link says it’s supported on Safari for iOS, for years now. It’s obviously not supported on MacOS because that attribute only applies to onscreen keyboards.
replies(1): >>42170392 #
4. hu3 ◴[] No.42170392{3}[source]
What makes you think onscreen keyboards are not useful in macOS if at least for accessibility reasons?
replies(1): >>42171790 #
5. fingerlocks ◴[] No.42171790{4}[source]
The browser feature under discussion is clearly intended for small screen mobile devices.

Accessibility keyboards are just keyboards from the web page’s perspective

replies(1): >>42174284 #
6. hu3 ◴[] No.42174284{5}[source]
It's clearly NOT intended only for small screen mobile devices.

There's no reason to restrict suggesting input types to mobile browsers only.

That's exactly why desktop Chrome and Firefox has support it for a long time now.

replies(1): >>42176961 #
7. fingerlocks ◴[] No.42176961{6}[source]
well apparently Apple disagrees
replies(1): >>42186705 #
8. hu3 ◴[] No.42186705{7}[source]
yeah, as usual. That's exactly the point