[
Lists Home |
Date Index |
Thread Index
]
The power is in consistent implementation. Even a technically
weak specification that is implemented consistently provides
a dependable tool. Dependable does not mean powerful. Where
it goes to h**l is in trying to specify too powerful a
system for the requirement. If the implementations are
inconsistent, there are problems in the specification.
I can accept that from a specification; I can't accept
that from a standard. I can wait for a specification to
cycle until the right mix of features emerges, but a
standard indicates that this has already been accomplished.
As for people, humans have to do the jobs and we have
to live with the limits. Experience and competence
are never the same for two people doing one job or
one person doing two jobs.
len
-----Original Message-----
From: Aaron Skonnard [mailto:aarons@develop.com]
The fundamental problem is that we need to agree on a type system. The
next problem is that we have to decide via committee. As David Chappell
recently said "only a committee is capable of deciding something that is
dumber than any of its participants". What one group believes to be
technically solid, another group will find technically weak. The
situation has been the same with every Web-based technology including
HTTP. The power is in compromise.
|
