Comments on: Memo to Apple: Drop Safari, Fix Firefox http://www.allpeers.com/blog/2005/04/06/memo-to-apple-drop-safari-fix-firefox/ The official AllPeers blog Thu, 20 Nov 2008 16:41:11 +0000 http://wordpress.org/?v=2.2 By: paulpod http://www.allpeers.com/blog/2005/04/06/memo-to-apple-drop-safari-fix-firefox/#comment-2949 paulpod Fri, 08 Apr 2005 01:49:13 +0000 http://www.allpeers.com/blog/2005/04/06/memo-to-apple-drop-safari-fix-firefox/#comment-2949 It is a bit more complicated than that - the rendering engine of Safari which you rightly say is based on KHTML is embedded into the OS as WebCore, allowing any application easy access to great standards compliant rendering engine *across* the OS. I'm typing this in Net News Wire, but I bet they didn't have to build their entire browsing architecture to get here. It is a bit more complicated than that - the rendering engine of Safari which you rightly say is based on KHTML is embedded into the OS as WebCore, allowing any application easy access to great standards compliant rendering engine *across* the OS.

I’m typing this in Net News Wire, but I bet they didn’t have to build their entire browsing architecture to get here.

]]> By: Dan http://www.allpeers.com/blog/2005/04/06/memo-to-apple-drop-safari-fix-firefox/#comment-2947 Dan Thu, 07 Apr 2005 23:57:38 +0000 http://www.allpeers.com/blog/2005/04/06/memo-to-apple-drop-safari-fix-firefox/#comment-2947 As a Linux user at work and Mac user at home, I've found Firefox's lack of polish on OSX to be very frustrating. However, the newer 1.0+ versions really are a big improvement. So I agree that Firefox is preferable to Safari if you've come from using it on another platform. However, in terms of integration, Safari is still way ahead. For example, it can't currently using OSX "services", which can be compared to extensions that can be used across many applications. As for your "Not Invented Here syndrome" comment, I think you're a little unfair. Safari's HTML engine is heavily based on the open-source KHTML rendering engine. The KHTML v Mozilla question was debated countless times when Apple announced their intention to produce their own browser. I believe they selected KHTML as the code was cleaner and the browser was lightweight: the Mozilla project was in a bit of a quandry at the time. Perhaps if they had to make the decision now, they might choose differently. But they're unlikely to dump a browser in which they've invested a considerable amount of time and money. After all, it's a solid browser with enough features for the average non-technical user. Having said all that, I'm typing this from Firefox :) As a Linux user at work and Mac user at home, I’ve found Firefox’s lack of polish on OSX to be very frustrating. However, the newer 1.0+ versions really are a big improvement. So I agree that Firefox is preferable to Safari if you’ve come from using it on another platform. However, in terms of integration, Safari is still way ahead. For example, it can’t currently using OSX “services”, which can be compared to extensions that can be used across many applications.

As for your “Not Invented Here syndrome” comment, I think you’re a little unfair. Safari’s HTML engine is heavily based on the open-source KHTML rendering engine. The KHTML v Mozilla question was debated countless times when Apple announced their intention to produce their own browser. I believe they selected KHTML as the code was cleaner and the browser was lightweight: the Mozilla project was in a bit of a quandry at the time. Perhaps if they had to make the decision now, they might choose differently.
But they’re unlikely to dump a browser in which they’ve invested a considerable amount of time and money. After all, it’s a solid browser with enough features for the average non-technical user.

Having said all that, I’m typing this from Firefox :)

]]>