Slashdot Mirror
Safari on Windows, Leopard Debut at WWDC
comm2k writes to mention that Apple has announced a Windows version of Safari along with Leopard, the new version of Mac OS X at this years World Wide Developers Conference in San Francisco. "He said Safari was 'the fastest browser on Windows', saying it was twice as fast as Internet Explorer. A test version of Safari for Windows XP and for Vista is available for download from the Apple website. Apple is hoping to replicate the success of iTunes, which has proved enormously popular on both Macs and Windows machines."
No, Apple is not trying to replicate iTunes' success. Nobody on windows would give a crap if iTunes wasn't the main way to get things onto an iPod. From what info was given about apps for the iPhone, Safari is the SDK. Any greater market share for WebKit is just gravy.
11 was a racehorse
12 was 12
1111 Race
12112
Safari for Windows?
Not a radical new 16-core desktop? Not a 19" Macbook Pro? Not a 30" iMac? Not an Apple-branded virtualisation solution?
Nooooo, SAFARI FOR WINDOWS>
I must ask here.... what the fuck!? Who would care about this announcement? And I say that as a Mac fan!
With spending like this, exactly what are "conservatives" conserving?
Safari for the PC is interesting for three reasons: (1) if widely adopted, it would force more web apps to become Safari friendly. Google apps, for example, often don't work with Safari. (2) Safari is the developemnt platform for iPhone apps. And by releasing Safari for the PC, the developer base just multiplied enormously. (3) Just the fact that iPhone apps are build from HTML and Javascript is going to shake up the mobile web scenario.
At the beginning was at.
So before that you did not care about Safari users? OK, I can understand that, just looking at the market share :)
Don't worry anyway. My guess is that Safari on Windows has more to do with iPhone SDK than with "we want our browser everywhere". iPhone apps being safari based AJAX apps, Apple wants Windows devs to be able to code/test it as well as Mac devs. They definitely have their eyes on the business market (just look at the "salesforce" remark), and they know they *have* to make iPhone dev possible from windows machine.
That's not a nick, that's my NAME.
I am a web developer. Every time I have seen a problem with my pages on Konqueror or Safari, it has turned out that I was not following the specs properly. It is more a reference implementation than another browser to hack for.
The masses are the crack whores of religion.
Hmm... in my experience, coding to IE was much easier because it was much better at interpreting how you wanted something to look like without worrying about being 100% 'standards compliant'. If a site didn't work in FF and worked fine in IE, that was more due to FF not knowing what to do with your code unless you put it together perfectly.
In other words, as a web "developer" you prefer IE because you can be lazy and sloppy and it lets you get away with it.
I don't think it's fair to bash IE for not complying.
Of course it is. Standards are supposed to make your life easier, because everyone agrees up front on how it all works and there is no need to worry about your customers using a browser you havn't tested with: it's all standards, right? Except that IE breaks that, because it doesn't understand a lot of very useful standards and a lot of web "developers" (Like yourself) are sloppy and lazy and write bad code (You again, by the way).
Stop being sloppy and lazy, is what I'm saying here.
This doesn't make a lot of sense to me. You don't have to worry about being standards compliant? How do you write pages? Do you just make up your own version of the standard and write to that and IE happens to read it magically, somehow?
When I generate code, I look at the spec and implement it, then I test it. I'm not always perfect at it, but I basically make things work the way the documented standard claims it should look. Then I test it. Generally it works in every browser (Safari, Firefox, Mozilla, Opera, Konquerer, OmniWeb, etc.) except IE. Then I try to add hacks to get it to look "okay" in various versions of IE all of which break the standard and all or which break it differently. I certainly can and do blame IE for being the only browser that can't work as the spec designates.
If a site didn't work in FF and worked fine in IE, that was more due to FF not knowing what to do with your code unless you put it together perfectly.Generally, I find that when a site does not work in FF it is because I screwed up and did not get it to spec. Generally when it does not work in IE, it is because I did things right, but IE either implements the spec incorrectly and differently than all the other browsers, or because IE is 6-8 years behind the times and is still using a partial implementation of an ancient spec.
Either way, the only reason the 'standards' got put together was because the minorities needed some way to differentiate themselves from IE.Are you trolling? The spec predates any implementation and MS participated in writing most of them.
More power to them, we need the competition, but I don't think it's fair to bash IE for not complying.I think it is more than fair to bash the single largest, wealthiest company for failing to match the quality of a half dozen smaller companies and another half dozen projects funded by hobbyists. MS does not comply with the specs because it is in their best interests to derail the standards and hold back Web development to help maintain their OS monopoly. They are breaking the standards for personal profit and if you don't see that I have a lovely, historic bridge you might be interested in purchasing.
You clearly have never used Office 98 for Mac. This was the only Office version for Mac that truly failed in the martketplace, and fairly so. This was when Microsoft tried to shove a Windows interface and a horrendeous back-end (extensions, extensions, extensions) down the throat of Macheads. Did not work. Even included some incursion of Clippy as a happy bouncing Mac. The horror, the horror, the horror.
Am I the only one who sees the irony in how Macintosh/Mac OS X users whine and moan when an app doesn't match the UI of the Macintosh, to the point where many developers don't think it's worth the effort, but then when Apple ports something to Windows, they keep the ugly, brushed metal, doesn't-act-like-or-match-anything-on-Windows interface?
Schnapple