Yes, that is precisely Alex's point. Don't choose iOS, because it's hurting the open web by disallowing browser competition on its platform.
-
-
Replying to @mikesherov @slightlylate
Sorry but your argument has a nonsequitur. Is the problem consumer lock-in or hurting the web? The two are not synonymous. If the problem is consumer lock-in, iOS sucks but there's worse. If the problem is hurting the web then Chrome is more harmful than Safari.
2 replies 0 retweets 2 likes -
I'm not sure what the heck you are getting at. I'm a web developer. This conversation is about browsers following web standards so that developers have a common target for all users. Apple not only lags behind, they block alternatives on their hardware. That hurts the web.
1 reply 0 retweets 1 like -
Replying to @kenmorechalfant @robinberjon and
How does Chrome hurt the web?
1 reply 0 retweets 1 like -
Chrome is engineered for tracking, and tracking sustains an economic model with inherent scaling effects that fosters concentration and intermediary capture. This helps Google and to a lesser degree Facebook, and no one else.
3 replies 0 retweets 0 likes -
While I disagree with the premise, a discussion of this aspect needs to account for the diversity in Chromium that enables (and encourages) different takes on this like Samsung, Brave, and others.
1 reply 0 retweets 0 likes -
Which premise? There are also limits to what Chromium enables. Some of the major integrators have told me first hand that when they wanted to add privacy features Google intervened to stop them.
1 reply 0 retweets 0 likes -
New features in the codebase require some socialisation, but if they were proposed with CLs that added flags, I'd like to dig into that and understand what happened. We are accountable for enabling a diverse of views in the codebase.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @robinberjon and
Obviously, can't say we'll take all features upstream -- contributor reputation for maintenance, testing, and bot hygiene matters -- but in general a motivated team should be able to land a "different opinion" upstream. It's one of the things that caused us to fork, after all.
1 reply 0 retweets 1 like -
Replying to @slightlylate @robinberjon and
Having tons of features behind flags is usually not scalable from eg. a testing point of view. Combinatorials and tragedy of the commons kicks in. Also, isn't it partly why Blink forked from Webkit (eg. disagreement on landing what became ITP)?
1 reply 0 retweets 1 like
Disagreement on landing Web Components was straw that broke
's back & why we want to take downstream needs seriously. We aren't perfect, but remember doing most of the commits and having very little influence. We don't want a project that disrespects contributors that way.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.