To be honest, I’m hoping to fall in love with Safari. I’m rooting for Safari’s success. It’s doubtful that it will. Browser fights are becoming old. I’d want to use Safari instead of Internet Explorer. It’s simple, sleek, and works with all of my other devices. Generally, it’s a decent fit for most of my requirements. There are occasions when it isn’t enough for me. I want it to be the ring that unites all of the other rings.
On my Macbook, I’ve been using the Windows version of Microsoft Edge for some time now since it’s the most versatile browser out there. However, I have no intention of doing so. It gives me the creeps. Safari is what I’d want to be using. Apple can never prosper until it makes significant changes to Safari. The following are my skewed views:
Contents
1. Safari Needs to Be on Windows
Apple released Safari for Windows a looooong time back. This was a big deal for me since it enabled me to synchronize my iCloud/Safari content throughout my Mac and Windows computers. Several years ago, Apple discontinued the Windows version of Safari. This was a blunder, and it broke my heart. As a result, Windows programmers no longer had an easy method to check whether their sites work properly on Safari without purchasing a Mac. Eliminating Safari from other os renders it much more costly from the standpoint of human costs to maintain interoperability throughout devices and web engines.
2. Updates Should Not Be Tied to the OS
Updates in Safari should be more frequent and more dependable. To do this, they must separate their arms and legs away from the basic operating system. Yes, I am aware that WebKit is an essential component of the operating system. With Internet Explorer, the tech giant made the same error… and they’ve subsequently reversed the course of action they took. To ape that would be absurd.
3. Could Use More Engines
Although I’m no developer, it appears to me that the engines that interpret the DOM, rather than the browser, are the main draw of these browsers. When I use Safari, why can’t I change the engine that the web browser leverages? I expect to be able to run Chrome or Firefox on Safari. Then I wouldn’t have to download and install a whole new web browser every time anything went wrong with WebKit. In addition, it would alleviate a few of the compatibility/testing difficulties I’ve mentioned before.
4. No Extensions
It’s a miracle that no one dislikes extensions. It’s a weird market there. As a result, Apple’s efforts to improve have been hindered by the restrictions it places on extension programmers. That should be improved upon. Apple, go beyond, please!
I’m rooting for Safari’s success. Since it is the strongest browser for my M1 Mac, I see no need to use anything else. A few smart choices might have made this web browser infinitely better.
