G
Guest
Guest
I love Safari in Mac OS X, but Safari in Windows suffers some majorly poor porting code. Not the rendering engine, WebKit, it holds fast, but the UI framework is horrid.
Were the time to startup tests done with blank pages, search engine pages, or in Safari's case with the "Top Sites" window open? The "Top Sites" window slows things down hugely, moreso in Windows than on the Mac. Even on my beast of a Xeon Mac Pro with loads of ram Safari can be a little slower in loading the Top Sites window. But that's because it fires off a process to update the thumbnails of all 24 sites I have pinned to the window.
I used to always develop in Firefox but find Safari lighter weight. Chrome with its WebKit internals and nice extension framework is slowly grabbing my attention. I use it exclusively on Windows unless of course I need to test in IE.
Thanks for this article.
Were the time to startup tests done with blank pages, search engine pages, or in Safari's case with the "Top Sites" window open? The "Top Sites" window slows things down hugely, moreso in Windows than on the Mac. Even on my beast of a Xeon Mac Pro with loads of ram Safari can be a little slower in loading the Top Sites window. But that's because it fires off a process to update the thumbnails of all 24 sites I have pinned to the window.
I used to always develop in Firefox but find Safari lighter weight. Chrome with its WebKit internals and nice extension framework is slowly grabbing my attention. I use it exclusively on Windows unless of course I need to test in IE.
Thanks for this article.