4 ms·
Safari's slow release cadence (typically tied to OS version upgrades) does leave it more broken and for longer than Firefox, Chrome, Opera and other browsers th
by leeoniya 5y ago
Safari's slow release cadence (typically tied to OS version upgrades) does leave it more broken and for longer than Firefox, Chrome, Opera and other browsers that are updated more frequently and not tied to the OS.
just recently i ran into incompatibilities with Safari < 14 needing a shim due to still having the old-spec MediaQueryList api:
https://github.com/leeoniya/uPlot/issues/538#issuecomment-870711531 https://github.com/leeoniya/uPlot/issues/538#issuecomment-87...
- dmitriid 5y ago> browsers that are updated more frequently and not tied to the OS. This is true. Apple's inane insistence that everything has to be updated only once a year is truly baffling.
- ttepasse 5y agoThese past years Safari gets two releases per year, the big one with the release of MacOS in fall and a .1 spring release, adapting web technologies and sometimes extra releases tied to other Apple events and Apple proprietary APIs I'm somewhat sceptical about evergreen browser, but that's mostly because I hate having the user interface changed under me without any action on my part. I would have hated to get the Safari 15 Beta just by opening my browser in the morning. A better update strategy seems to me to keep the big UI changes for a yearly update; but update the web engine somewhat more often, bi-monthly or so.
- dmitriid 5y ago> A better update strategy seems to me to keep the big UI changes for a yearly update; but update the web engine somewhat more often, bi-monthly or so. I can't emphasize strongly enough how much I agree with this.