News for hackers. Stuff that matters.
Re:Thoughts on Arc Browser by CharlesW on Wednesday November 09, 2022 @08:59PM (#33541193)
From where I sit, browser engines are commodities. There's not notable differentiation to be had there. Are four actively-developed, open source, mainstream browser engines enough? I think so, given that we haven't seen a downside to a relative monoculture in open source operating systems.
Re:Thoughts on Arc Browser by satvikpendem on Wednesday November 09, 2022 @09:00PM (#33541203)
Which are the four? I count Chromium, Gecko and WebKit.
Re:Thoughts on Arc Browser by rvnx on Wednesday November 09, 2022 @09:37PM (#33541504)
One day I discovered an independent engine: LibWeb (Ladybird Browser) which is developed from scratch. Quite brillant guys and effort.
Re:Thoughts on Arc Browser by still_grokking on Wednesday November 09, 2022 @10:16PM (#33541749)
Ladybird isn't mainstream. So it doesn't count in this list.

Blink (Chromium) and WebKit are also closely related as the former is a fork of the later.

So there are effectively only two "independent" engines.

But in reality there is actually none. Both engines exist through Google money.

Given that most people can't even tell the difference between the internet and the web (hello, Arc developers!) and the web became the new all encompassing platform (like MS Windows was before) we have here a very dangerous concentration of power. Almost all private computing is controlled end-to-end by Google these days.

If Microsoft got almost split up for having way less power Google is long long overdue for a divestiture. Should this ever happen (I suspect the US would not give up control of personal computing all over the world so it's imho unlikely, but if) everybody would recognize quite fast how bad the mono-culture in the browser space really is…

Re:Thoughts on Arc Browser by wereHamster on Wednesday November 09, 2022 @11:27PM (#33542198)
Blink has forked from WebKit a long time ago and only diverged since, they should be considered two engines.

WebKit itself forked from KHTML.

Re:Thoughts on Arc Browser by CharlesW on Wednesday November 09, 2022 @09:53PM (#33541606)
Re:Thoughts on Arc Browser by dmitriid on Wednesday November 09, 2022 @10:11PM (#33541712)
> Are four actively-developed, open source, mainstream browser engines enough? I think so, given that we haven't seen a downside to a relative monoculture

We have a near-monopoly with Chrome, a very distant second Safari, and a nearly non-existent Firefox. Anything else (like Goanna or Flow) have literally zero impact.

Chrome's outsized influence is such that it no longer even pretends to care about consensus or processes at w3c and just ships random features at neck-breaking speed.

Re:Thoughts on Arc Browser by AgentME on Thursday November 10, 2022 @02:34AM (#33543375)
What features is Chrome shipping that it shouldn't?
Re:Thoughts on Arc Browser by dmitriid on Thursday November 10, 2022 @05:00AM (#33544395)
The question isn't "should or shouldn't". The question is how.

Web standards are supposed to be based on a) consensus and b) at least two independent implementations.

As an example, let's take a recent Chrome-only non-standard that made HN frontpage, WebTransport: https://web.dev/webtransport/

The status of this API? "Editor's Draft". That is, scribbled on a napkin [1]

--- start quote ---

These drafts have not received formal review and are not endorsed W3C.

These drafts MUST NOT be cited as W3C standards and may or may not become W3C standards.

--- end quote ---

Guess what its status is in Chrome? Already shipped, and advertised as available.

As with other such non-standards expect HN comments decrying other browsers as being "the new IE" because they are in no rush to develop this.

[1] https://www.w3.org/standards/types#ED

Re:Thoughts on Arc Browser by graftak on Thursday November 10, 2022 @07:56AM (#33545761)
And the worst thing is when you call out Chrome for being the new IE instead[1] you get jousted by your web development peers because their dev tools are so great and other browsers are too slow to implement.

[1] Pushing through (user hostile) apis without consideration about others