Safari on Windows was never intended to garner market share. It was created so that web site authors that couldn't be bothered to have a Mac could checkout how their site works on Safari. It has succeeded wildly.<p>Remember, these were darker days. Webkit was the strange thing on the internet. There was no Chrome. There was Konqueror, but the webkits had diverged. You made your site work on IE and Firefox in your preferred order, then after drying your tears with the shredded remains of your schedule gave two minute's thought to making it not obviously be complete rubbish on Safari and maybe Opera.<p>So of course it sucks on windows.<p>• It feels like a Mac but in a Windows world which is like speaking English with an outrageously French accent.<p>• It operates through layers of compatibility designed to identically preserve the Mac behavior above perform well.<p>• When you come down to it, it is the <i>away team</i>. If the user wanted a Mac experience, they'd have a Mac.
I've been using Safari on every Mac I use since I switched back to the platform in '04 or so. It's a nice browser, has all the features I want, and it's quite fast. I've played with Chrome a bit, and it may be faster, but Safari is fast enough.<p>But that's on a Mac.<p>At my last job I had a Windows box. I installed Safari as soon as it was released on Windows for testing purposes. I wouldn't have minded switching, but there was one cold fact in the way: Safari was a pig.<p>I haven't used it on Windows in about a year, so it may be better, but at the time it took a long time to start Safari up. Later releases were better, but it still would feel slow launching and opening tabs. All and all, I stayed with FireFox.<p>I recommend Safari as a good browser for anyone who uses OS X. When people I know have bought Macs and asked if they need to download FF or Chrome, I tell them there is no need. Give Safari a try. Only one or two hasn't stuck with it, it fits all their needs.<p>On Windows I would tell them FF or Chome. Based on my experience there was no reason to recommend Safari.<p>I think it's too late. Even if Apple made Safari an amazing browser on Windows it's a very crowded market. FF is huge, Chrome is big and gaining. IE 8/9 are pretty nice browsers. That's 3 good choices. I have a hard time seeing Apple get any meaningful Windows marketshare.<p>Frankly, I think Safari is only on Windows to allow developers to test their sites to work better on iOS without having the devices or Macs. Any promotion to consumers is very half-hearted.
Could just be me; But I've never found any "Apple" software that wasn't miserable to use on windows. iTunes, QuickTime, Safari... I assume laziness or the feeling that it just isn't necessary on the part of Apple; But who knows.<p>As for why I use Chrome (Even on my Macs); It's just more pleasant to use. It's the sort of thing that's hard to put a finger on, though it does run google web apps way better than the competition which is a huge reason for me also.
This article arrives at the answer and keeps walking. It points out that most people who have used it think Safari on Windows sucks, but somehow refutes that with the fact that it's only a little slower than Firefox and it's version 5.1. What?
I use Chrome on all platforms for which it's available for three reasons:<p>1. It's fast<p>2. It updates automatically<p>3. It has a single location/search bar<p>For me, that's it. Really.
The answers are pretty obvious.<p>1. Chrome is marketed all over the web (and in real life) and bundled through shareware. Google is spending a tremendous amount of money to market Chrome. Apple is not doing that with Safari.<p>2. Safari is the default in OS X, but OS X is still small compared to Windows.<p>3. Safari on Windows is not as fast as Safari on OS X, presumably because Apple cares more about one than the other, whereas Chrome is fast on both platforms. The author seems to assume that since they are both WebKit browsers, that means they are the same, but that isn't true by any measure: First, Google doesn't use the WebKit multiprocess code or the WebKit JS engine, it has its own, and both of those components are very important for speed; and second, even aside from those there are many factors that go into making a browser fast, and just using WebKit (or Gecko or Trident or whatever) doesn't fix them automatically.<p>The real question is how many people use Safari on OS X. That's where it is optimized and bundled. I am guessing the percentage is pretty high, but if it is low, then that would be a surprising fact that requires explanation.
I use both on my machine. Safari is my "Facebook" browser -- I use it for Facebook and Facebook alone.<p>Chrome is my everything else browser. Mainly because it has a unified url/search bar. I have no idea with Safari hasn't picked this up, but that's pretty much it.<p>Oh and also because all the google apps just seem to work better on Chrome.<p>I used use Firefox as my everything browser, but it got just too slow. I mostly only use it for testing and doing front-end development.
Browsers are interesting beasts. Sure, you can compete on speed and compatibility with both standards and existing sites, but only to a point. Once you reach that point, then what? Most of the interaction you will have with a browser is outside the control of the browser (i.e. the code of the sites you visit, ultimately, accounts for 95% of your interaction with a browser).<p>I've found that browsers have become a study in small touches and interesting niches. Firefox, for a long time, had a lock on the "I want to mod the hell out of this" niche. Meanwhile, as trite as it sounds, I couldn't leave Safari for the longest time because I had become addicted to the address bar also showing load progress.<p>These days, I use Chrome, but not because of speed. I use Chrome because I have become addicted to OpenSearch (the "Press tab to search this site"). Apple's refusal to merge the address bar and search bar used to be forgivable, but it is increasingly becoming a pointless distinction to hold out on (and will cost them market share).
Safari's integration of bookmarks and reading lists over iCloud is just such a useful feature to have out of the box. I switched back to Safari just for that. Keeping all my devices in sync is a huge gain over slightly faster rendering times.
Apple products just suck on windows. Look at the massive piece of shit that is Quicktime and iTunes. I don't think that anyone that has used either wants to use another Apple product on windows.
Apple doesn't promote Safari for Windows and it doesn't offer a very compelling experience on that platform. On the other hand, Google has been pushing Chrome like crazy.
I will give the same answer that many on this page have given, Apple software is horrible on Windows. Safari horrible, Quicktime, horrible, iTunes, the granddaddy of horrible. He really didn't have to go any further with the story, he already answered his own question.<p>I like the idea of iTunes and open it occasionally but after a day or two of using it, I am reminded of just how bad it really is.
People talk about Safari being bad on Windows, but frankly, it offers little reason to use it on a Mac either.<p>Really, the only thing that prevents Safari from being the "worst" mainstream browser is the existence of IE.<p>It's not <i>awful</i>. It just pairs mediocre performance with fewer features and lower extensibility.
I'm not a big fan of Safari on Mac either; I use Chrome everywhere, and Firefox only if I want to debug something with firebug. I use Safari only if I need a quick way to run a browser with no personalization settings, to see how sites work.
1. It's fast
2. It updates automatically
3. It's fast
4. I can have all my settings/passwords/bookmarks synced across all my machines regardless of OS
5. It's fast. It opens faster than notebook.exe on Windows and Preview.app on OSX
In addition to what others have said, Safari 5.1 moved to a subprocess model somewhat like Chrome but the change went severely wrong. Memory usage skyrocketed, and speed and stability both took a big dive. After using Safari pretty much exclusively since it was originally released, the awful 5.1 release prompted me to switch to Chrome and I haven't looked back since.<p>Apple's attention really is turned to the mobile space today, and the non-mobile Safari suffers for it.
Safari has the same problems that Firefox has had in Linux for me. Slow startups, not terribly responsive tabs. In addition, it hides downloads on the FS until they're finished, the download box is awkward, and frankly, it still inferior to Chrome.