Apple Safari to be released for the Windows Platform!


Recommended Posts

I'm sure there were plenty of people with the same issue on the first public Mozilla or Phoenix builds. But there were plenty of people that didn't have that issue, and don't with Safari, such as myself. BETA.

ALPHA. and with that, I am done with this topic. goodbye everybody.

Exactly. The only other WebKit based browser for Windows was Swift, and that didn't seem to be hitting prime time anytime soon. I'm really impressed that Apple decided to do this. I may not end up using it as my main browser, but even if I don't it's an excellent tool for testing the websites I design and develop.

I was a supporter of the Swift project, knowing the main [and basically only] developer.

Swift was far from finished, I will tell you. This had nothing to do with Swift, it was only because the WebKit libs [the actual rendering engine] were not fully ported to Windows, and I believe the source wasn't in svn until today. Actually, they might not be in there yet :p

Just a little reasoning behind Swift's lack of completion.

Clint

I was a supporter of the Swift project, knowing the main [and basically only] developer.

Swift was far from finished, I will tell you. This had nothing to do with Swift, it was only because the WebKit libs [the actual rendering engine] were not fully ported to Windows, and I believe the source wasn't in svn until today. Actually, they might not be in there yet :p

Just a little reasoning behind Swift's lack of completion.

Clint

Oh yeah, I read the blog and he had mentioned that, and I'm not putting the project down in any way. It just kinda sucked because I was really hoping it would get finished, you know?

Uh. No. POS.

no.jpg

It loaded 5x slower too.

"Vt{ cickp Crrng" :p

What the heck are some of you doing to get that screwed up text? There HAS to be some setting wrong somewhere for you to be getting that because I've only seen a couple of people's screenshots with that kind of problem, everyone else has the text displayed properly.

On XP x86-64:

- No rendering issues.

- No font issues (expect the contrast)

- Some of the shortcuts are not appliable to my keyboard (pt)

- Random crashes

- Faster than Speedy Gonz?lez

Actually I hope Job's next announcement is that OS X is ported to run on standard PC's:DD I'd buy it in a heartbeat.

Pigs will learn to fly in that day.

@Gaius

Bangbang is right though. Apple are notorious for not fixing things in their Window applications, Quicktime being a great example. What's going to change? They want people to move to their platform away from Windows remember?

You know, I keep hearing this, but no one will ever say what exactly is "broken" about Quicktime on Windows. Can someone PLEASE tell me what you think is broken about it, because quite honestly I never had any problems with it doing what it was supposed to do.

You know, I keep hearing this, but no one will ever say what exactly is "broken" about Quicktime on Windows. Can someone PLEASE tell me what you think is broken about it, because quite honestly I never had any problems with it doing what it was supposed to do.

Same here. It may be a little sluggish sometimes, but not very often, and it does exactly what it's supposed to do without a hitch.

I just realized what's going on with the messed up text. They're all two characters forward in the character map. Why it's doing that, I have no clue, and it's not happening to me. I just thought I'd share though :laugh:

You know, I keep hearing this, but no one will ever say what exactly is "broken" about Quicktime on Windows. Can someone PLEASE tell me what you think is broken about it, because quite honestly I never had any problems with it doing what it was supposed to do.

It's slow as hell. The UI, because it's not native, in any shape or form, is slow to respond. Try resizing Quicktime then try resizing any video player of your choice made for Windows. You'll see the difference instantly. The problem is these are ports and not natively coded. A port is never going to function as smoothly as a native app, but Apple seems content to leave it at that. So be it, however, they lose some users (including me) along the way.

On XP x86-64:

- No rendering issues.

- No font issues (expect the contrast)

- Some of the shortcuts are not appliable to my keyboard (pt)

- Random crashes

- Faster than Speedy Gonz?lez

Pigs will learn to fly in that day.

pigs will be flying long before that announcement

