3 ms·

> Mandatory use of WebKit limits competition Exactly opposite! Right now we have 2 mobile browsers/engines. Without this we will have “Please use Chrome” on ev

by nuker 4y ago

> Mandatory use of WebKit limits competition Exactly opposite! Right now we have 2 mobile browsers/engines. Without this we will have “Please use Chrome” on every website and soon there will be only one left. Google won. The reason is simple. Today web developers have to make websites work with WebKit, because of iOS users. Tomorrow they will have a simple way out - ask user to install Chrome.

commoner 4y ago
Gecko (Firefox's native browser engine) is also a mobile browser engine, and Apple's anti-competitive WebKit requirement prevents browsers such as Gecko-based Firefox from being released on iOS. By forcing the use of WebKit, which is much more similar to Chrome's Blink than Gecko is, Apple is indeed limiting browser engine competition.
- nuker 4y ago
  Have you read my comment? You’ll have 100% Chrome very soon if all engines were allowed.
realusername 4y ago
The problem isn't having multiple engines, it's Webkit specifically, I'm fine coding for Firefox and Chrome.
- nuker 4y ago
  whats wrong with it
  - realusername 4y ago
    I've experienced layout bugs, form bugs, core js language issues, background issues, svg issues, navigation issues, they break indexdb or localStorage every other version as well, the list is very long. It's just a buggy engine due to the lack of investment in it in my opinion. And yeah on top of that they are also missing features.
    - nuker 4y ago
      But with 100% chrome users and zero Webkit users there will be zero investment and no bug reports very soon. I don't like having Google browser as my only choice, that will be death to any privacy and that was my point.
      - realusername 4y ago
        The gap between webkit and Gecko / Blink is widening every year though so that's pretty much what's happening.
    - nuker 4y ago
      > I've experienced layout bugs, form bugs, core js language issues, background issues Was that codebase optimised for Chrome? Maybe these bugs are only bugs because the code works only in Chrome? Did you check the browser implementation against W3C or IETF or some independent authority? Or there is no authority but only Chrome as a gold standard?
      - realusername 4y ago
        No, usually it works totally fine on both Firefox and Chrome and Webkit is in the wrong. As an example from this list, you have css background bugs in Safari mobile due to the way Apple implemented scroll snaping, this isn't a problem of a standard. The scroll can go further than a maximized full screen absolute div. Another example could be this issue preventing to use ES2020 minification on safari https://bugs.webkit.org/show_bug.cgi?id=220517 https://bugs.webkit.org/show_bug.cgi?id=220517 Overall it works but the details are just not polished enough.

by nuker 4y ago

commoner 4y ago

Gecko (Firefox's native browser engine) is also a mobile browser engine, and Apple's anti-competitive WebKit requirement prevents browsers such as Gecko-based Firefox from being released on iOS. By forcing the use of WebKit, which is much more similar to Chrome's Blink than Gecko is, Apple is indeed limiting browser engine competition.

nuker 4y ago
Have you read my comment? You’ll have 100% Chrome very soon if all engines were allowed.

realusername 4y ago

The problem isn't having multiple engines, it's Webkit specifically, I'm fine coding for Firefox and Chrome.

nuker 4y ago
whats wrong with it
- realusername 4y ago
  I've experienced layout bugs, form bugs, core js language issues, background issues, svg issues, navigation issues, they break indexdb or localStorage every other version as well, the list is very long. It's just a buggy engine due to the lack of investment in it in my opinion. And yeah on top of that they are also missing features.
  - nuker 4y ago
    But with 100% chrome users and zero Webkit users there will be zero investment and no bug reports very soon. I don't like having Google browser as my only choice, that will be death to any privacy and that was my point.
    - realusername 4y ago
      The gap between webkit and Gecko / Blink is widening every year though so that's pretty much what's happening.
  - nuker 4y ago
    > I've experienced layout bugs, form bugs, core js language issues, background issues Was that codebase optimised for Chrome? Maybe these bugs are only bugs because the code works only in Chrome? Did you check the browser implementation against W3C or IETF or some independent authority? Or there is no authority but only Chrome as a gold standard?
    - realusername 4y ago
      No, usually it works totally fine on both Firefox and Chrome and Webkit is in the wrong. As an example from this list, you have css background bugs in Safari mobile due to the way Apple implemented scroll snaping, this isn't a problem of a standard. The scroll can go further than a maximized full screen absolute div. Another example could be this issue preventing to use ES2020 minification on safari https://bugs.webkit.org/show_bug.cgi?id=220517 https://bugs.webkit.org/show_bug.cgi?id=220517 Overall it works but the details are just not polished enough.