Inspite of being anti microsoft, anyone who codes dhtml / css / javascript knows what a pain in the ass getting pages to work in both Netscape and IE is. What really gets me about Netscape 6 is after all the careful balancing work and branching Javascript code we have to use to get our features working in both browsers, Netscape 6 doesn't even support the things that used to work in 4.7.
This means major code rewrites on a large number of sites just to get back to where we were with the previous version.
Netscape never really supported CSS to even CSS1 compliance and 6 was supposed to fix it for good. The fact of the matter is, even IE4 has better support for CSS standards than Netscape 6.
We have all these great technologies that the w3c keeps churning out and all we get are half-assed implementations. Now Microsoft's compliance isn't perfect, but its a LOT better than Netscape's.
Its enough to make you want to write your own browser.
Slashdot Mirror
Inspite of being anti microsoft, anyone who codes dhtml / css / javascript knows what a pain in the ass getting pages to work in both Netscape and IE is. What really gets me about Netscape 6 is after all the careful balancing work and branching Javascript code we have to use to get our features working in both browsers, Netscape 6 doesn't even support the things that used to work in 4.7. This means major code rewrites on a large number of sites just to get back to where we were with the previous version. Netscape never really supported CSS to even CSS1 compliance and 6 was supposed to fix it for good. The fact of the matter is, even IE4 has better support for CSS standards than Netscape 6. We have all these great technologies that the w3c keeps churning out and all we get are half-assed implementations. Now Microsoft's compliance isn't perfect, but its a LOT better than Netscape's. Its enough to make you want to write your own browser.