Ah, no... Recently I decided to develop a new site with DW8 on my Mac, using FF and Safari as my test beds. After 2 weeks developing the site, I opened up the site on my Windows XP machine under IE. It was phucked... Literally. I had to start over from the ground up. IE interprets things like image Maps, differently from any other browser... Tables, just about everything... I ended up hand coding the site in bbedit and pulling any java as a result. I fault DW with this for the most part, because it should really point out these problems in the development stage, keeping in mind that there are unfortunately a large number of misguided souls still using IE. This time around after completely developing the site using BBedit, all hand coded, and only testing with and IE browser on a PC, I opened up FF on the PC, FF on the Mac, Safari, Mozilla, etc.. and did not see a single issue. If it works with IE, it's probably gonna work with everything...
I find it best to code using Firefox as my primary development platform, and validate to W3C HTML4.01 Strict and CSS2 specifications. I then cross checks in Opera and IE 6&7. I almost NEVER have more than minor cosmetic problems with MSIE or Opera. The key is validating the code and using tableless designs. I only use tables for true data tables; I don't use them for controlling layout. The fastest way to introduce cross browser issues is to code only using MSIE and to not validate one's code. I have even used complex image maps with no issues.
So it would seem that some people figured out what Apple had in mind when they released Safari on Windows and many of us were wrong. Read: http://blogs.zdnet.com/hardware/?p=511 Apple wants to wipe out Firefox and Opera.
That was probably the worst opinion I've seen expressed in a blog in a long time. Interesting take on the subject, but completely out in left field.