At one point I was doing a lot of coding in a coffee shop. When testing my work in Safari, I could sit down and run on my Mac’s batteries until I got tired of the coffee shop and headed home.
With Chrome, I had to plug in immediately. I believe people who tell me Chrome has better bling and is faster, but Safari is fast enough for my purposes, and battery life is a far bigger factor for my browser choice than raw performance.
https://bugs.webkit.org/buglist.cgi?bug_status=__open__&cont...
I ask because that returns 351 issues but if you do the same search for Chrome you'll find 414. I would assume that you would agree that the correct interpretation of that is not that Chrome doesn't support WebRTC?
https://bugs.chromium.org/p/chromium/issues/list?q=component...
Since all of the major services work without issue in all mainstream browsers, I would argue that to a first approximation this is not an effective proxy metric.
All of the major services support it and the only one which I’ve ever had problems with is Google’s, which shockingly had issues with every browser other than Chrome. Do you have links to bug reports?
I switched to Safari primarily a while back because it used the least battery and memory (Safari & Firefox were close, Chrome is a distant gluttonous third place). I’ve noticed very, very few cases where a compatibility issue forced me to switch browsers. As a web developer I use all three, of course, and using Chrome doesn’t feel notably better so halving my energy usage is an easy trade.