7 ms·
Sorry Safari Team
- 0des 5y agoI wish we saw more posts like these. Refreshingly sincere, and focusing on the data itself. Kudos to the author for putting this together.
- havkd 5y ago> I can see arguments on Twitter and I really want them to stop because it's making us all look bad. Get off Twitter.
- afavour 5y agoThat wouldn't make the arguments disappear. The author is a DevRel for Chrome, for better or worse they have to go where the audience is. It's literally their job.
- kinlan 5y agoYeah - I have to take the rough with the smooth. :D
- ronsor 5y agoQuite honestly, Twitter makes anyone and everyone look bad at some point.
- bla3 5y agoWeird that the Safari team gets worked up over this when https://apple.com/safari https://apple.com/safari regularly shows numbers based on years-old versions of Chrome. They just updated it so it's now only Safari prerelease versus Chrome 94, but it used to compare against a one-year old version. Right after the update, it's still comparing prerelease to an outdated stable Chrome version. Apple is very willing to intentionally make skewed comparisons to make themselves look good, but Apple apparently also gets very upset over an apparently honest mistake where a presentation that even tried to make them look good didn't make them look good enough.
- ezfe 5y agoI mean, it would've been the newest version at publication a year ago. Nobody expects Google to update these slides over the next year either.
- darkwater 5y agoBeing a dynamic website vs a static slide from a presentation happened at a specific point in time, I think you are comparing apples (err..) to oranges.
- FemmeAndroid 5y agoThey do have a clickable footnote on one of their claims which currently reads: > Testing conducted by Apple in September 2021 by measuring page load performance of snapshot versions of 10 popular websites under simulated network conditions. Tested on production 13-inch MacBook Pro systems with Apple M1, 8GB RAM, 256GB SSD, and prerelease macOS Monterey. Tested with prerelease Safari 15.0 and Chrome v94.0.4606.61. Performance will vary based on usage, system configuration, network connection, and other factors. And in August 2021, it read: > Testing conducted by Apple in October 2020 by measuring page load performance of snapshot versions of 10 popular websites under simulated network conditions. Tested on production 1.4GHz quad-core Intel Core i5-based 13-inch MacBook Pro systems with 8GB RAM, 256GB SSD, and prerelease macOS Big Sur. Tested with prerelease Safari 14.0.1 and Chrome v85.0.4183.121. Performance will vary based on usage, system configuration, network connection, and other factors. In September 2020, they posted a clickable footnote with: > Testing conducted by Apple in August 2019 using Jetstream 2, MotionMark 1.1, and Speedometer 2.0 performance benchmarks. Tested on production 1.4GHz quad-core Intel Core i5-based 13-inch MacBook Pro systems with 8GB RAM, 256GB SSD, and prerelease macOS Catalina, and Windows 10 Home, version 1903, running in Boot Camp. Scores represent browsers that completed the test. Tested with prerelease Safari 13, Chrome v76.0.3809.100, and Firefox v68.0.2 on macOS, as well as Chrome v76.0.3809.100, Microsoft Edge v44.18362.267.0, and Firefox v68.0.2 on Windows Home, with WPA2 Wi-Fi network connection. Performance will vary based on system configuration, network connection, and other factors. Could they constantly update this piece of information? Sure. But I think they're being pretty up front and clear about what they're saying. And it seems like they do similar testing every year, at a fairly regular interval. I see no evidence that they're doing anything wrong here. I think it's a pretty high bar to expect that all web pages must always show the latest possible data. Edit: I actually pulled slightly different footnotes accidentally, since the pages have updated over time. But in general, all testing clearly points to the months where the testing occurred. I think the worst thing I saw was in 2018, I think they had some tests which used data in August and October. Which I don't love. But I didn't notice that happening recently, and they did clearly disclose it.
- bangonkeyboard 5y agoSo Apple previously requested that Safari Tech Preview be used for bake-offs instead of release Safari, then macOS 11 recently broke CI which prevented STP from being updated, and this resulted in a slide mistakenly attributing Safari with a 21 point improvement instead of 28.
- londons_explore 5y agoYeah... when you say it like that, it sounds like the apology really ought to be going in both directions...
- dmitriid 5y agoThis reeks of "oops we're sorry" described by Johnathan Nightingale (former General Manager and Vice President of the Firefox group) in his thread on how Google was sabotaging Mozilla: https://archive.vn/tgIH9 https://archive.vn/tgIH9 (or direct link, https://twitter.com/johnath/status/1116871237240852480 https://twitter.com/johnath/status/1116871237240852480) - "I'm sorry for the misrepresentation of Safari Tech Preview's compatibility score". This was intentional. Show these numbers at a large dev summit. Post an apology on a personal blog a week later. Related: https://news.ycombinator.com/item?id=29228083 https://news.ycombinator.com/item?id=29228083 (the mistake was noted before the summit, but wasn't even mentioned) - "it stated that Safari had jumped from a score of 64 => 85, when in fact what we should have had on the slide is is 64 => 92." Yup. It still shows 86 - "I hadn't seen any negative press or negative developer sentiment to this slide, but it clearly irked the Safari team." Any negative news presented by Chrome team is uncritically taken at face value and accepted as truth. This is very well known to the Chrome team and they are very happy to exploit this. - "Compatibility is a shared ecosystem problem. It makes no sense to me that we try and score 1-up points on Compatibility. Just because one browser might be on spec, it also means that same browser might also not be interoperable with other browsers and this means that developers have to deal with the difference irrespective if a browser is "technically correct"" Chrome should stop pretending they are good guys. They are not. They keep implementing increasingly Chrome-only APIs and ignoring any and all concerns about those APIs from Firefox and Safari. They couldn't care less if Chrome wasn't interoperable with other browsers because in their minds Chrome has already won. - "Longer term, I'm going to be directing my teams to focus more on broad browser support in our work and less on newer Chrome-first (/only?) features and I think our wider story should all be based on what users have today, and less on what they might support at some point in the future." This will never happen. "You have to run twice as fast just to keep up with Chrome" is an insanely successful strategy for Chrome. If anything, Chrome-only work will only accelerate.
- heavymark 5y agoIn regards to, "We realised the mistake on the morning of the keynote (November 3rd) and at that point it was too late to change it." Confused. While can understand not being able to change a number in a presentation last minute, the person reading/presenting could certainly just mention on that slide, or that number is actually x. Mistakes happen, but since they realized it before presenting why wouldn't they mention that rather than providing the knowingly wrong info?
- chaboud 5y agoIt sounds like it was pre-recorded.
- mnd999 5y agoWas the whole thing not pre-recorded?
- BuildTheRobots 5y ago> We recorded the keynote in early/mid-October I'm not sure when the presentation was actually made, but if it's a pre-recorded video then it makes sense they couldn't change it on the morning for either the slides or presentation. In that situation, I'm honestly not sure how I would have handled it.
- londons_explore 5y agoMaybe they knew the number was wrong, but didn't have the correct numbers...?
- kinlan 5y agoIt was all pre-recorded. We clarified it in the live AMA after the pre-record.
- jacknews 5y agoI don't think I want to work anywhere that has this level of angst.
- antonzabirko 5y agoLmao what did apple do to this guy to make him write an apology about a 7-point correction from the hospital without a thumb??
- pdenton 5y agoThey made it look like an accident
- mynameisvlad 5y agoDo you have any proof that what happened was not an accident? Everything written in the article makes sense. Is there anything out there that disproves anything that what was said?
- mst 5y agoI'm pretty sure you're replying to a joke.
- droopyEyelids 5y agoThe author's boss had to present the inaccurate data, and then take responsibility for it. Even if Apple wasn't involved, that would make me want to confess.
- kinlan 5y agoI wouldn't even say it was that. No one asked me to write it, but I also want to make sure it was clear when and how the mistake was made. I'm not above pride in this case and in the long run I saw the two teams arguing over something that I had done and I value developers more than that.
- droopyEyelids 5y agoThat has to feel bad and I think you set a beautiful example for people who find themselves in this position in the future.
- hnarayanan 5y agoSliced off his thumb and still made time to write this!
- kinlan 5y ago:thumbs-up: - I've got some gnarly pictures, but I can say I am on the mend.
- nobleach 5y agoI'm confused why Apple should get to compare the stuff in their Technology Preview, instead of the actual browser that people are using day to day. It took Apple eons to ship `navigator.getUserMedia`. This was a serious hindrance to those that wanted to provide a cross-browser video upload experience. Yet if we went by their Tech Preview, one would be able to argue that they supported it. Apple if very frustrating in this way. They have a massive amount of resources, yet they choose not to put those resources into developing their browser. That's fine, that's their choice. But telling everyone that they support something that they only "intend to support at some future date" is less than honest.
- syspec 5y agoIn this case there Non-tech preview version of safari scored higher, due to a bug in the testing framework which was not correctly updating the tech preview version used. Yet they still used the tech preview number which was much lower, in their slides That's why there's uproar, chrome dev tools team showed the lower score which was caused by a non-updating test framework and people ran with it
- magicalist 5y ago> due to a bug in the testing framework the "bug" is https://github.com/web-platform-tests/wpt/issues/31147 https://github.com/web-platform-tests/wpt/issues/31147 MacOS 11 isn't allowed(?) to be virtualized, so the Safari TP, which is tied to MacOS updates, couldn't be updated. > That's why there's uproar Was there an uproar? There were some objections from some Safari devs that they understood the difficulty in getting the latest number since the web platform test runner can't run the latest Safari Tech Preview (which they've also known for some time), but since the whole point of this was to show how browsers have improved their compatibility on this set of tests, it was hurtful and counterproductive to leave out their latest work. Chrome devs apologized and now we have this article, and it looks like the test runner will start running WebKitGTK for this set of tests so at least the Compat 2021 dashboard[1] will show the latest results. [1] https://wpt.fyi/compat2021?feature=summary https://wpt.fyi/compat2021?feature=summary
- deleted 5y ago[deleted]
- diebeforei485 5y agoI tend to agree that you should only use "release" versions of browsers when comparing features. I think it no longer makes sense to compare betas or prerelease versions.
- gtirloni 5y agoI'm having a hard time understanding why people are so worked up about such a small difference in the numbers. I read the whole post and thought both sides to be overreacting.
- mmastrac 5y agoI've given up on Safari - it's buggy as hell, seems to ignore the most interesting standards available on every other browser and is just generally not a great experience for me as a developer or as a user. I am happy that they gave the world WebKit[°], but they absolutely destroyed that good will by providing the worst-of-breed dev tools (assuming they're even working in a particular release) and failing to support web standards properly that could have driven the web forward (ie: WebRTC). [°] EDIT: I am aware that it was forked from KHTML but it was still a big engineering effort
- neilalexander 5y ago> the most interesting standards available Genuine question — which standards is it you have in mind?
- phillipseamore 5y agoMSE media source extensions - supported on macOS and iPadOS but not iOS for an unknown reason (was available off by default in one iOS beta though).
- mmastrac 5y agoRestricting the list just to the ones I can find on caniuse or bugzilla, but this is a tiny, tiny subset. It also doesn't include the fact that implementations are completely busted (IndexedDB for the longest time [1], ServiceWorkers [2]) https://caniuse.com/av1 https://caniuse.com/av1 https://caniuse.com/mdn-css_properties_contain https://caniuse.com/mdn-css_properties_contain https://caniuse.com/css-overflow-anchor https://caniuse.com/css-overflow-anchor https://caniuse.com/css-focus-visible https://caniuse.com/css-focus-visible https://caniuse.com/js-regexp-lookbehind https://caniuse.com/js-regexp-lookbehind [1] https://bugs.webkit.org/show_bug.cgi?id=226547 https://bugs.webkit.org/show_bug.cgi?id=226547 [2] https://bugs.webkit.org/show_bug.cgi?id=187461 https://bugs.webkit.org/show_bug.cgi?id=187461
- rp1 5y agoAdding on to this, WebRTC really doesn't work well, especially on mobile. Also, you can't set the volume on video and audio elements on mobile, which really limits what you can do. The audio context implementation is also pretty buggy.
- fron 5y agoIf the Safari team could get their shit together and ship all the features they're missing that other browsers have supported for years, then perhaps I'd have more sympathy. All I see here is that Safari still sucks in terms of feature support and developer experience.
- syspec 5y agoClearly didn't read the article
- robertoandred 5y agoWhat you're actually seeing is people who want Chrome to control the web and expect all other browsers to blindly follow whatever features they add to suit their business model.
- ocdtrekkie 5y agoSo much this. Most of the new "features" Google keeps introducing and expressing irritation aren't supported in Safari offer significant privacy risk and dubious real world benefit. And herein again, Google does an "Oops" like they so often did to Firefox. https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has... Chrome team no longer gets the benefit of the doubt. They are a monopoly with a history of aggressive harms to competing browsers.
- sefrost 5y agoWhich features are you thinking about that would present a privacy risk? I am aware of the File System Access API. What else is there?
- ocdtrekkie 5y agoMuch of the Chrome-introduced API surfaces which aren't supported in Safari tend to be about direct access to hardware. WebUSB, WebSerial, Bluetooth API, WebXR API, etc. etc. etc. I would generally consider the introduction of these APIs to be hostile to average users: Each one adds a new fingerprinting vector, an extremely easy malware vector, and the protections Chrome team and standards folks have designated are woefully inadequate: Average users accept basically anything, and nobody on the Chrome development team has learned that yet.
- chrsig 5y agoAm I the only one that thinks that this whole thing seems kind of...petty? A mistake was made, it was corrected ...move on? am I missing something?
- skinkestek 5y agoFor some of us this is just the most recent event in a long series. Is it necessarily an evil ploy this time? I say no. Should I cut them some slack? Again, I say no. When they are big enough to hurt others badly by being careless, then they should be taken to task just for being careless. As someone said Google had mountains of goodwill until recently. When they have worked so long and so hard to make us dislike them I think they deserve to reap the rewards ;-) Also, as someone else mentioned, there is the pattern of announcing something misleading on stage and then retracting it on a private blog later, just like big media tend to do.
- chrsig 5y ago>When they are big enough to hurt others badly by being careless, then they should be taken to task just for being careless I guess this is where I'm having difficulty -- Who's being hurt badly here? What was the actual damage? I guess I'm just having a hard time caring that google and apple are duking it out? Like...out of all the things google does to get up in arms over, I'm having a hard time ranking getting a number wrong on a slide....and with all the things apple does, and all the resources they have at their disposal, I'm having a hard time finding much empathy for it.
- kinlan 5y agoI think there's a number of people who've said that they've lost trust in Google and that's pretty much the sum of it and why I felt like I needed to write up the post. For me, there are three sets of people that I work with: Developers, Engineers in Chrome and Engineers on other browsers. Projects like Compat 2021 are super important to me to the point that if another browser vendor doesn't trust that we are working and pushing together then the project just won't succeed. If the partner browser (Safari in this question) doesn't trust the data we present, then the ecosystem won't trust the data or project. If the ecosystem doesn't trust data then the browser teams won't trust the project etc. So even if it was just a small change in the number, it's trust all the way down.
- kaycebasques 5y agoPaul is good people. He leads Chrome's DevRel team. I was on that team from June 2015 to June 2021. Browser DevRel can be messy stuff. You're perpetually trying to advocate for your browser's vision of the web while also maintaining respectful, collaborative relations with the other browsers. The tricky part is that they often have a different vision for the web. This holds true no matter which browser you're rooting for. IMO that is the fundamental cause of all these conflicts that occasionally bubble up between Chrome/Safari/Firefox. The bright side is that the web appears to still be a functioning, open ecosystem (in that different parties are competing to take the web in different directions). Case in point you don't often see posts like this about the Android/iOS ecosystem making it to the front page of HN. Conflict is healthy albeit exhausting.
- kinlan 5y agoThanks mate :) miss you.
- GoodJokes 5y agoWhat fragile people got upset about a number to the point that this person had to write this apology.
- lloydatkinson 5y agoWhat issues are people actually facing in regards to browser compatibility on evergreen browsers in 2021? I keep hearing people complaining about Safari but no one has explained what issues they actually face. The article mentions CSS but I've not encountered any incompatibilities so far. I've made SPAs, normal sites, used CSS Grid, some simple animations, all been fine across browsers.
- jjcm 5y agoMy most recent issue was with the ElementInternals API: https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals https://developer.mozilla.org/en-US/docs/Web/API/ElementInte... They still don’t have it implemented despite giving their “strong support” a few years ago when the API was in the final spec stage. That’s really the crux of the issue - they always seem a few years behind in implementing any new spec.
- robertoandred 5y agoFirefox hasn't exactly implemented it either.
- jjcm 5y agoNo, but at the very least Firefox has the bare minimum needed not to crash js execution when it encounters usage of the API. Safari doesn't recognize the syntax (or at least didn't when I tested this ~5 months ago, though it looks like nothing has changed on the safari side).
- lloydatkinson 5y agoWow thats terrible actually. I remember looking into how to get web components to work with forms and decided to put it off for a while. Didn't know Safari doesn't implement it yet. Is there a polyfill?
- jjcm 5y agoThere is: https://github.com/calebdwilliams/element-internals-polyfill https://github.com/calebdwilliams/element-internals-polyfill
- deleted 5y ago[deleted]
- evrydayhustling 5y agoThis should go in a textbook about great professional apologies.
- brunojppb 5y agoVery honorable of Paul going out there, assuming the mistake and making this write up.
- mmcnl 5y agoSomeone made a mistake. Correct it. Move on. Why so apologetic? I personally never apologize for an honest mistake. Humans make mistakes, I make mistakes, mistakes happen, and if it's not a big deal, then there's no need to apologize imo. Apologizing too often leads to a culture where failures are not embraced.
- ropable 5y agoCouldn't disagree more. To me, an apology signals that a mistake was made, noticed, embraced, (hopefully) corrected, and learned from. There's no shame or opprobrium attached to an honest apology, and plenty of potential for improvement. There's quite the opposite attached to a person who blithely handwaves away their own mistakes without any acknowledgement.
- phillipseamore 5y agoI'd like to make a note that these tests do not cover feature differences within the Safari ecosystem since this is only comparing Safari macOS (the only OS that allows other browser engines). Safari on iPadOS has fewer features available than Safari on macOS, iOS even less. Missing features between Safari for each OS are either because they default to off (but the user can enable them) or they are explicitly not available. For instance iPadOS supports MSE (Media Source Extensions) but iOS does not, despite them running on the same SoC. I do not recall having encountered such differences with other engines between different desktop/mobile operating systems. Since Safari on iOS has the greatest number of users of all the Safari versions it should be used for comparison, and not Safari macOS.
- hit8run 5y agoSorry to hear that with your thumb. I guess safari devs made it clear that if you shit on their browser you will next time lose more than a thumb. These animals…
- musicale 5y ago> Longer term, I'm going to be directing my teams to focus more on broad browser support in our work and less on newer Chrome-first (/only?) features Not focusing on Chrome-only features? Interesting.
- mijoharas 5y agoI just want to commend Paul on a classy apology. A lot of people are saying "it's not a big deal", and frankly, it might not be, but some safari developers felt that the work they put in wasn't respected, and Paul came out and gave a mea culpa. Whether it's a big deal or not, if people's feelings are hurt, I think it's best to address it and apologise rather than to say "it wasn't that bad" especially when you've made a mistake. Mistakes happen Paul. Well done for coming out and owning it.