Slashdot Mirror
CaminoBrowser.org Launches
Samuel Sidler writes "Introducing CaminoBrowser.org, the new Camino project site. The pages have been completely revamped with up-to-date information, useful and easy-to-read support pages, and, of course, pretty pictures. Months of effort have gone into creating a truly excellent site. While the product pages will remain hosted at mozilla.org, our new website will be the home of the project and all support/development information as well as up-to-date news and information."
I would think Firefox would be Firefox for the Mac. It is very nice, though, primarily because it's a lot lighter on the usage of system resources.
I recently stumbled upon Kazehakase, which uses GTK+ and is available for Linux. It's in many ways a superior Gecko browser for Linux to Firefox, mostly because it avoids the drawbacks of XUL. It has mouse gestures, full text search and thumbnailed history, RSS, better tabbing (drag and drop of them, they can be displayed vertically, etc.), and I believe some sort of benefit for Japanses speakers. Despite their limited development base, I really think Firefox's platform-specific alternatives (including Camino and K-Meleon) are superior to it.
(IIRC) Camino has native widgets. Firefox uses custom ones.
There are 11 types of people in the world: those who can count in binary, and those who can't.
I used Camino until they removed the sidebar feature. I would much rather have my most often used bookmarks on the side of my screen than the way Safari and Camino now do it.
There they were, sitting in the van with all those dials, and the cat was dead. -V. Marchetti, CIA
Camino: :-(
+Nicer tabs
+Better scrolling
+Better integration
-No Mozilla extensions.
-So no way to block Flash or images natively
+Much better preference panel
+Pretty close functionality to Safari.
+Fastest of the three, it seems.
Firefox:
-A little glitchy at times
+Very good extensions support
+Works mostly the same as Firefox on other platforms
-Integration with OSX not so good, nor is it supposed to be.
-Slow at times.
Safari:
+Just works
-No way to block annoying Flash popups
Safari works for most things, Firefox works for the rest, and Camino sort of just ends up out there in case the first two don't work.
-Rob
Marriage doesn't have to suck!
You imagine wrong. For one thing, dedicating part of the Firefox team to making a native OS X port would take resources away from Firefox. They are two different projects with different goals. Firefox is a multi-platform web browser. Camino is an OS X native web browser. In my case, I use Camino because it is far less likely than Firefox to crash my ancient 400 Mhz G4.
"If it's real, then it gets more interesting the closer you examine it. If it's not real, just the opposite is true." -
Looking at the screenshots there's lots of improvements since I last saw it (0.7), but on the Mac side, Safari does everything I need.
My only problem with Safari is that it is so noticeably slower on HTTPS connections. I use a G4 at work, and any time I need to use an HTTPS connection I use Camino because Safari drags so much. It's not so noticeable at home where I have a 1.8GHz G5, but when on slower machines (including my mom's iBook), Safari just drags on secure connections.
Mozilla fanatics will downmod me but, Camino is not a clone. It must be installed/supported/helped instead of Firefox.
Its a native OS X application. If you use Firefox instead, you just have a windows/unix browser on OS X which is 5 years ahead of them.
E.g. Omniweb here, while I write this reply, spell check is in action. It just calls spell check framework of the system.
You wouldn't believe the "services" a mac user uses everyday. For me, a foreigner, its "one click answers" at first place.
Opera does some inventions about the stuff you mention. Their work with IBM will be in cars. A browser which you control purely by voice, voice XML etc.