I have *always* had the opposite problem. I've found, if some java or html is going to break, it is Firefox that it will do it for. I also hate that interface with a passion and consider it clunky and slow.
I use Firefox mainly for either going to pages that were written for it and have issues under IE, or for making corrections to working code to get it to work under FireFox.
I consider it worthy as a emergency backup browser only.
Interesting.
I know that Firefox loads more slowly (at least on first opening it after Windows has loaded) than IE, but then, IE is so deeply integrated into every version of Windows post 98, that it loads 90% of it at boot anyway. :lol:
But still, it has to be taken into consideration that by far the most 'popular' browser is IE - either because it is used by people who have little computer knowledge because 'it comes with the system' or because businesses wish to stick to MS products for whatever reason. And by popular, I meant that IE has something over 80% of the browser 'market' even now.
Generally I find that sites that rigidly adhere to the W3 specifications work perfectly under Firefox... and
can but do not always... work perfectly under IE. The coding screwups necessary to fix various problems with the way IE handles Javascript or CSS are pretty well known, and so most sites tend to use them if they're expecting high volumes of IE-based traffic. Unfortunately, that can cause problems for other browsers that do actually follow the W3 specs - like Firefox and Opera.
It's a bit worrying when something has such market dominance, and the coders are so arrogant that they won't fix problems - they make everyone else code around it.
As for interface... it's all personal taste.