News for hackers. Stuff that matters.
Re:What will a Chromium-only Web look like? by Joeri on Wednesday June 22, 2022 @06:57AM (#31834356)
The chromium-only web is not google’s fault. It is a symptom of a body of web standards that has grown wild to the point of being all but unimplementable.

Building a browser for the modern standards-based web is effectively impossible, because it costs too much, takes too long, and requires a standing army to keep up with.

We are at an impasse. The standards cannot be deprecated because they are used all over the web, and because they are used all over the web a new browser maker has little choice except forking chromium or firefox. Even microsoft couldn’t afford to keep adding all the standards to their browser engine. Normally the solution for a messy overgrown implementation is a grand reboot. But we can’t do a grand reboot of the web because we cannot get rid of the legacy. The only viable strategy I see to have real browser engine diversity without giving up on compatibility is moving as much of the standards implementation as possible into JS modules, so new browser makers can start with a small engine that loads the publicly hosted standards modules.

Re:What will a Chromium-only Web look like? by ohgodplsno on Wednesday June 22, 2022 @07:47AM (#31834776)
>The chromium-only web is not google’s fault. It is a symptom of a body of web standards that has grown wild to the point of being all but unimplementable.

>Building a browser for the modern standards-based web is effectively impossible, because it costs too much, takes too long, and requires a standing army to keep up with.

I wonder which company grew their browser marketshare through ruthless advertising on their already-a-monopoly search engine, then began to compete with the other browsers by purposefully breaking their websites on other browsers (all by accident of course, hundreds of times), then began to implement their websites with alpha versions of their proposed web standards that only their browser properly implemented, leaving other browsers with a dreadful polyfill that had horrible performance on purpose, only to then basically force their proposals through the web standards body that they had made because they couldn't control the W3C, leaving everyone having to follow such great APIs as WebUSB or other badly-implemented-but-only-by-them flavor of the day API, all the way to forcing dreadful protocols like QUIC and HTTP/3, justified by their need to save up three bytes per request and making the user's experience better while they serve 2MB of tracking javascript and ads through DNS-cloaked servers.

I think the name was like... Gogle ? Golgool ? Can't remember.

Re:What will a Chromium-only Web look like? by moron4hire on Wednesday June 22, 2022 @10:17AM (#31836264)
> then began to implement their websites with alpha versions of their proposed web standards that only their browser properly implemented

That is the standardization process. The W3C won't ratify a standard that does not have draft implementations in the wild.

Re:What will a Chromium-only Web look like? by ohgodplsno on Wednesday June 22, 2022 @10:52AM (#31836767)
No. The standardization process does not call for you to make your public facing, extremely visited website use Polymer/ShadowDOMv0. You can implement your API and make a demo website/offer a beta test on your website so that people can try it out.

Making it the default and making the fallback only reasonably accessible by installing an extension that will rewrite your links (that all send back to the alpha-using version), causing every browser that isn't Chrome to slow down to a crawl while you happily display a "Hey, did you know the web is faster with Chrome?" isn't working through the standardization process, it is weaponizing it to sabotage other browsers.

Re:What will a Chromium-only Web look like? by guerrilla on Wednesday June 22, 2022 @07:07AM (#31834426)
> It is a symptom of a body of web standards that has grown wild to the point of being all but unimplementable.

A body of web standards that they lobbied for and to be in the form that they are...

Re:What will a Chromium-only Web look like? by Closi on Wednesday June 22, 2022 @07:50AM (#31834811)
… and are a member of … holding more seats than Apple and Google combined … and more than four times the vote share of Mozilla …

As an example, Google holds 18 of 39 seats on the Web Assembly Working Group. This means that if they whip their seats, they only need 2 additional votes to pass anything.

Re:What will a Chromium-only Web look like? by gsnedders on Wednesday June 22, 2022 @10:09AM (#31836175)
> As an example, Google holds 18 of 39 seats on the Web Assembly Working Group. This means that if they whip their seats, they only need 2 additional votes to pass anything.

That's making big assumption: that decisions are made by votes, and those votes are done purely based on participation.

And they're not. For decisions within the WG, they're normally done by some notion of rough-consensus (frequently, lack of significant dissent); actual votes within most WGs are relatively rare.

For decisions at the W3C level, it is admittedly done by votes, but it's one-Member, one-vote, so in that case all W3C Member are equivalent in power: Google, Apple, Microsoft, Mozilla all have their votes count as one.

This is pretty normal within industrial standards development organisations: voting happens at an organisational level, representing the industrial members, not based on individuals participating from those members. (There certainly are negatives associated with a disproportionate number being from a single organisation, but that's mostly related to disputes in meetings ending up with one individual arguing against ten.)

Re:What will a Chromium-only Web look like? by guerrilla on Wednesday June 22, 2022 @08:31AM (#31835199)
I think you meant Apple and Microsoft combined, right[1]?

1. https://www.w3.org/groups/wg/wasm/participants

Re:What will a Chromium-only Web look like? by Closi on Wednesday June 22, 2022 @12:57PM (#31838604)
Oops, yes!
Re:What will a Chromium-only Web look like? by account42 on Wednesday June 22, 2022 @10:05AM (#31836120)
A body of web standards they are still trying to expand right now.

The first step in saving the web needs to be to stop adding so many new standards that are only needed for "apps".

Re:What will a Chromium-only Web look like? by andrekandre on Wednesday June 22, 2022 @09:22AM (#31835697)

  > Building a browser for the modern standards-based web is effectively impossible, because it costs too much, takes too long, and requires a standing army to keep up with.

  > We are at an impasse. The standards cannot be deprecated because they are used all over the web, and because they are used all over the web a new browser maker has little choice except forking chromium or firefox.
could web assembly be a way out?

the browser just becomes an execution engine, the current "web stack" becomes a (cacheable) downloadable library, meanwhile other languages, ui frameworks etc can flourish in the browser (now a much more simple thing that anyone can implement)

maybe just pie-in-the-sky?

Re:What will a Chromium-only Web look like? by gernb on Wednesday June 22, 2022 @12:43PM (#31838386)
IMO No,

The web works because of HTML. HTML is scanable, searchable. It's what allows search engine to exist at all. HTML enables extensions. HTML is also generally responsive. HTML allows uses to be in control (see extensions). HTML allows uses to copy and paste and even for sites that try to prevent it users can go into devtools to get the text. HTML supports all of unicode and so is inclusive across all languages.

A world in which the browser is just an executable environment and people make random UIs means pretty much all of the above disappears. No more searching for content, no more extensions to block ads or block distrdacting feature. No more extensions for language translation, braille, accesabiltiliy. No more all language support, only whatever each framework decides to support, every page with different limits at different versions of the frameworks.

Re:What will a Chromium-only Web look like? by shadowofneptune on Wednesday June 22, 2022 @11:42AM (#31837517)
You cannot escape the politics of browsers by going to WebAssembly, because that's where WebAssembly was born. To use features outside of the original WASM spec, you have to consult a table and perhaps use a polyfill, like with CSS or JS features. Browser implementers have a large influence on the direction of the VM. For example, around a year into the original spec's development, it switched from being based on an abstract syntax tree to being based on a stack in a decision made by the browser teams [1]. A big change like that, a year in! The s-expressions in the text format are an artifact of that period, since tools already relied on their existence for optimization.

Anyone who writes a compiler or engine for WebAssembly is going to have to deal with the mess of web standards, unfortunately.

1. https://github.com/WebAssembly/design/issues/755

Re:What will a Chromium-only Web look like? by corrral on Wednesday June 22, 2022 @11:19AM (#31837185)
Accessibility and UI inconsistency are going to be serious problems with that. And UI inconsistency's already the curse of the Web—definitely not something that needs to get worse.
Re:What will a Chromium-only Web look like? by woojoo666 on Wednesday June 22, 2022 @11:30AM (#31837353)
I feel like the point of standards to to provide more structure on top of an execution layer. Think about the browser's file picker dialog. Now imagine if every browser had their own file picker API, and each website only bothered to support one of those APIs. Now as you browse the web, the file picker only works on some websites but not others
Re:What will a Chromium-only Web look like? by sicp-enjoyer on Wednesday June 22, 2022 @01:30PM (#31839098)
QuickJS (and various others) demonstrates that small teams can create fast and efficient JavaScript engines that comply with standards. Even though v8 is faster, it spends an order of magnitude more engineering effort for that marginal benefit.
Re:What will a Chromium-only Web look like? by yencabulator on Thursday June 23, 2022 @12:12PM (#31851151)
A Javascript engine is pretty far from a browser. It's too much work to write a browser even if you reuse the existing V8.
Re:What will a Chromium-only Web look like? by sicp-enjoyer on Thursday June 23, 2022 @11:56PM (#31857659)
I agree. The context of this comment is the user asking if Web assembly will make that effort easier. I don't think it will since getting good JS is already reasonable.
Re:What will a Chromium-only Web look like? by yencabulator on Friday June 24, 2022 @04:22PM (#31868804)
Yeah, it won't be the wasm itself that makes anything possible.

What might happen is that it ushers in technically-unrelated fashions, such as standard WASI interfaces to something slightly less insane than DOM+Javascript.

Just Canvas-over-WASI isn't the answer because of accessibility, but something like it might happen.

Re:What will a Chromium-only Web look like? by jakelazaroff on Wednesday June 22, 2022 @07:38AM (#31834674)
Who do you think has been pushing features into web standards at a breakneck pace? From where I sit, it’s mostly Google.
Re:What will a Chromium-only Web look like? by fooey on Wednesday June 22, 2022 @11:54AM (#31837682)
Unfortunately, their priority lately has been pushing "features" like FLoC and Manifest v3
Re:What will a Chromium-only Web look like? by xnickb on Wednesday June 22, 2022 @07:09AM (#31834443)
> moving as much of the standards implementation as possible into JS modules

Heh. Now you have two problems. One of them is JS, which was a mistake in the first place and now we can't get rid of it for similar reasons.

Re:What will a Chromium-only Web look like? by timw4mail on Wednesday June 22, 2022 @08:56AM (#31835443)
And Chromes dominance has nothing to do with all the advertising for Chrome on Google's websites...
Re:What will a Chromium-only Web look like? by i5Aj7PXGjUPy on Wednesday June 22, 2022 @07:42AM (#31834726)
> The chromium-only web is not google’s fault. It is a symptom of a body of web standards that has grown wild to the point of being all but unimplementable.

what exactly is the benefit of having a byzantine set of standards in the first place? Like why not just have a standard and not dick around with it?

Re:What will a Chromium-only Web look like? by daveoc64 on Wednesday June 22, 2022 @08:40AM (#31835295)
Frustration with the shortcomings of older web standards resulted in the prevalence of browser plugins like Adobe Flash, and non-standard technology like ActiveX.

If there are things browsers can't do natively, then someone will build their own way to do it and then you end up with non-standard implementations.

It's better to get everyone on the same page and develop an open standard.

Re:What will a Chromium-only Web look like? by GekkePrutser on Wednesday June 22, 2022 @06:13PM (#31842525)
Was that all though? I think part of this was just businesses attempting to lock the web into their tech. Microsoft has never wanted the web to be open, first trying to reinvent it with their own MSN. Then trying to lock it in with IE and ActiveX.

Adobe / Macromedia started from the designer perspective but Flash soon became a goal of its own because Adobe wouldn't give up that marketshare.

Only now all parties realise it's too big for one company to own. Well except Google perhaps.

Re:What will a Chromium-only Web look like? by daveoc64 on Wednesday June 22, 2022 @07:05PM (#31843039)
Flash was able to support file uploads, video streaming, and clipboard access long before the HTML and JavaScript specs allowed for this.

Users and website creators wanted these features and Flash was the way to do them.

Sure, other technologies like Microsoft's Silverlight allowed similar things, but Flash was so widely used it could be relied on to offer these features.

Even now things like clipboard access aren't supported in the same way across all of the major browsers.

Re:What will a Chromium-only Web look like? by GekkePrutser on Thursday June 23, 2022 @08:52AM (#31848349)
File uploads were in HTML almost from the start :) And video was not no, but it was a tricky thing to figure out, not just from an implementation but also licensing point of view. RealMedia was another player that dabbled in this market.

I think the disconnect was more with designers. They wanted visual tools back in those days and had no time for CSS and JavaScript. Adobe/Macromedia gave them what they wanted and also entrenched their commercial position this way (which Adobe already had in the paper publishing market!). It took a long time for the graphical guys to come on board with the open toolchains.

Macromedia wasn't a bad company as such as they did make the excellent Dreamweaver which did promote open standards, but Adobe corrupted them badly.

Re:What will a Chromium-only Web look like? by yencabulator on Thursday June 23, 2022 @12:15PM (#31851203)
The big thing Flash added to file uploads was resumability. Uploading a large video file with pure HTML features on the internet of 2006 tended to fail, and adding a Flash helper worked around that.

And I recall it enabled a progress bar, too.

Re:What will a Chromium-only Web look like? by ClumsyPilot on Wednesday June 22, 2022 @08:28AM (#31835168)
> The chromium-only web is not google’s fault

They got exactly what they wanted, but its not their fault?

Re:What will a Chromium-only Web look like? by Gigachad on Wednesday June 22, 2022 @07:25AM (#31834563)
We should convert browsers in to just a basic wasm window responsible for rendering html and running wasm. Then JavaScript and all it’s apis can become a shared library as a wasm package or something.
Re:What will a Chromium-only Web look like? by IshKebab on Wednesday June 22, 2022 @07:30AM (#31834607)
I'm not convinced that JavaScript is the difficult part. HTML/CSS rendering seems far more challenging.
Re:What will a Chromium-only Web look like? by Gigachad on Wednesday June 22, 2022 @07:43AM (#31834731)
Servo seemed to have pretty much got rendering working. I'm no expert but I feel like the hundreds of JS apis contribute a lot to the complexity. Just looking at the list here looks like it would take decades for a single person to complete https://developer.mozilla.org/en-US/docs/Web/API
Re:What will a Chromium-only Web look like? by replygirl on Wednesday June 22, 2022 @08:48AM (#31835364)
Re:What will a Chromium-only Web look like? by postalrat on Wednesday June 22, 2022 @09:56AM (#31836026)
Decades of work for a single person shouldn't take longer than 3 months for one of these mythical "100x" developers.
Re:What will a Chromium-only Web look like? by NoGravitas on Wednesday June 22, 2022 @10:40AM (#31836608)
It's the interaction of JS with HTML and CSS, combined with the expectation that all browsers will implement everything in ways that are functionally identical. Current "web platform" specs are in the form of algorithms/pseudocode rather than descriptions of desired behavior.
Re:What will a Chromium-only Web look like? by guerrilla on Wednesday June 22, 2022 @08:33AM (#31835220)
So... aren't we kind of coming full circle if we do that, going back to the JVM+Swing except this time it's boxed in a window and is more dynamic...
Re:What will a Chromium-only Web look like? by diggernet on Wednesday June 22, 2022 @02:01PM (#31839555)
No, we are coming full circle back to the days when a company might put up a website that was just a single Flash app, and you couldn't link directly to anything in it, you could only interact with whatever navigation they built into it.
Re:What will a Chromium-only Web look like? by Gigachad on Wednesday June 22, 2022 @06:44PM (#31842839)
Single page apps and wasm apps have full access to the URL and usually integrate well with it. With the age of SEO, everyone wants their pages fully linkable.
Re:What will a Chromium-only Web look like? by spacemanmatt on Wednesday June 22, 2022 @08:58AM (#31835455)
Seems like that sort of retrofit could take a good month, given the rate of churn in JS/frontend land. </sarcasm>
Re:What will a Chromium-only Web look like? by freediver on Thursday June 23, 2022 @11:58AM (#31850942)
Normally having one strong alternative would be enough, but in this case we have two - Gecko and WebKit.

The problem is not in the lack of browser rendering engines, but the lacking innovation and product features of the browsers running these rendering engines.

Re:What will a Chromium-only Web look like? by mdavis6890 on Wednesday June 22, 2022 @07:22PM (#31843186)
Basically - the web is what Chromium source code says it is - no more, no less, and no other.
Re:What will a Chromium-only Web look like? by alcover on Wednesday June 22, 2022 @08:19AM (#31835067)

  >  we can’t do a grand reboot
But a partial one, yes. Let's make new 'virtuous' sites using only a core subset of HTML/JS and fast and energy-efficient.

(inb4 XKCD) Yes, like a new standard.

Re:What will a Chromium-only Web look like? by SenHeng on Wednesday June 22, 2022 @10:03AM (#31836104)
You mean like AMP?