3 ms·

Ehh, I use Safari as my main browser (it feels more "native" than Chrome & FF, has seemingly lower CPU usage than Chrome, and is WAY better for the battery), an

Ehh, I use Safari as my main browser (it feels more "native" than Chrome & FF, has seemingly lower CPU usage than Chrome, and is WAY better for the battery), and I rarely suffer for it. Once in a while there is a site that does something fancy that requires Chrome, but it is rare.

squeaky-clean 9y ago
Same experience here. Safari is my daily driver for casual browsing because it feels smoothest and integrates well with the OS, iPhone, etc. The only times I can remember it being a problem are when I see a bleeding edge tech demo posted somewhere like HN.
- soperj 9y ago
  flexbox isn't a bleeding edge technology, and it's supposed to work properly on safari, but it really doesn't. Annoying as hell, and garbage on their organization to be honest.
  - stephenr 9y ago
    Have you submitted a bug report about it?
    - soperj 9y ago
      There have been bug reports submitted for years. Still not fixed.
      - stephenr 9y ago
        Caniuse reports some issues with < v10, but nothing currently?
  - squeaky-clean 9y ago
    I just Googled a few flexbox demos and had no issues viewing them or playing with them on Safari. Care to share an example that fails on Safari? Also seems it's been supported for a while? https://caniuse.com/#feat=flexbox https://caniuse.com/#feat=flexbox
kitsunesoba 9y ago
Precisely this. It’s not that the WebKit/Safari team doesn’t implement new features/standards (they usually do), it’s just on a different schedule. I don’t know anybody on the Safari team but I suspect that they prioritize very differently than the Chrome team does. One is all about impressing web developers with the latest and greatest where the other is more interested in having resource efficient implementations.