Re: Target browsers for web development

> I would like to raise a point highlighted by John and Todd. I'm all for
> empowering the user through good design but should we really be
"educating"
> the user about our coding standards. Standards are for us to worry about,
> they shouldn't be used as a way of bending the user to our design
decisions.

Educating users in this context is very sticky. I think educating users
explicitly about standards is not the right way as they don't care about
standards. But informing them is essential.

Moving to another area of technology, I know that a black and white TV won't
show me colour pictures. But I was not born with this knowledge - I was
told. I understand there are different TVs and only colour ones show colour
pictures because I was informed.

What was essential though was that Black & White TVs did not break when
colour pictures were transmitted due to a very clever use of encoding.

So firstly I think it is fair to inform people they are using old technology
and ask them to consider upgrading - though you will need to show them why
it is worth it. Secondly, there should be some effort to achieve graceful
degradation or alternatives and this should be in your standards.

So when does a browser become too old? Will there be an equivalent of old
browsers causing pollution on the information superhighway and maybe at some
point we will take away their toxic, leaded petrol, information pumps until
they run out of gas.

And why not - things move on...

Cheers,

jod

    --------------------------------------------------------------
     POSTINGS (in plain text): [email protected]
           SUBSCRIPTION CHANGES:  http://lists.syntagm.co.uk
            (or send email to mailto:[email protected])
    --------------------------------------------------------------