Comment by gerash
6 days ago
Is Chrome being run so bad that we need even more committees, councils and bureaucrats to implement every single feature ?
Microsoft is already using the Chromium and changing the default search engine to Bing and shipping it as Edge. What else is needed?
This DOJ looks like they just want to pad their resumes with some grandiose case which might be bad for everyone else.
Chrome isn't being run bad because of committee, it's being run bad because it's used by Google as part of their web advertising empire.
Notice how their web advertising empire, which they do have a monopoly on (unlike Chrome), is not being broken up?
There is a separate, ongoing antitrust lawsuit over Google’s adtech business. Closing arguments in that case are scheduled for Nov. 25, next week: https://www.nytimes.com/2024/09/27/technology/google-antitru...
Chrome is not run badly at all. But in its current state it gives Google the ability to singlehandedly dictate webstandards. Thats an issue.
That doesn't go away with not Google. It's the result of having a browser with such big market share.
I think the point is to stop adding more features. The web is feature complete, everything Google is adding is just stuff to make them more money through ads and lock in.
That's not true, plenty of great stuff is shipping every year. Take your pick: https://web.dev/series/baseline-newly-available https://web.dev/blog/baseline2023
This is what Microsoft thought when they released IE6, and is why we ended up still supporting IE6 into the 2010s
That is not true at all. Plenty of features added expands the capabilities of what can be built for the browser
is that based on feelings or facts?
There’s nothing wrong at all with adding features as long as more than one browser/engine actually adopts them.
There’s an argument to be made that a high pace of new feature additions effectively functions as a moat that ensures that new competitive web engines cannot be developed as a result of not being able to ever catch up.
1 reply →
Oh come on, I for one am excited about the upcoming WebKmem API that allows random websites direct access to kernel memory..
How else are web devs supposed to write kernel modules?