I’m off to work tomorow but I’m working from home so I’ll be looking forward to getting a good night sleep so I’m all ready for a walk tomorrow. I’ve got the new sunscreen I bought from the supermarket but I couldn’t be bothered getting the name brand stuff so I just got the Woolworths branded which is SPF50+ which is good enough for when I go walking. I was hoping that getting out of the house by 9:30 am would result in me being out before the sun is it at its most intense but the one thing to keep in mind about New Zealand is even on overcast days the UV is pretty intense.
Apple is now pushing a marketing bitz to get people interested in switching from Chrome to Safari (link) – with all due respects, Safari is already included with your platforms by default so if people are going out of their way to down a competing browser then maybe you should so something about why people feel the need to do that. For example, Apple needs to have a proper native implementation of the declarative net request in the browser rather than it sitting on top of the content blocking API (the lack of a native implementation means having to wait for filters to be converted from the DNR format to the content blocking format vs being able to use the filters without the conversion process).
That doesn’t touch on the numerous implementation bugs that they haven’t addressed. For example bug case 295043 – over a year and nothing has been approved for merging, 10 months ago I requested the status of the bug but I was completely ignored by Apple engineers. Then there is the issue of website compatibility such as YouShop (NZ Post) doesn’t render properly – I’ve reported it and over a year later nothing has been done. WordPress for the daily writing prompt doesn’t work when you click on post and for that daily prompt to appear in a new post but it works on Chrome. Teams routinely throws login errors when on Safari (added to my uBlock Origin Lite allowed websites) but the problems don’t exist on Chrome (I also use uBlock Origin Lite on Chrome as well). On Google Chat when you send a message it automatically scrolls up to the last message the receiving party views and on Chrome when you receive a message there is a red dot in the tab showing a message has been sent to you but on Safari the only option is to have an annoying notification to come through.
All of these issues I’ve reported and all of these issues have been ignored by Apple engineers – at some point you stop wasting time and just shift browsers. This is the same issue that Microsoft faced many years ago when they had EdgeHTML and websites deliberately breaking on it but would suddenly work if you spoofed the useragent to Chrome which made it clear EdgeHTML could render the website but the website was the one at fault. After years of playing cat and mouse Microsoft eventually threw in the towel and decided to create a Chromium based Microsoft Edge which has resulted in a reliable experience for end users ever since. Microsoft are now adding support for Google accounts so that it will be possible to sync to your Google account – if you like using Edge but have a Google account then it is all good. Something tells me that Apple aren’t going to be that pragmatic no matter how far behind Safari gets with the only remaining users being hardcore Apple fanboys and those who don’t know how to download a different browser.


You must be logged in to post a comment.