Recent days Apple’s Safari web browser considered as an outdated program that people from different backgrounds don’t use. Even the developers are avoiding to use the Safari in their programming scenarios as the feel and operation has been gone much like an Internet Explorer, Ars Technica Argues.
Ars Technica makes a convincing note on Apple’s Safari update saying that Apple isn’t updating it’s web browser sufficient enough to support the tools like APIs that the most of the developers play with while designing the websites. Up to certain period it might not seem like an issue even if Apple doesn’t support every new API that come in the market which is used by the developers, but it could mean that developers have decided not to test their developed websites on Safari which could mean it eventually becomes an outdated, unused and unsupported browser like Microsoft’s Internet Explorer.
It’s not just Ars Technica’s Nolan Lawson who shows concerned about Safari, Apple writer Ben Thompson also said in his routine daily email on Monday that ‘Safari is slower to adopt to standards it it adopts them at all, Apple doesn’t really attend conferences (although folks working on Safari are active on web standards mailing lists), and iOS does not allow other rendering engines on iOS‘. On the other hand Apple hasn’t shown many signs in support of developers working on its Safari browser, doesn’t attend developers conferences and the developer communities. Due to all these kind of mute activities Apple has been left in the dark about the major updates until Apple reveals the latest news. This is not an ideal situation for the web developers who rely on mutual communication with the tech companies to make sure their websites runs ideally. Every one is waiting to hear from Apple about this updates to Safari during it’s keynotes.
So in this situation what might be Apple solution to this enlarging problem with the lack of updates? Apple would probably argue saying the developers should create the native web applications instead of creating the web applications which could take massive time in testing in multiple web browsers. But each and every person who has proper knowledge on Technical aspects can say this is not an ideal solution that Apple would have suggested. One solution that Ars Technica considers is that Apple starts contributing to open source web standards, helping the whole web, as well as Safari. This solution doesn’t sound like Apple’s way of thinking, but in some way it could at least help the developers to get back onto Safari.