> Coen Naninck wrote:
>> I don't see its use since 98% of people browse with Internet Exploder.
> Validation ensures at the very least that your code is error free. Not
> all browsers are as forgiving as IE 6 and even it won't be around forever.
> And 98%? Not all sites are the same, so such wide reaching
> generalizations are always way off the mark. Most sites have nowhere
> near that many IE only users and even if they did it still doesn't make
> sense to exclude anyone, especially when it's just as easy to create
> browser neutral sites.
> Furthermore, are you banking on the fact tha IE will continue to be used
> by a majority of users forever? I wouldn't bet oin it. Have you missed
> the annoucement that IE as a standalone browser is no longer supported
> by Microsoft and that the next version will not be made available
> outside of the next MS OS (Longhorn) to be released sometime in 2005?
> That's, no free standalone downloads anymore. You'll need to buy
> Longhorn to get IE 7. In the meantime, Mozilla will continue to thrive,
> so will Opera and the Mac specific browsers who's user base keep growing
> since IE5 Mac has also been discountinued.
> The web is not, has never been and never will be a one browser
> environment so it doesn't make any sense whatsoever to code for any
> specific browser and its quirks. That's what people did in 1997 when
> Netscape 4 was all the rage? Where's that browser now?
> Coding for standards is the only thing that makes sense and that's what
> yields the best results in all modern browsers, including IE 6. It also
> has several advantages over older Web design methodologies. Some of them
> can be found here:
> I would strongly suggest that you try to learn about the modern methods
> of Web design. A great introduction would be this Webmonkey article:
> Another great source of info might be Jeffrey Zeldman's new book
> "Designing With Web Standards". To get an idea of what it's about, go to
> the book site:
> Project Seven who's DHTML menus have often been recommended as
> alternatives to Fireworks' built-in ones have a great eBook called
> "Foundations" that deals with these issues with a Dreamweaver centric
> Their free tutorials also teach many real world techniques that are
> grounded in modern standards based, accessible Web design.
> Before dismissing the W3C validator as useless, I would try to
> understand its use and benefits better first... :-)