1. 28
  1.  

  2. 58

    Safari isn’t the new IE, Chrome is. From the market share, to features only available on Chrome, to developers writing for Chrome only. Some of the points on this article even clearly show that.

    1. 22

      The “Widely accepted standards” in the OP made me laugh…

      When I file bug reports/support tickets to websites saying your website doesn’t work with X or Y browser, the answer I almost always gets back is: “Use Chrome.” Occasionally(and more and more rarely) I’ll get back, OH right, we should fix that. Clearly nobody even bothers to test their stuff in the “other” browsers.

      I keep filing tickets, anyway.

      1. 2

        But that’s only part of what IE did.

        On the upside, the core of Chrome is open source. Enabling Microsoft Edge to basically just rebranding it is good, in my opinion, because if chrome got bad, they could immediately increase pressure by doing some little things better. (Disclaimer: haven’t used Edge)

        What I mostly subject to in Chrome is that Google pushed it so hard and probably unfairly by its other businesses. And that is somewhat similar to what Microsoft did with IE and Windows.

        1. 4

          Most Google websites work way better in Chrome than in Firefox. And most of the time, that’s a decision from Google, not technical limitations in Firefox.

          • Google Meet lets you blur out your background. This feature only uses web features (like WebGPU) which are supported perfectly fine by Firefox - but it’s disabled if you’re in a non-Chrome browser. It used to be that you could just change your user agent in Firefox, and the feature would work perfectly, but then Google changed their browser sniffing methods and changing the UA string doesn’t work anymore.
          • YouTube uses (used?) a pre-standard version of the Shadow DOM standard, which is implemented in fast C++ in Chrome, but Firefox only implements the actual final Shadow DOM standard, so YouTube uses (used?) an extremely slow JavaScript polyfill for non-Google browsers.

          Those are only the cases I know of where Google explicitly sabotages Firefox through running different code paths based on the browser. Even when they’re not intentionally sabotaging Firefox, I’m certain that Google optimizes their websites exclusively for Chrome without caring about other browsers. Firefox and Chrome are both extremely fast browsers, but they’re fast and slow at different things - and Google will make sure to stay within what Chrome does well, without caring about what Firefox does well or poorly. Optimizing for non-Google browsers seems like something that’s extremely far down Google’s priority list.

      2. 19

        For all its faults, Safari is usually open on my desktop for one reason: its incognito mode is not dumb like Chrome’s. Every new incognito tab and window in Safari is its own separate sandbox, as opposed to Chrome where there is a single incognito environment that is shared by all open tabs and windows. (Astonishingly, the Chrome dev team considers this a feature, not a bug.)

        1. 2

          Reading that bug is a little disheartening.

        2. 8

          Resolution media queries, which allow content to be styled to match the device pixel density. Implemented in Firefox in 2012 and Chrome in 2013

          Odd, considering how Apple was the early adopter of HiDPI… on the other hand, I can’t say I ever needed these.

          IndexedDB APIs hangs indefinitely on initial page load, making it almost completely unusable

          LocalStorage is broken when a page is open in more than one tab, in a way likely to cause major data loss in most use cases

          These do suspiciously look like they were deprioritized to harm the web platform / help the App Store. Come on. The wealthiest company in ever can’t fix these awful bugs??

          1. 10

            The wealthiest company in ever can’t fix these awful bugs??

            According to the article, the LocalStorage bug was fixed within a day—it just hasn’t been deployed, because Safari updates are either tied to OS updates (on iOS) or at least not automatic (on macOS). It does seem like many of the article’s complaints might be modulated a bit if Apple didn’t force major Safari updates onto their other software products’ yearly release schedule.

            1. 4

              I mean, that does look like the sort of thing you’d do if you were trying to deprioritize browser support to harm the web platform. Especially if you’re a manager who doesn’t have direct control over the browser team.

              1. 2

                Totally true. It’s in the zone where it could be incompetence or it could be malice.

            2. 9

              The wealthiest company in ever can’t fix these awful bugs??

              Any software project which survives long enough and becomes large enough inevitably accumulates some number of bug reports that someone will be able to cherry-pick into an “OMG??!?!!?!??!?! They can’t even fix THAT!!!??!?!?!?!?!”

              No need to invent a deep dark vicious conspiracy to explain it. It’s just part of the lifecycle of projects.

            3. 7

              One of the most surprising things I’ve found today is that safari supports neither trusted types nor strict-dynamic in content security policies.

              Makes it really hard as a site owner to produce a site that effectively protects its users, even if you’re motivated&trying to do so.

              1. 4

                If even Apple and Microsoft aren’t able to keep up with the pace of change, maybe the issue lies somewhere else. Where are the efforts to simplify the web? Most of the things Google seems to be doing is adding more and more features, ever-increasing the complexity and attack surface of the web.

                1. 3

                  I like Safari just fine as a user; I value its advantages and don’t mind a few compatibility issues (I browse a lot of sites in Reader view anyway). But to the author’s point, it’s true that lots of regular Mac users leave Safari behind, probably for Chrome, which strengthens it as a de facto standard. Privacy, battery life, and iCloud features don’t seem to be enough.

                  1. 2

                    I feel like the OP just forgot how bad IE was. I did quite a bit of web development a few years ago (and I still do frontend things occasionally) and in my opinion the current Safari situation isn’t even remotely comparable to the Internet Explorer problem: it was stupidly hard to write a simple website with IE because things as important as SVG weren’t implemented, while nowadays Safari just supports everything you need, at least for a reasonably simple website. And things Safari doesn’t support (like Web MIDI, filesystem access or even web push) are not even desirable in a regular website.

                    1. 2

                      But if you’re trying to launch an app on a shoestring budget a web app could and should be a easy choice for write-once-deploy-everywhere. But Apple being so slow in adoption means this isn’t a reality for many since iOS has to matter. I can agree on simple websites, but the minimalist designs most dev blogs are using now can easily be implemented in IE as well (even if flex and grid make it make easier), but we live in a world where we can put more into the web platform and could get something meaningful out.

                    2. 1

                      In addition, Apple doesn’t make an effort to provide the browser for testing on other platforms. So if people ask for Firefox support, that’s testable with reasonable effort and great dev tools. Asking for Safari support means asking to buy Apple hardware.

                      I hope that their one browser rule falls in court.

                      I really like some of Apple’s innovations and Safari was once innovative. But there closed strategy (we create closed ecosystems fully under our control) means that they don’t get pressure to stay innovative in areas that fall out of favor by their management. Especially, if they rather push native apps.

                      1. 4

                        I hope that their one browser rule falls in court.

                        I found it fascinating that the OP had praise for the rule that WebKit is the only allowed rendering engine on iOS:

                        This paints a bleak picture. The one saving grace today is that Apple blocks use of any non-WebKit engine on iOS, which protects that one environment, and the iOS market (in the US at least) is large enough that this means Safari must be prioritized.

                        He sees it as a stopgap against the total domination of Blink. The viewpoints are kind of like, “Apple is a big bully” vs. “Apple is a big bully that is at least protecting us all from an even more harmful bully” in the form of Google.

                        1. 2

                          Apple doesn’t say this anywhere officially, but you basically can test on any WebKit browser like GNOME Web (Epiphany). You’ll even see the exact same devtools UI as Safari.

                          1. 1

                            Cool tip!

                        2. 1

                          Due to no notification support, we were unable to use a PWA as a solution for an application at my job. Instead there’s only iOS support currently and an unsupported Android user went out to buy an iPhone for support. This isn’t the open application platform future I wanted.