Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mostly with you .... Only thing is that developers do not really need to use Safari to develop code. All they are writting is Ajax and they can use just about any browser that is JavaScript and AJAX compatible. While Safari compatability is probably the best, it is not the only choice. Peple been developing AJAX apps for several months before Apple decided to release Safari for windows.

I am not aware of anything in Safari that will significantly make development any better / faster. It is just a browser.


Yeah, neither am I. It could just be to ensure total Safari compatibility. If there is anything, I guess we'll be hearing about it in the next few weeks.
 
Mostly with you .... Only thing is that developers do not really need to use Safari to develop code. All they are writting is Ajax and they can use just about any browser that is JavaScript and AJAX compatible. While Safari compatability is probably the best, it is not the only choice. Peple been developing AJAX apps for several months before Apple decided to release Safari for windows.

I am not aware of anything in Safari that will significantly make development any better / faster. It is just a browser.

It isn't 'just a browser', it is 'the browser". People can write an app for safari and know exactly how it will operate on the iPhone. I understand your thoughts but feel Safari on Windows means a lot more than you think.
 
I wouldn't call trying to gain market share with Safari focusing on the iPhone.

Read post #115, he explains it pretty well. I put in my own 2 cents in post #170.

Basically, the primary reason they released the Safari beta is because it's the test environment for iPhone apps.
 
Read post #115, he explains it pretty well. I put in my own 2 cents in post #170.

The theory is that the primary reason they released the Safari beta because it's the test environment for iPhone apps.

I'm not stupid. That was my first thought when Jobs announced the port. However, Jobs presented it as if the only goal was to gain market share with Safari. And at the same time bragging about it being the best and most innovative browser in the world.
I know that Steve doesn't like to be modest, but this is really asking for trouble. Especially since the presentation showed their intentions to wipe out FF.
And if they indeed are trying to gain market share with Safari that will take a lot of resources. Clearly a lack in focus in my opinion.
 
i would like to point out that safari now seems to be able to access and render pages that it USED TO a loooooooooong time ago but hasn't for at least 3 years. pages like THIS haven't worked in safari for so long (couldn't see the gallery or images and page would load funny). it used to, in like 10.2 and maybe part of 10.3. that's why i switched to firefox (even though FF has it's own problems lol) cuz this site and many others 'just worked'.

now though - the new safari beta seems to be working again with it. i wonder what they changed and i hope it stays. i might just come back...
 
Here's what I'm confused about: there is little mention that the core of Safari is open source via WebKit. WebKit was ported to Windows almost a year ago (although it might be considered alpha at best). Safari is just an interface to WebKit, like RealPlayer, OmniWeb, or the Apple Dictionary. What's different is that there's now an official Apple port of WebKit and Safari.

So, my question is are the bugs in Safari or in WebKit?

I assume they're in WebKit, so it seems incorrect to talk about "Apple's insecure coding practices" when they're really www.webkit.org's insecure coding practices. Apple has as much control over WebKit as the Mozillla Corporation has over Mozilla.
 
apple should stop wasting there time making this work on windows.

and claiming that it is just as good on windows as mac? so, some pc user can get itunes and safari and be fine without a mac, if thats all they really use?

this is dumb.
 
I'm not stupid. That was my first thought when Jobs announced the port. However, Jobs presented it as if the only goal was to gain market share with Safari. And at the same time bragging about it being the best and most innovative browser in the world.
I know that Steve doesn't like to be modest, but this is really asking for trouble. Especially since the presentation showed their intentions to wipe out FF.
And if they indeed are trying to gain market share with Safari that will take a lot of resources. Clearly a lack in focus in my opinion.

I think they had to come up with a reason other than "iPhone apps are just web pages". And when Steve lies, he lies big. As far as building Safari's marketshare, where is the upside in that? It doesn't really seem like a profitable endeavor. Almost all of the free, non-OS browsers out there are open source.

It's total PR. If the iPhone is a big success (which it probably will be), that alone will boost Safari marketshare, so it's an easy goal to set for themselves. Steve can brag about it at the next keynote.
 
The real question is...

The real question is: When does Apple release the rest of OS X Leopard for PCs? It wouldn't be beyond the realm of possibilities that they could work with someone like Dell and get Leopard working on, say their inspiron line.

Now THAT would be news!!!

If Microsoft is Jealous of Apples relationship with Google, this is would really get his panties in a bunch!!!

Apple ][ Forever!!!
 
I think everyone so far has missed the real reason why Apple have released Safari for Windows. That happens to be developers for the iPhone. Apple would not allow third party developers to write independent apps for the iPhone,
but have instead opened up Safari as a way to get third party apps onto the iPhone. These apps can be written on any computer running Safari. What better way to instantly increase the amount of people able to write apps for Safari
than to put Safari on another 95% of computers? Developers who might like to write an app for Safari/iPhone may not want to go out and buy a Mac just to write an app. But now, they can use safari on their Windows box. So, I guess
this could really be an iPhone related discussion.


Point very well made Guerro
 
Here's what I'm confused about: there is little mention that the core of Safari is open source via WebKit. WebKit was ported to Windows almost a year ago (although it might be considered alpha at best). Safari is just an interface to WebKit, like RealPlayer, OmniWeb, or the Apple Dictionary. What's different is that there's now an official Apple port of WebKit and Safari.

So, my question is are the bugs in Safari or in WebKit?

I assume they're in WebKit, so it seems incorrect to talk about "Apple's insecure coding practices" when they're really www.webkit.org's insecure coding practices. Apple has as much control over WebKit as the Mozillla Corporation has over Mozilla.

Except that Apple is hardly hands-off with coding WebKit. They have help from the open-source community, but I am under the impression that they also write a good portion of the code, and fix a good number of the bugs.

Therefore, the fault can conceivably lie with Apple. And, when Apple ships the final version, they must make sure it is stable and secure (enough), no matter what the state of the current WebKit build is.
 
yawn, i posted this yesterday. I don't care if it is beta, we're talking REMOTE CODE execution on the local machine. That's not a "little bug" imho. Very very disappointing....

In any case, without Adblock/plus , I still won't use it in XP/Vista. When Safari has adblock support, i might consider it for my browsing.
 
yawn, i posted this yesterday. I don't care if it is beta, we're talking REMOTE CODE execution on the local machine. That's not a "little bug" imho. Very very disappointing....

In any case, without Adblock/plus , I still won't use it in XP/Vista. When Safari has adblock support, i might consider it for my browsing.

Yeah adblock certainly is good.
 
bludy windoze! haha thats really quite funy, you can take the safari out the os, but you cant take the flaws out the os

LOL, the Windows people are complaining about things that ALREADY affected them before.....

Yagran you put it so well :D


Plus Safari 3 is still in the Beta, there will be bug but I didn't think there would be as many as this.
 
I think the point most have missed with the how high you can pee fighting contest going on is this. Apple have created software for windows - to potentially increase it's market share and usher in future switchers.

No, not primarily for market share nor future switchers, though those are likely benefits from the move. The #1 reason for releasing Safari for Windows is to gain more browser hits which will in time lead to web developers sticking more strictly to the standards! Currently, the Safari percentage is too low but this move will likely up it significantly.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.