We're moved to shipping new web developer features twice a year. That's not near as often as Chrome but still a big improvement to once a year, solely with the major OS releases.
This release also has a ton of compatibility and standards compliance fixes.
> It's extremely satisfying to know that your browser will receive those important security updates quickly.
Apple has shipped plenty of Safari security updates outside of the OS update cycle. Feature releases of Safari are tied to the OS update cycle, not security updates.
You might want to consider the Safari Technology Preview. Updates every 2 weeks! https://webkit.org/downloads/
(Although, it has had some pretty major bugs. There was about a month where commenting on Github was broken, and currently JIRA doesn't even render.)
We try to prioritize bugs that block livability for STP. Do you know if there's a bug filed on the JIRA thing so I can get folks to follow up?
Yep, it's this one: https://openradar.appspot.com/30056643
Thanks!
EDIT: Also just found this Firefox bug report for the same thing: https://bugzilla.mozilla.org/show_bug.cgi?id=1328218 Discussion there seems like it's really more of a JIRA bug than an FF bug ¯\_(ツ)_/¯
My main gripe with Safari is that its release schedule is basically tied to OS releases. Ever since Chrome, I've come to love continuous releases. It's extremely satisfying to know that your browser will receive those important security updates quickly.
With Safari I have to deal with the App store nonsense (I still can't believe how bad that application is), waiting for stuff because Apple wants major releases to happen with their busted OS releases (your OS is free now! Please do rolling releases).
And I'm not a fan of Apple's positioning for web apps compared to Google or Mozilla. I like fancy new features!
The OS integration is, of course, better. Looks nice to use. And I think Chrome halves my battery life at this point. I should give it a shot again.