But hacker news users won't do that because they complain about Apple not because they are close or monopoly, but they make squeezing money from web users a little bit harder
Chrome isn't exclusive to one platform, and conversely Android doesn't force you to use it across the entire operating system.
If Chrome is forcing Web standards even in places where no one wants them, the equal and opposite problem is that Safari has a long history of holding back Web standards that are inconvenient to them, and making the entire industry bend around them because their users don't have the option to just install something else.
Part of the problem is actually that Apple also won't really compete here. They want the vertically-integrated everything, and so WebKit everywhere other than their devices is a second class citizen. The support for its underlying stack anywhere else -- from Linux-based browsers like GNOME Web to runtimes like Bun using JavaScriptCore -- has come pretty much entirely from third parties, and there doesn't really seem to be any sort of toolkit analogous to the CEF that could be used to embed it into other applications.
If anything, the only viable effort to make WebKit available across platforms was Chrome.
Chrome isn't forcing web standards. Chrome is forcing Google's own APIs, and calling them Web Standards
I mean, Web Workers is something only Google could love. They could have provided an API that would let you give commands to the cache layer of the browser and it would have the speed and reliability of native code behind it and if the system wants to evict one piece of data from the cache to deal with storage pressure... it can. Instead they invented a Rube Goldberg machine which doesn't really do anything and you have to write another Rube Goldberg machine inside the first Rube Goldberg to get "offline operation as a service." And you've got to deal with all the async programming difficulties and unreliability and I know for years all the storage operations you could back it with are awful.
Like I'm the guy who signs off on the ticket being done and I've been the guy who answers the pager when it goes off in 2 in the morning and even when I'm getting a stage demo ready for somebody who has the improv acting and stage magic skills to make a 20% done app look like... magic I have to get that 20% functionality working 100% in some certain sense and the Web Workers API screams "you're going to mess around with this forever and it's never really going to work right" where the product is under or over baked.
So the discussion about PWAs is another one of those discussions that SV has with itself without involving the other 99% of software developers and web users. Google might have had a lot more luck pushing it had they involved a focus group of people in Minnesota or Dublin somewhere.
And of course that 1/3-baked notifications API just raises my hackles, like the first thing I am going to do with a new web browser is turn it off. I mean, every web site is already trying to spam me every way it can possibly spam me, the last things I need are another pop-up menu that covers content, another dialogue of any kind to close, and the possibility that I'll click the wrong button and get spammed.
(And in the "iOS sucks" department, notifications are a big part. I've found that if I have any kind of filtering or groupings I lose important notifications, I will find out i got a text message from my son a week after I get it, etc. To have a decent experience I have to turn filtering/grouping off and give notifications permissions to the few apps that I need notifications from)
Consider that if the web was created today, it would never be allowed to run on iOS. The next web-like thing won't be allowed run on iOS without new lawsuits.