5 ms·

"actual" Firefox absolutely means using their engine.

by kevinmgranger 4y ago

briandear 4y ago
The average consumer doesn’t know the difference nor care. They want to open webpages and have them work.
- codedokode 4y ago
  There is a difference. Gecko might implement features that would allow sites to work and look better in Firefox (for example, smoother scrolling, better animations, new CSS/HTML/JS features and so on). But Apple doesn't allow other browser engines, and Firefox cannot use this as an advantage to compete with Safari. Also, if Apple allowed other browser engines with better support for new features, then web developers might stop caring about supporting Safari. This might be another reason why Apple doesn't want other browsers on their devices.
  - Spivak 4y ago
    Apple wants to make sure that all websites work on their phones out of the box the horror. Like take the alternative world where the first thing you have to do after setting up your iPhone is installing Chrome because developers found it less effort to just target Chrome. Are we better off?
- gernb 4y ago
  Plenty of webpages don't work in Safari because Safari doesn't ship the APIs that other browsers have been shipping for years.
  - dmitriid 4y ago
    Safari is my primary browser day in day out. The only pages that don't work in it are developed by people who believe that Chrome-only APIs are standard.
    - postalrat 4y ago
      Like web push. Supported in both chrome and firefox for ages. But apple not interested because it can replace apps with web pages.
      - al_borland 4y ago
        https://developer.apple.com/wwdc22/10098 https://developer.apple.com/wwdc22/10098
      - dmitriid 4y ago
        Yup. When you ask people "what exactly so horrible about Safari", WebPush is inevitably the number one thing, followed by a bunch of Chrome non-standards like hardware APIs. Truly, truly a horrible browser that is impossible to use (even though I've been using it for over 10 years now)
    - twism 4y ago
      web workers is an example of a standard api that only got implemented (partly) recently. they are more examples like ths
      - dmitriid 4y ago
        You mean Web Workers that were available in Safari since version 4? Or Shared Web Workers that were originally implemented in Safari version 5? No idea why they got removed to re-appear later, and I honestly can't care: I prefer browsers to be careful with standards than just rush forward. Why is it that these "examples" are never actual examples?

"actual" Firefox absolutely means using their engine.

briandear 4y ago

The average consumer doesn’t know the difference nor care. They want to open webpages and have them work.

codedokode 4y ago
There is a difference. Gecko might implement features that would allow sites to work and look better in Firefox (for example, smoother scrolling, better animations, new CSS/HTML/JS features and so on). But Apple doesn't allow other browser engines, and Firefox cannot use this as an advantage to compete with Safari. Also, if Apple allowed other browser engines with better support for new features, then web developers might stop caring about supporting Safari. This might be another reason why Apple doesn't want other browsers on their devices.
- Spivak 4y ago
  Apple wants to make sure that all websites work on their phones out of the box the horror. Like take the alternative world where the first thing you have to do after setting up your iPhone is installing Chrome because developers found it less effort to just target Chrome. Are we better off?
gernb 4y ago
Plenty of webpages don't work in Safari because Safari doesn't ship the APIs that other browsers have been shipping for years.
- dmitriid 4y ago
  Safari is my primary browser day in day out. The only pages that don't work in it are developed by people who believe that Chrome-only APIs are standard.
  - postalrat 4y ago
    Like web push. Supported in both chrome and firefox for ages. But apple not interested because it can replace apps with web pages.
    - al_borland 4y ago
      https://developer.apple.com/wwdc22/10098 https://developer.apple.com/wwdc22/10098
    - dmitriid 4y ago
      Yup. When you ask people "what exactly so horrible about Safari", WebPush is inevitably the number one thing, followed by a bunch of Chrome non-standards like hardware APIs. Truly, truly a horrible browser that is impossible to use (even though I've been using it for over 10 years now)
  - twism 4y ago
    web workers is an example of a standard api that only got implemented (partly) recently. they are more examples like ths
    - dmitriid 4y ago
      You mean Web Workers that were available in Safari since version 4? Or Shared Web Workers that were originally implemented in Safari version 5? No idea why they got removed to re-appear later, and I honestly can't care: I prefer browsers to be careful with standards than just rush forward. Why is it that these "examples" are never actual examples?