1. 52

  2. 16

    I thought safari was the new IE.

    1. 10

      Safari is probably the best browser out there IMO. I wish Windows 10 had it so I could run it.

      1. 17

        What makes you say that Safari is the best browser?

        1. 4

          It’s fast, light on battery, and has a native UI that respects platform conventions.

          1. 1

            Sounds like Firefox? <3

            1. 1

              Firefox is faster than it used to be, not sure about battery, but it’s not very native. Safari is the gold standard in not having its own conventions and completely submitting to the platform HIG.

        2. 11

          I appreciate many things about Safari as a user; it basically doesn’t touch the battery, for one thing.

          As a web dev, it unfortunately punches well above its weight in terms of WTFs-per-minute. Specifically, it implements quite a few things incorrectly (such that a careless ‘feature present’ test returns true but the feature doesn’t work).

          For example, localStorage/sessionStorage are present in private tabs, but raise an exception if used (other browsers downgrade localStorage to sessionStorage and clear sessionStorage when you close the tab).

          For another, flexbox was broken until 10.1, putting the wrong number of items on a line, calculating heights incorrectly… just a total mess.

          1. 1

            other browsers downgrade localStorage to sessionStorage and clear sessionStorage when you close the tab

            Doesn’t that seem like more of a wtf? Transparently turning “long term storage” into “this will be gone in a moment” with zero notice.

            1. 3

              The defining feature of a private tab is that it acts like a regular tab, then deletes everything afterwards.

              Lots of websites try to put stuff into localstorage (‘works in every browser’) and don’t bother with error handling. Where is the user going to place blame when a private tab is the only place it fails?

          2. 2

            I’d disagree here. Mostly because of Security (see other reply), but also because of slower web platform feature support.

            1. 1

              Your other reply isn’t exactly a cornucopia of information about why you think it’s poor on security.

              1. 1

                Exploiting WebKit is apparently easy enough, that every game platform jailbreak (from early PSP to recent Nintendo Switch) finds one. Also: no sandbox

                1. 1

                  Ok so firstly - game devices are only going to ship with a single web renderer. If they ship webkit thats where attackers will focus - if they shipped blink, it would attract attacks the same, and given the following, it would hardly be surprising if they found vulnerabilities in any rendering engine when the device maker ships an unpatched version of the software:


                  Why do you think safari has no sandbox? Sandboxing was a feature of v5.1 in 2011.

                  1. 1

                    Re, the Sandbox: oops :) i must have been wrong

          3. 7

            That’s security-wise ;)

            Chrome is the IE in terms of abused market dominance.

          4. 20

            Chrome is worse than Internet Explorer 6, really. I don’t recall ever being concerned that IE6 itself was spying on me and phoning home to Microsoft, but I can’t say that about Chrome and Google. I think using Chromium mostly avoids that problem, at least.

            However, I recently found Otter Browser which attempts to mimic the original Opera browser. I’ve been using it instead of Chromium when I can, and haven’t noticed any rendering problems or Javascript incompatibility, which should be expected since it’s WebKit based.

            My biggest complaints so far are that the built in ad-block isn’t great compared to uBlock Origin, some videos don’t play due to Widevine problems, and it’s not very stable. The last problem may be my own fault, though, because I’m running the bleeding edge tip of their Git repo. It’s on my todo list to start debugging some of the problems and contributing code, but I say that about a lot of projects…

            In any case, it’s being actively developed and I think it’s worth a look for anybody tired of being at the mercy of Google, Microsoft, Apple, and Mozilla.

            1. 5

              I’ve used SeaMonkey[1] for years now which mimics the original Firefox 2.0. Never found any compatibility issues as it’s still a recent Gecko, some WebGL or WebRTC stuff doesn’t always work but that’s fine.

              [1] https://www.seamonkey-project.org/

              1. 1

                Otter just seems to be a UI wrapped around WebKit. Meh.

                1. 1

                  I’m not using it for the rendering engine.

                  I’m not even sure why the underlying engine matters, really.

              2. 11

                I’ve been hoping for a while that all the work Mozilla is doing will propel Firefox into more of a market leading position.

                1. 11

                  Isn’t the situation fundamentally different?

                  IE6 had huge marketshare (90% if I’m not mistaken) but abused it by not following standards, forcing people to write their websites for IE6, which meant other browsers had to conform with IE6, which meant users didn’t have to switch away.

                  Chrome now has majority marketshare (around 60%), but they’re following standards. Sure, they keep pushing new standards and introducing their own, but they are standards.

                  Nonetheless, I agree that Google should not abuse its power.

                  From what I can tell, they keep pushing new web standards, which means devs have new tools that they want to use, which are only available on Chrome, so users switch to Chrome because they see more and more of these websites. I tend to ignore websites that say “Chrome only”.

                  Personally I use Chrome, as a developer, for two simple reasons:

                  • I can inspect Node.js processes by running Node.js with --debug/--debug-brk and going in Chrome to chrome://inspect
                  • I have an easy-to-use Profiles feature, which means I can have a work browser, personal browser, etc. I have different histories, bookmarks, etc. Firefox is not up-to-par here.

                  Those two features are all I need to switch to Firefox fully. I dislike Google. I appreciate Mozilla.

                  1. 4

                    I agree with this post, when I’m developing front-end applications sometimes, I have problems with Javascript, I mean Chrome is lax with the good practices on JS, and I have to do improvements on Firefox in order to have an equilibrium. So, as the post mention Chrome wants to jump all those good practices sometimes in order to keep the dev on the browser.