When comparing W3Schools vs Safari, the Slant community recommends W3Schools for most people. In the question“What are the best resources for learning Javascript and the DOM API?” W3Schools is ranked 7th while Safari is ranked 8th. The most important reason people chose W3Schools is:
All the tutorials are written in a straightforward and easy to understand way.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to learn
All the tutorials are written in a straightforward and easy to understand way.
Pro Built in editor
Almost every example has a "try it yourself" button which opens up an editor in a new tab. It allows you to play with the example code and see how it works.
Pro Well organized tutorials
All of the lessons are separated into their own pages, which makes it easy to learn about specific concepts.
Pro Great source from Google search's perspective
Pro Works elegantly in OSX
The rendering of the pages and the browser compatibility with OSX works smoothly, when compared to other browsers. Also you get very high battery life with Safari, when compared to Chrome.
Pro Extremely fast
Pro Sleek design
– No distraction stuff like favicons in tabs, all that borders, bevels and embosses in panels like in other browsers, no ugly shaped tabs.
– Neat adress bar.
– Good looking start “show all tabs” screen.
Pro iCloud syncing
Tabs, passwords, bookmarks and, history all sync across devices.
Pro Safari uses Webkit, a great open source web engine
Webkit is very light compared to Blink, renders web pages at an incredible speed, great CSS support and is also constantly evolving.
Cons
Con Outdated practices / problem solutions
The practices that are shown to solve the problems at hand are rarely, if at all, updated. Usually, their tutorials and learning material is updated only after they see their profits drop.
Con Doesn't care about teaching right
There are multiple errors in the data they show. Although the solutions they show work, they will lead to unmaintainable code. That happens even when the maintainable code alternatives are as easy or accessible to new programmers as the alternatives.
Con Certifications not recognized
Many professionals in IT agree that w3s certifications are not recognized by them and are deemed useless. Good luck finding any respectable professional that accepts a w3s certification.
Con It is for profit
What defines what goes is and what gets fixed on w3schools is what gives them profit and what doesn't (through their ads system).
Con Written tutorials only
While many learning resources offer a mixture of media in their courses (such as videos, challenges etc.), w3schools offers only written tutorials and code editors. This makes w3schools more beneficial as a quick reference rather than a primary learning resource.
Con OSX only
Apple dropped Windows support after Safari 5.
Con Does NOT block Ads
Doesn't block ads, unlike browsers like Brave and Vivaldi.
Con Poor support for new web technologies
Safari usually takes its time when it comes to adopting new and useful web technologies meaning that the user gets an inferior experience compared to other modern browsers.
Con Proprietary
While Safari er is currently available gratis (without monetary charge) on Mac OS X, it is currently not libre (meaning that it does not allow users to view the source code used to create, to modify that code, or to redistribute modifications) and is therefore neither free nor open-source software.
Con Outdated Rendering engine
All other browsers and toolkits (Qt/GTK) have shifted to Googles Blink-fork of KHTML/Webkit so Apple is currently the only main contributor left.
Con Terrible support for open source formats like .VP9 or .ogg
Apple does not support open source formats. Instead, they use H.264 and H.265.
Con Even on OSX not the best Experience
Video controls are bad esp. on youtube. Only few browser extensions.
