Apple's Safari's Developer Tools (F12) is so outdated and behind Google Chrome. If they don't do something about it soon, they are going to be left behind.
IF Apple and Google weren't such drama queens with each other they could partner up on a hell of a Webkit browser. But if Apple Maps is any sign that Apple wants to be rid of Google, I don't know what is...
No, Google and Apple have different needs and aims for the Web. Google wanted Web Apps, Apple wanted Web Pages with extra functions. The split to Webkit was possible the best for both parties.
Safari is so far behind Chrome on standard support, it has become the "new Internet Explorer". Every time I want to use a newer HTML5 feature I need some workaround to deal with Safari antics (typical example: no native support for displaying error message on forms)
Firefox continues to be, in my opinion, the best browser for MacOS. It's also the only browser that continues legacy support for OSX pre 10.6\32-bit Core Duo builds) so for the most part a lot of people with Pre 2009 Mac's have no choice but to run Firefox build 22.
I love the Safari:IE analogy, that made me laugh, because its entirely relevant.
Most people using IE analogy has either 1. Not done any Web Programming in the IE era 2. Fail to notice how many other standard HTML5 features support. 3. They wanted the Web Platform to be Apps, and not Web Pages first, but Apps.
Apple really needs to give Safari some love. Edge isn't much better in standards support, but they've made great strides and are clearly working at it. FF and Chrome have been champs for a long time now. Safari seems almost willfully behind the curve.
I was talking to a friend who is a committer to one of the big JS frameworks. He tells a rather different store. It's Chrome that is the new IE, particularly on mobile. Its JIT sucks, and its "native" implementations aren't all native, which is a problem, because its JIT sucks. Meanwhile, they are about to torpedo a bunch of long awaited standards at the last minute because they can't make them not suck on Chrome.
On the other hand, Safari's JIT doesn't suck. In fact, it doesn't suck so much that the new stuff that require polyfills (for now) on Safari outperforms Chrome's native implementations.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
10 Comments
Back to Article
stun - Wednesday, March 30, 2016 - link
Apple's Safari's Developer Tools (F12) is so outdated and behind Google Chrome. If they don't do something about it soon, they are going to be left behind.Samus - Thursday, March 31, 2016 - link
IF Apple and Google weren't such drama queens with each other they could partner up on a hell of a Webkit browser. But if Apple Maps is any sign that Apple wants to be rid of Google, I don't know what is...iwod - Thursday, March 31, 2016 - link
No, Google and Apple have different needs and aims for the Web. Google wanted Web Apps, Apple wanted Web Pages with extra functions. The split to Webkit was possible the best for both parties.MartiCode - Wednesday, March 30, 2016 - link
Safari is so far behind Chrome on standard support, it has become the "new Internet Explorer". Every time I want to use a newer HTML5 feature I need some workaround to deal with Safari antics (typical example: no native support for displaying error message on forms)Samus - Thursday, March 31, 2016 - link
Firefox continues to be, in my opinion, the best browser for MacOS. It's also the only browser that continues legacy support for OSX pre 10.6\32-bit Core Duo builds) so for the most part a lot of people with Pre 2009 Mac's have no choice but to run Firefox build 22.I love the Safari:IE analogy, that made me laugh, because its entirely relevant.
easp - Monday, April 4, 2016 - link
Relevant, as in "wrong?"iwod - Thursday, March 31, 2016 - link
Most people using IE analogy has either1. Not done any Web Programming in the IE era
2. Fail to notice how many other standard HTML5 features support.
3. They wanted the Web Platform to be Apps, and not Web Pages first, but Apps.
Timbrelaine - Sunday, April 3, 2016 - link
Apple really needs to give Safari some love. Edge isn't much better in standards support, but they've made great strides and are clearly working at it. FF and Chrome have been champs for a long time now. Safari seems almost willfully behind the curve.easp - Monday, April 4, 2016 - link
Hmmmm, last I heard (as of a few weeks ago), Edge had the best standards support in terms of breadth and quality.easp - Monday, April 4, 2016 - link
I was talking to a friend who is a committer to one of the big JS frameworks. He tells a rather different store. It's Chrome that is the new IE, particularly on mobile. Its JIT sucks, and its "native" implementations aren't all native, which is a problem, because its JIT sucks. Meanwhile, they are about to torpedo a bunch of long awaited standards at the last minute because they can't make them not suck on Chrome.On the other hand, Safari's JIT doesn't suck. In fact, it doesn't suck so much that the new stuff that require polyfills (for now) on Safari outperforms Chrome's native implementations.