[EMAIL PROTECTED] (Vadim Plessky) wrote in
news:[EMAIL PROTECTED]:
>| A developer not checking for it would happen to be a very bad
>| developer.
>
> A manager who will pay developer (or outsourcing company) for tuning
> web site to 1% of all users, out of 100%, will be very bad manager.
Yup. However, web pages now should be modified for NN4, IE4+, and Mozilla.
The first two because they are the standard, and the lizard because it is
the future, because standards are the future.
> Question is: who can confirm that it's "good coder" or notify that you
> are going to recruit "bad coder"?
That's a job for the HR department. If they are clueless, they should
consult an actual coder to see if the new employee can code.
>| You have got it backwards. The standard is defined by w3c. IE does
>| not follow those standards. The fact that millions of people are
>| using a broken browser does not justify coding in broken ways.
>
> Standard is what *used by people*.
No, I'm afraid that you still have got it backwards. The standards are
defined by w3c. Standards should be followed as long as possible.
Sometimes, it's not possible (I don't write 100% standards-compliant HTML,
however, I try to write 100% compliant CSS), but that's the way of the
world. However, IE is NOT the reference point, the reference point should
be either the lowest common denominator (the worst browser a page should be
displayed in according to customer specs) or, if 4+ browsers, an as
compliant page as possible. Yup, it will take some more time, but quality
takes time.
> Why do you think people should rush to remake products when, by
> occasion, somebody releases new *standard*?
Aaah! But that's the point with w3c -- that our products shouldn't HAVE to
be remade every year. Just follow the standards. New browsers will follow
the standards. We are happy! Customers are happy! Customers' customers are
happy! Managers are happy! We are all one big, happy, standards-
compliant family!
> W3C is doing very good job, but it will influence web 3-5 years later.
> look, CSS1 is already 5 years old, but still none browser is compliant
> to it.
That's too bad. However, that's no reason for writing code that only works
in one specific browser.
> To get CSS3 and DOM3 to masses, you need another 5-7 years :-((
I seriously don't think so. Standards are becoming more important to
people.
