two issues here #1
As a webmaster for an edu, I have to deal with strict government compliance issues daily, and coding to w3c spec saves time and money.
As a contract developer, developing for IE only at the expense of 9% of your audience saves the client time and money, and is a worthwhile tradeoff since a minimal amount of netscape support can be written in effortlessly.
#2
Web development is a field that constantly strives towards providing applications level functionality that rivals and imitates desktop software. DHTML and SQL are how we make those happen.Regardless of who makes it, IE exceeds css standards, and pushes the envelope for what will come in the next standards. Its a joy to use! I can give my users so much more. Having to make a site netscape compliant means sacrificing features. Its really not about "bells and whistles", its about bringing the user the best experience.
while this experience comes from designing UI for custom database driven applications behind logins, it does apply to the front end as well, albeit to a limited extent.
the solution i have found is this: If you want a custom web-based software solution, you are bound by the same constraints that desktop users are, ie: mac, linux and pc softs are not interchangeable.
behind the login, the functionality is what you want and the browser is what most easily supports the application.
Slashdot Mirror
#1 As a webmaster for an edu, I have to deal with strict government compliance issues daily, and coding to w3c spec saves time and money.
As a contract developer, developing for IE only at the expense of 9% of your audience saves the client time and money, and is a worthwhile tradeoff since a minimal amount of netscape support can be written in effortlessly.
#2 Web development is a field that constantly strives towards providing applications level functionality that rivals and imitates desktop software. DHTML and SQL are how we make those happen.Regardless of who makes it, IE exceeds css standards, and pushes the envelope for what will come in the next standards. Its a joy to use! I can give my users so much more. Having to make a site netscape compliant means sacrificing features. Its really not about "bells and whistles", its about bringing the user the best experience. while this experience comes from designing UI for custom database driven applications behind logins, it does apply to the front end as well, albeit to a limited extent.
the solution i have found is this: If you want a custom web-based software solution, you are bound by the same constraints that desktop users are, ie: mac, linux and pc softs are not interchangeable. behind the login, the functionality is what you want and the browser is what most easily supports the application.
SkizZy