← Back to context

Comment by Ygg2

8 months ago

> Seeing someone ignore the naysayers and attempt the so-called impossible task of developing a new independent browser is awesome to see

Well the impossibility isn't so much in making a browser but making a browser that manages to get a chunk of web audience.

That means presence on mobile, feature and performance parity with Chrome, surprasing Chrome on some level (e.g. Safari having better vendor lock-in).

Safari is better than Chrome in many ways, arguably most.

  • Sure, it does have some benefits. Like lower energy consumption, I hear good things about JavaScriptCore (Safari's JS engine), that said, so many of the features are missing, and one part is it encroaching on the iOS apps territory.

    • The features missing thing was true years ago, but Apple significantly increased their investment in Safari about 3 years ago and it really gained ground. If you subtract all the Chrome-invented features, they aren't too far off.

    • > so many of the features are missing, and one part is it encroaching on the iOS apps territory.

      Be careful when listing those features. Many of those "encroaching" are Chrome-only non-standards

      4 replies →

  • A fact that appears to be lost on the majority of users that have a say in what browser they use: https://gs.statcounter.com/browser-market-share/desktop/worl...

    • The problem is that when Chrome came out it was heavily marketed/targeted towards developers. Developers took it up and then built websites in & for Chrome. The end result is many websites work better in Chrome than Firefox or Safari. It's a vicious cycle of continuing dependency.

      I'm doing my part to break the cycle by supporting the underdog by using Safari as my daily driver & developing primarily for Safari & Firefox.

      7 replies →