3 ms·

If you are correct, let's ensure the browser duopoly is broken up first, rather than forcing Apple to open the market for Google to corner it. Then it will trul

If you are correct, let's ensure the browser duopoly is broken up first, rather than forcing Apple to open the market for Google to corner it. Then it will truly be a monopoly and all consumers lose.

manderley 3y ago
Why would the Chrome engine being dominant be all that problematic? And as a user, I'd like to make that choice for myself. Also, Safari wouldn't vanish just because you'd be able to use a different browser engine. I strongly disagree with your "scary" (not scary) scenario: Only a small percentage of users is ever going to change defaults.
- tremon 3y ago
  https://en.wikipedia.org/wiki/Browser_wars#Second_browser_war_(2004%E2%80%932017) https://en.wikipedia.org/wiki/Browser_wars#Second_browser_wa... The growing number of device/browser combinations in use, legally-mandated web accessibility, as well as the expansion of expected web functionality to essentially require DOM and scripting abilities, including AJAX, made web standards of increasing importance during this era. Instead of advertising their proprietary extensions, browser developers began to market their software based on how closely it adhered to standards. As soon as one browser dominates, one company gets to dominate how the web works. If you, as a user, want to be able to choose your own browser you should oppose one engine becoming dominant.
ThatPlayer 3y ago
Apple's monopoly is currently harming competition/consumers. Why should a potential monopoly that doesn't exist (yet) and doesn't hurt competition or consumers be a higher priority?
- jeffbax 3y ago
  As an Apple user and web dev, I like some of their restrictions because I prefer incentive to build native apps for things I do all the time. They’re usually showing a lot more polish and integration. Every time Twitter or Instagram bring up their custom share sheets I get super annoyed it’s not the default. PWA’s can probably get a lot of that, but a ton of web UX is arbitrary, unique, and more likely to feel janky in ways. Even for well done web apps, like Notion, it stands out like a sore thumb when parts of the editor don’t work like normal Mac input controls. I think PWA’s will have a lot of uses, but I don’t want them to take over either or Google get a browser monopoly. It’s bad enough how many devs don’t use anything but Chrome when testing. The web is what it is because it is not beholden to one company like the IE6 days

If you are correct, let's ensure the browser duopoly is broken up first, rather than forcing Apple to open the market for Google to corner it. Then it will truly be a monopoly and all consumers lose.

manderley 3y ago

Why would the Chrome engine being dominant be all that problematic? And as a user, I'd like to make that choice for myself. Also, Safari wouldn't vanish just because you'd be able to use a different browser engine. I strongly disagree with your "scary" (not scary) scenario: Only a small percentage of users is ever going to change defaults.

tremon 3y ago
https://en.wikipedia.org/wiki/Browser_wars#Second_browser_war_(2004%E2%80%932017) https://en.wikipedia.org/wiki/Browser_wars#Second_browser_wa... The growing number of device/browser combinations in use, legally-mandated web accessibility, as well as the expansion of expected web functionality to essentially require DOM and scripting abilities, including AJAX, made web standards of increasing importance during this era. Instead of advertising their proprietary extensions, browser developers began to market their software based on how closely it adhered to standards. As soon as one browser dominates, one company gets to dominate how the web works. If you, as a user, want to be able to choose your own browser you should oppose one engine becoming dominant.

ThatPlayer 3y ago

Apple's monopoly is currently harming competition/consumers. Why should a potential monopoly that doesn't exist (yet) and doesn't hurt competition or consumers be a higher priority?

jeffbax 3y ago
As an Apple user and web dev, I like some of their restrictions because I prefer incentive to build native apps for things I do all the time. They’re usually showing a lot more polish and integration. Every time Twitter or Instagram bring up their custom share sheets I get super annoyed it’s not the default. PWA’s can probably get a lot of that, but a ton of web UX is arbitrary, unique, and more likely to feel janky in ways. Even for well done web apps, like Notion, it stands out like a sore thumb when parts of the editor don’t work like normal Mac input controls. I think PWA’s will have a lot of uses, but I don’t want them to take over either or Google get a browser monopoly. It’s bad enough how many devs don’t use anything but Chrome when testing. The web is what it is because it is not beholden to one company like the IE6 days