As someone who does this as his job, the real issue is web site compatability, as it can be very expensive, even compared to training support staff. Testing and remidification can be very time consuming, and most web developers are MSDN whores, which complicates it even more. And lets not forget third party web applications, over which one doesn't have control...

I am not a programer, but I like to have some of the settings, the bookmarks and other stuff customized when I recomend Mozilla. I was able to do that with 1.5, 1.6 and FireFox 0.8. It was nt easy having to change all the files manualy in the installation using http://www.mozilla.org/unix/customizing.html and other sources.

Even after finishing it (with a satisfactory result), I noticed that although the default setting is to store cookies for current session only, the cookie file is getting filled and neither Mozilla nor FireFox are throwing out the cookies; that is probably a bug. I tried to overcome this by making the cookies.txt file as "read only" in the installation to find out that the installer changes it back during the installation.

The time I had to spend on the customized settings, bookmarks, changing the start page, cookperm.txt, default installation iof the PubMed toolbar in Mozilla and multiple additional search plugins in FireFox is a bit long.

A good CCK would make it easier.

For MSIE look and feel for Mozilla suite take a gander at this: http://kodu.neti.ee/~tar/mozilla.html

Needs some tweaking for 1.7 but works fine with 1.6.

And don't whine about it, nobody is forcing _you_ to use it.