It's slow as hell. The UI, because it's not native, in any shape or form, is slow to respond. Try resizing Quicktime then try resizing any video player of your choice made for Windows. You'll see the difference instantly. The problem is these are ports and not natively coded. A port is never going to function as smoothly as a native app, but Apple seems content to leave it at that. So be it, however, they lose some users (including me) along the way.

But because iTunes ships with every iPod that you see on the street, they are gaining more than they're losing.

Safari's now taking 64MB. Hooray! All this browser testing makes me want to start reusing Opera again.

I'm thinking that there has to be some common denominator with the people who are having the two main problems I've see posted here (screwy text and no text at all). Overall, it seems that the problem isn't the OS (various people seem to have it working or broken on Vista 32-bit and 64-bit as well as XP), so perhaps it has something to do with other things that are installed, or maybe even something odd with video drivers. There seem to be 4 classes of people here:

1. Safari won't install at all

2. Safari installs but won't display any text

3. Safari installs but displays scrambled text

or

4. Safari installs and works fine

Maybe if the people who are having problems would post some helpful information, then we could all figure out what is causing the problems.

FWIW, I installed it in my Parallels install of XP and it worked just fine.

Loaded extremely slow (for starting up), but I was surprised at how fast it rendered pages. I don't like the interface at all, though. Hopefully this will encourage the Firefox team to work to decrease their rendering time though :)

With further browsing, I can confirm what most are saying. ****ing fast rendering and browsing but the amount of RAM it eats gets sillier by the minute. Eating up 83MB now!

By the way guys, for the members who are actually useful and contribute to the testing instead of just bitching and wanting results without doing **** (i.e. most of you), you can display the Debug menu to access extra debugger tools like javascript debugger, using user agents, etc.

Add this to your C:\Documents and Settings\USERNAME\application data\apple computer\safari\preferences.plist file

<key>IncludeDebugMenu</key>
<true/>

More bugs. I had to click preview post like twice and retype some of my last sentences because they somehow dissapeared, again. Watch out before you do Submit guys.

I've installed this on Windows XP under Virtual PC 2007 not to somehow mess up my Vista install. Here are some quick observations that I've made in no particular order:

  • No autoscroll
  • Can't close a tab with middle mouse button
  • Tab close button is on the wrong side of tab for Windows
  • No dropdown for URL bar
  • Slow at startup (the browser loads, but then delays a few seconds before rendering the home page)
  • Status bar not enabled by default (I see this as a security issue because you may not know the URL of the link you're clicking)
  • The UI itself is way too Mac-ish.
  • Window position not remembered after minimize/restore
  • No tooltips for any UI element (I'd really like to know what a certain button does before I click it).

I am currently using it and I am impressed. Very fast speeds, somewhat faster than Firefox.

The only problem is the memory usage. Currently taking up 114,248K, considering that Safari 3 is still in beta and not finished, the memory problem will likely lessen and hopefully be less than Firefox. I am liking this browser and probably will continue to use it.

No, but they can say whatever the **** they want to! It really doesn't matter because it's a browser.

Beta is beta, no matter what stage it's in....

Unless its a Alpha. Which this should have been. I see no way they could have run any RELIABLE benchmarks on this browser and NOT see the huge issues with it and STILL gotten the figures they say.

You can tweak some settings in the .plist files (they open in Notepad) located in -

C:\Documents and Settings\username\Application Data\Apple Computer\Safari

Preferences.plist contains a few of interest, BackForwardListSizeLimit is set to 200, which I guess means dynamic browsing history (and why it is eating so much RAM), I changed it to 20.

HistoryAgeInDaysLimit is set to 31 days, change to 7.

Also this speed tweak I read about, in PubSub.plist-

C:\Documents and Settings\username\Application Data\Apple Computer\Safari\Preferences

Between the <dict> </dict> tags add the lines

<key>WebKitInitialTimedLayoutDelay</key>

<real>0.25</real>

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.