Live data from Hacker News

Is Chrome the New IE? (2023)

magiclasso.co

281–290 of 316 posts

Re: Is Chrome the New IE? (2023)

#281
post #90

Earlier quoted context omitted.

Possibly. I guess XUL was that API, but XUL is no more. It helps if your company uses the embedded stuff in other products. Like Microsoft used the Trident engine from IE6 all over Windows components. In that way, allocating resources for developing an embeddable engine is justifiable. Can Mozilla do that? I don'know. Google can (and does it! why wouldn't they?).

There is GeckoView on Android: https://mozilla.github.io/geckoview/ On desktop, it used to be available as an ActiveX component and a GTK widget, at least: https://www-archive.mozilla.org/projects/embedding/embedding... Wine still uses WineGecko as a replacement for IE engine – might also be worth looking into.

> There is GeckoView on Android: https://mozilla.github.io/geckoview/

But sadly on Android the alternative is simply using a Chrome/Blink-powered webview, which is capable enough for most people and importantly comes at a zero APK size hit. So you need to have pretty special needs before including a complete custom browser engine inside your app becomes an attractive proposition.

(Whereas on Windows for example for a very long time the only OS-provided browser engine was IE, so if you needed more advanced web features, you couldn't avoid shipping your own browser engine in your application anyway.)

Re: Is Chrome the New IE? (2023)

#282

Earlier quoted context omitted.

It really depends on where in the world we're talking about. iOS is big in some places (like US) but insignificant in others.

iOS is important in all rich countries, and if you want to address wealthy people in developing markets. It is very important for these reasons.

In Europe Safari has decent 21%. Thus I would not neglect Apples web browser but calling it very important is going a step to far in my opinion.

Re: Is Chrome the New IE? (2023)

#283
post #77

Earlier quoted context omitted.

You do know that Edge is Chromium repackaged, like all other browsers except Safari and Firefox?

So then why does Microsoft try to push it so hard on users who are trying to use Chrome? It's hard to believe they're just trying to save everyone the minimal time and effort that's being spent installing a different browser by randomly deciding to force a full-screen ad on an OS update. At absolute best, it's benign but worth not using simply to avoid rewarding whatever misguided incentives lead to them to "market"…

Edge integrates to Windows, Chrome doesn't.

You can set parental controls on Edge using Microsoft's tools, not so for Chrome and Firefox.

Re: Is Chrome the New IE? (2023)

#284
post #123

Earlier quoted context omitted.

>It's not Chrome's fault for third party developers being lazy and not supporting Firefox. What if it's Google themselves? From my original post: > [...] and that often includes Google sites/apps

[Citation Needed] What google site or service requires Chrome?

There are less options for screen sharing on Google Meet.

Re: Is Chrome the New IE? (2023)

#285

No not even close by every single possible measure. I was there, I suffered through it, Google would have to make TONS of hostile moves for that fact to change. I have no interest in the arguments of a closed source subscription service that wants me to switch to the bundled browser of the wealthiest company on earth's most popular consumer OS, lecturing me about using the 4th wealthiest company on earth's browser th…

Safari hasn't actually been particular far behind implementing industry standards. As far as I can tell, it's more that people seem to believe that Google dictates industry standards and base everything on when Chrome supports it as opposed to when it actually gets standardized. SSE's W3C draft standard in 2012. Supported in Safari in 2010. web sockets This one is true. IETF standard 2011. Supported fully in Safari 2…

As usual, there's supported and "supported" with Safari, nobody could build an IndexedDB app in 2014 supporting Safari, I've been there. It's only been really stable through the past 3 to 5 years max.

Re: Is Chrome the New IE? (2023)

#286
post #206

Earlier quoted context omitted.

It really depends on where in the world we're talking about. iOS is big in some places (like US) but insignificant in others.

It also depends on the kind of site. The more the operator thinks you should be using a desktop, the worse it is.

Yeah one non-profit is a place that people physically so I imagine a lot of people look at it on their cell phone. We have over half of our visitors on mobile.

Re: Is Chrome the New IE? (2023)

#287

Earlier quoted context omitted.

This is very misleading, compare implementation timelines between browsers and you'll see that Safari has implemented many of these things year(s) after chromium, firefox and even opera. This of course was because they have tried as much as possible to push people to closed source/walled garden apps.

I'd argue calling non-standard chrome/firefox/opera features "standards" is misleading.

This is plain bad faith. If you know anything about web standards, you already know the W3C process requires candidate implementations and interoperability before a standard reaches its later stages. Other browsers implemented the standards earlier because they participated in that process; calling those implementations "non-standard chrome/etc features" is absurd.

Re: Is Chrome the New IE? (2023)

#288
post #220

Earlier quoted context omitted.

VDOM would still exist if the DOM was faster. It's a different abstraction that reconciles the differences between the simple data->elements flow and the inherently stateful DOM. If you don't understand why VDOM exists, here's a nice experiment: in your next web app stop using VDOM and always set innerHTML. You'll find that (1) it's actually fast enough so you can conclude that VDOM doesn't exist just to patch over D…

Let's ask the next why. Why make the interaction with the DOM stateless? Because walking the tree sucks, and more specifically building upon the tree sucks a lot (createElement, appendChild, etc). That's why innerHTML, which was _not_ a standard, became a standard after being widely implemented and used. So, the solution was to almost never read the actual tree, because it is slow and weird. This was solved before Re…

[deleted]

Re: Is Chrome the New IE? (2023)

#289
post #230
post #228

Earlier quoted context omitted.

The only browser that seems to be able to get around this is Orion. No idea how they are doing it.

Orion is WebKit. Safari’s rendering engine is WebKit.

I know it’s WebKit. But they are somehow allowing extensions, which none of the other iOS browsers has managed afaik.

Re: Is Chrome the New IE? (2023)

#290
if any browser is the new IE, it's Firefox -- poor compatibility, very few people use it, but enough that makes people think we need to support it

https://analytics.usa.gov/

We're now at 0.8% Firefox usage on Gov't websites, that means Firefox support is no longer required at a gov't level (2% usage is the threshold)

Firefox should be shut down in 2025 if all trends continue

Post reply on HN