Replies

For IE just add the feature to the site or app and go. With Netscape tweak the code for hours just trying to get a table or some other simple feature to display just how you want it. Netscape lovers, Opera lovers, Mozilla lovers, Gecko lovers....FLAME AWAY!

If you're a professional web developer (so am I) then you know the reason IE works so easly is because it allows BAD CODE to pass. At least netscape didn't let you get away with that, which I think was a GOOD thing. The problem with both browsers (although they've all gotten better) was adhering the the W3C standards.

Hey IE works with complex Lotus/Domino apps without javascript errors. Netscpe 4.7 works OK as well for most of my needs. Who needs to charge clients 150/hour for several man days worth of work so it can work with a crap browser like Netscape 6 or 7. If that is a W3C compliance issue than we need new standards from somewhere else. IBM used to tell us none of the WebSphere/Net Dot Commerce/Lotus configuration stuff would work with IE. They were lying. Now none of them work in new Netscapes...window resize issues. IBM has even jumped ship.