me again,
the 'absolute' criteria of simplicity being Radia's ability
to explain it in under an hour is novel. but, i expect that
she could, if she wanted, explain the most important
concepts of today's routing system in the same amount of
time. the level of abstraction in the explanation would
help her keep to constant time.
there is a tradeoff in simplicity. my assumption is that
people will continue to want the services and features they
want today as well as new features they think of for the
future. while it is possible to create a minimalist
architecture that moves the complexity away from the
primitives, i.e. the components and component interfaces,
the complexity would then move to the combinations of
these simple entities (and their management). i question
whether this really makes the system any simpler. in an
architecture it may be beneficial to balance the complexity
of combinations against the complexity of the primitives and
come up with a solution that is sufficiently rich while
remaining as simple as reasonable.
this is no to say i disagree with goal of simplicity, but it
worries me as a hard MUST requirement.
a.
-- Mobile: +46 73 029 8019 Office: +46 920 49 3030http://www.bethepeople.com/vaccine_rides/events_vacc_eu.htm Rider: Avri Doria Rider #: 1338
This archive was generated by hypermail 2b29 : Mon Aug 04 2003 - 04:10:04 EDT