Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
five04 said:
safari has serious issues with the javascript engine which i've read will be fixed in tiger. khtml is also a crappy engine to build a browser on. oh and one thing i've noticed with my site is that it doesn't show the correct colors with png files. they're all darker than they should be. ie also seems to have this problem, but firefox and mozilla show the correct colors. png's been out for a while and i wish browsers were better with handling them.

Yes, the new kJS engine will be a lot faster.

kHTML is actually a great engine to base a new browser on. Apple had to start with a small code/efficient choice for their developers to completely get their head around it and kHTML was perfect for that. At the time Gecko was overengineered and had too much unneccesary code. Fortunately Gecko is also a very good engine choice now.

Your site doesn't display your .png files correctly because you failed to properly setup ColorSync and calibrate for your system. There is nothing wrong with .png files, Safari is displaying them 100% correctly based on your selected ColorSync profiles.
 
five04 said:
i think it should also be stated the omniweb is safari. right on their website it says this: "Omniweb 4.5 uses the WebCore and JavaScriptCore frameworks from Apple – the same technology used in Safari for rendering web pages."

if you know how you use interface builder you could make your own web browser as well. omniweb doesn't even count as another web browser.

Yes it does because it's not as clean cut as you think. Safari uses Webkit and OmniWeb uses WebCore. While it may be in essence the same thing it is actually very different.

Omni has to use WebCore (as a omniweb framework) to implement many of the changes to their browser because WebKit is limited to what Apple decide to include. Simply creating a WebKit binding in IB would not even get close to the amount of work Omni have put into Omniweb. The disadvantage is Omniweb's engine will most likely never be as up to date as the system webkit that Safari uses.
 
Mav451 said:
the "Home Deport" benchmark? When I used Camino on my iBook, it crashed at least 2-3 times from SIMPLE blogs and pretty much "regular" websites. If it crashes from blogs, I can't imagine using this for anything more serious than simple browsing purposes (vs. research or work, when you want to keep multiple tabs open). Firefox, on the other hand, rarely crashes in comparison, and I'm even using a NIGHTLY!

For the bookmark issue, would Camino be able to import the .html from Firefox (PC) or vice versa? I mean I can ftp it to my site, but I'm worried bout compatability issues.

Camino 0.7 uses the Gecko 1.0 engine
Camino 0.8 uses the Gecko 1.7 engine (exactly the same as FireFox 0.8)

You should notice no difference between the page rendering and the only difference is in the GUI (Cocoa vs XUL). Gecko is also currently faster than kHTML(Safari).

You can import/export the html bookmarks for Camino using the Import Bookmarks.../Export Bookmarks options in the Camino menu.
 
Sparky's said:
So tell me all you Camino maniacs out there, how do you spell check???
We don't.

encro said:
Maybe there is a utility that could be added into the services menu item?
There are several utilities that add this feature to the services menu, but it'd sure be nice if the Camino guys took advantage of the built-in spelling service.

Incidentally, what's all this hulabaloo about Homedepot.com? The site has so much hideous orange I wish my browser would crash, but the current versions of Safari and Firefox both open and browse it just fine, as does the Camino nightly I have installed. What's the issue?
 
which browser is the fastest page renderer? other performance factors like cpu usage and memory are important to me too. can anyone who has done this research (saving me from doing it) please give advice?
 
melchior said:
which browser is the fastest page renderer?
Depends on the page. Apple will tell you Safari is fastest, and it is on some systems and some pages. Camino fans will tell you Camino is faster, and it is under some conditions, too. And Firefox users will tell you it's the fastest, which it probably is in some situations.

Bottom line, any of those three will probably work pretty well. If you're using Panther, the latest version of Safari is pretty zippy under most circumstances, but Firfox will probably work well too (though it won't boot as fast). If you're on 10.2, I'd recommend a Camino nightly instead of either.

They're all in the same general range, though.
 
Well...in my highly unofficial tests just now (consisting of me loading a few webpages and counting time as "one-onethousand", Camino was faster at loading all the web pages than Safari.

Tested Pages:

Macrumors: C: 2s vs S: 3s

eBay: C: 5s vs S: 15.5s

Yahoo: C: 3s vs S: 5s

Slashdot: C: 2s vs S: 5.5s

Of course, this is all very unscientific, but it does "confirm" the fact that every time I use Camino, it feels much faster than Safari. Then again, it is lagging behind me typing this posting. In addition, Camino is known to have some Java problems, and lacks some of the features and interface niceties of Safari. Its a hard choice.
 
If you want to be deadly accurate:

Sparky's said:
"Interesting how my post earlier in this thread got yanked (I mean completely wiped out of the forum) and this one stays." disregard this statement, I am blind

PS this preference was reached in 3 clicks = Safari>Preferences>Tabs

PSS also Bookmarks>(scroll to bottom)Open in Tabs = 2 clicks


That'll be 3 clicks to get to and an extra 2 clicks to check the option and close the window for the tabbed browsing to take effect.

Anyhow, as decent a browser as Safari might be, IMHO, it is nicer to have the same decent browser across multiple platforms. That's why I used to use Opera before FireFox/Bird. From the POV of a SW person, these types of apps make my life easier.
 
Now after several days of analyzing Omniweb, Camino, and FireFox I am not impressed with any one of them over Safari. One major gripe I do have however is that neither Camino or FireFox has a spellchecker. I am also not impressed with the fact that both have a very poor help menu if any at all!!
I like keyboard strokes short cuts and full function-ability within a web browser, and Camino and FireFox at this time just don't measure up to Safari. Sorry sad but true

I'm still in the process of using all mentioned and am evaluating each as much as I can.

Sparky
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.