Re: Target browsers for web development

 
> Ultimately we can only blame the browser upto a certain 
> point, before we have to get off our arses and cope with real 
> world issues.
 

My point was as much about the spirit of "never educate" as it was about
browsers. And my goal was not to blame, but rather to point out that as
members of the technology community, we all cope with different aspects
of the "real world." Those of us who deploy applications within browsers
must accept the limits of today's browsers. But those of us who develop
browsers must seek to transcend the current limits.

The "education" discussion that we're having similarly splits into two
distinct categories. It's not about the definition of the word
education. It's about the subject matter.

It can be helpful, useful and appropriate to enable users to learn more
about the problem domain so that they can more effectively achieve their
goals. For example, it's good to create day-trading software that helps
users learn more about day-trading. In our case, technology is the
medium for this education. But education *about* the medium itself
should be understood as a red flag. Is it necessary? For application
designers today, sometimes it is. But those of us who are responsible
for the enabling technology should perceive in these interactions the
opportunity to do better.

In other words: to the extent that we control the enabling technology,
our goal should be to eliminate the need for education about that
technology. And we can do that in the "real world."

JS

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