I(POWER)MAC  addendum:

it seems that there has been a problem in my previous post.

The URL from where to download the newest Java Embedding Plugin is the following: http://sourceforge.net/projects/javaplugin/files/  
(Version 1.6.10)

ROBOTANK  I would hardly say it's better than Firefox, though I think that some users prefer it simply because of its better integration with OS X and status as a full-fledged Mac browser rather than a cross-platform port like Firefox. Also, Camino does have some features that require an add-on in Firefox, such as ad blocking and Flash blocking, and it is lightweight and quick. However, as you point out, Camino is lagging behind in terms of its rendering engine. The current stable release of Camino uses the 1.8 branch of Gecko (roughly equivalent to Firefox 2.0.x). Even the upcoming Camino 2 will use the 1.9.0 branch of Gecko (equivalent to Firefox 3.0.x), putting it many months behind most other browsers in terms of standards compliance and support for emerging standards like HTML 5 and CSS 3.  
(Version 1.6.10)

JOHN SAWYER CJS  But it's unlikely that everyone working on web browsers would want to work with everyone else, making compromises, etc. There are definite differences in each browser, reflecting different ideas and techniques used by each set of developers, and so far I've found that to be better instead of worse--it gives people more choice. I agree that when one set of developers figures out some useful feature, etc., other browser developers should try to emulate it, but sometimes various approaches aren't mutually compatible. I used Camino until some time earlier this year, when my personal favorite at the moment switched to iCab--it's fast, can save web pages as single files, in Safari webarchive format, as well as other formats, etc.--all other browsers, except Safari, save web pages by splitting them into little files and placing these files into folders--I find that messy, and it's one of the main reasons I stopped using Camino, since I save a lot of web pages.  
(Version 1.6.8)

ROBOTANK  Isn't that the point of open standards? They allow developers to operate within a single framework and create web sites that work equally well on almost any browser? Most modern browsers, except of course for IE, are very standards-compliant, so I don't see how choice is a bad thing. It seems at this point that it's Microsoft vs. all when it comes to making the web a neutral place.  
(Version 1.6.8)

JKT  But there are only 4 different mainstream web rendering engines:

Gecko

WebKit

Opera's

MS's

You don't have to test against a large number of browsers, just against a few rendering engines and IE 6. If a site is not rendering correctly in one browser using a particular rendering engine, but is in the other browsers using that engine, then it is the fault of the browser and should be fixed by the developer, not the person coding the site.  
(Version 1.6.8)

BUMBLEB  Thank you!

I for one didn't know there was a version 2 beta.

Camino is my fave browser because it is so lean. Luv it.  
(Version 1.6.7)

OZEAN  Well, I do not think that they spend too much time on this. It is mostly backporting a few fixes that are in the 2.x series anyway. The good thing about this is that the 1.6.x branch is the last to support Mac OS 10.3.x – so for these users, Camino is one of the few modern browsers that offer up to date security.

However, I would also think that they should push out their updates more often. I have been using the 2.x nightly builds for months now without any major problems and with many benefits to my browsing experience.  
(Version 1.6.8)

LARRYMCJ  Beta 2 is really nice...BUT...it has a horrible, reproduceable bug they simply won't fix. Google visited links don't change color so you don't know what pages you've searched. Really frustrating. This works fine in the release v1.6.8.  
(Version 1.6.8)