zlacker

[parent] [thread] 14 comments
1. toyg+(OP)[view] [source] 2023-07-26 17:44:49
Apple don't have enough web properties to force this sort of change.

Google can turn around tomorrow and say that no browser without WEI can access GMail, GMaps, GSheets, Photos etc; people will have to comply, effectively killing any browser that does not support the feature.

This is the problem with the Chromium monoculture. "We", as generic IT people and developers on HN, definitely have a responsibility for not deprecating this monoculture earlier. If you use Brave, you're guilty; if you use Ungoogled Chromium, you're guilty; if you use Safari, you're guilty. It's high time people start taking responsibility.

replies(4): >>pjmlp+e4 >>meepmo+S5 >>db579+8q >>neural+PC
2. pjmlp+e4[view] [source] 2023-07-26 17:58:08
>>toyg+(OP)
And everyone that ships an Electron app as well.
replies(1): >>Klonoa+xh2
3. meepmo+S5[view] [source] 2023-07-26 18:03:41
>>toyg+(OP)
How are Safari users part of the Chromium monoculture problem?
replies(2): >>smolde+Q8 >>toyg+ea
◧◩
4. smolde+Q8[view] [source] [discussion] 2023-07-26 18:14:16
>>meepmo+S5
It's part of the KHTML monoculture that has been harming our industry and holding us back from real progress.
replies(2): >>mschus+Db >>meepmo+UC
◧◩
5. toyg+ea[view] [source] [discussion] 2023-07-26 18:19:50
>>meepmo+S5
They support another monopolistic player that would do exactly the same thing.

... oh wait, they already did. They force a monoculture on all the platforms they can get away with, and even shipped this WEI crap already.

◧◩◪
6. mschus+Db[view] [source] [discussion] 2023-07-26 18:24:34
>>smolde+Q8
If you want a browser engine it's either one of the KHTML descendants or Firefox. The problem is, both are ridiculously complex, only one family has the backing of three multi-billion dollar giants, and the other infamously suffers from "progressive disease" aka complete unwillingness to move fast and instead preferring to engineer the "perfect" solution.

That even Microsoft couldn't manage to keep up with progress only shows how utterly impossible it would be to kickstart a browser engine.

(The fact that Mozilla as an organization is embedded in constant infighting and utter incompetence doesn't help either)

7. db579+8q[view] [source] 2023-07-26 19:18:56
>>toyg+(OP)
Google can also decide at any time to put those web properties behind forced logins, or paywalls or just shutter them altogether. If Google doesn't want them to be part of the open web they won't be, regardless of whether this particular set of things is implemented or not. If we're all dependent on them enough that that's a problem for us, then that dependency is the problem.
replies(1): >>toyg+2F
8. neural+PC[view] [source] 2023-07-26 20:09:10
>>toyg+(OP)
If they do that then otrer browsers will appear
◧◩◪
9. meepmo+UC[view] [source] [discussion] 2023-07-26 20:09:15
>>smolde+Q8
That's kind of a stretch.
replies(1): >>smolde+tO
◧◩
10. toyg+2F[view] [source] [discussion] 2023-07-26 20:17:13
>>db579+8q
> If Google doesn't want [Gmail etc] to be part of the open web they won't be

The point is not that Google cares about those sites - they don't. Those services are leverage that they use to control web standards, in order to enable their real cash-cow: AdSense. They will use their web properties to shove down our throats anything that makes AdSense more profitable, from the anti-adblock measures in Chrome to this one.

> If we're all dependent on them enough that that's a problem for us, then that dependency is the problem

I don't disagree - and I use Firefox, keep my important mail outside of Gmail, etc etc. But I recognize that many, many people don't, so the technologically literal out there have an ethical responsibility to push back against corruption of the open web.

◧◩◪◨
11. smolde+tO[view] [source] [discussion] 2023-07-26 20:55:10
>>meepmo+UC
It's kinda hyperbole, to demonstrate how taut of a claim "Chrome monoculture" is.

We had a shot at open browser engine development with limited scope. Everyone said no, not just Chrome. Mozilla and Apple both have blood on their hands too, if we want to be reductive.

◧◩
12. Klonoa+xh2[view] [source] [discussion] 2023-07-27 08:21:50
>>pjmlp+e4
Sigh, no.

We would’ve gotten Electron any other way if it wasn’t Chromium, it’s the only endgame for UI given how native layers shat the bed.

Mozilla also no longer even supports embedding. ;P

replies(1): >>pjmlp+Qm2
◧◩◪
13. pjmlp+Qm2[view] [source] [discussion] 2023-07-27 09:05:48
>>Klonoa+xh2
Speaking as someone that has been doing native and Web for 30 years, it is the only game for developers that couldn't care, and in the process help Chrome to widen its market share and influence.
replies(1): >>Klonoa+ix2
◧◩◪◨
14. Klonoa+ix2[view] [source] [discussion] 2023-07-27 10:30:04
>>pjmlp+Qm2
I've been doing this for 20, which is enough to say: rattling off years of experience isn't going to win me over on this point.

> it is the only game for developers that couldn't care

Yeah, dude. Most devs literally do not care, they just want to write and ship stuff. The native stack(s) are not cohesive enough and the numbers do not lie; devs do not want to rewrite the UI n times.

Signed, someone who also does native and web UI dev. ;P

replies(1): >>pjmlp+6e3
◧◩◪◨⬒
15. pjmlp+6e3[view] [source] [discussion] 2023-07-27 14:31:28
>>Klonoa+ix2
Then don't complain about Chrome taking over the Web.
[go to top]