Apple Releases Safari Technology Preview 141 With Bug Fixes and Performance Improvements
Apple today released a new update for Safari Technology Preview, the experimental browser Apple first introduced in March 2016. Apple designed the Safari Technology Preview to test features that may be introduced into future release versions of Safari.
The current Safari Technology Preview release is built on the Safari 15.4 update and it includes Safari 15 features introduced in macOS Monterey.
The Safari Technology Preview update is available through the Software Update mechanism in System Preferences to anyone who has downloaded the browser. Full release notes for the update are available on the Safari Technology Preview website.
Apple's aim with Safari Technology Preview is to gather feedback from developers and users on its browser development process. Safari Technology Preview can run side-by-side with the existing Safari browser and while designed for developers, it does not require a developer account to download.
Top Rated Comments
But whenever not using Safari I try to stick with Firefox. A world where everyone is using a chromium based browser is not ideal. It puts too much power into Google and Chromiums hands. And we already see it a lot where many web developers develop for Chromium first, and often end up not keeping web standards in mind at all. If it works in Chromium, it's good enough has become the mantra which is quite sad for the web as a whole.
Microsoft Edge became much better when Microsoft decided to move from EdgeHTML to Chromium, but it was a sad day for the web as a whole. Now Apple and Mozilla are the only ones left. Apple has huge marketshare due to iOS and iPadOS, but on desktop Safari isn't really competeing at all. Neither is Mozilla. WebKit will stay with us for a long time, but all it's focus is on mobile. Gecko is fighting a uphill battle, Mozilla is growing more frustrated by the day as a result of so many websites using non-standard Chromium specific features that has yet to be adopted as a part of the open web standard making Firefox run worse not as a result of the browser being bad, but as a result of how web developers are pretty much enforcing Chromium to be the best. The same issues Microsoft had when trying to push EdgeHTML and even a company as big and resourceful as Microsoft simply had to give up and move to Chromium to stay relevant and competetive.