[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: "Phase Relationships in the Standardization Process"

• To: mc@x..., xml-dev@l...
• Subject: Re: "Phase Relationships in the Standardization Process"
• From: Niels Peter Strandberg <nielspeter@n...>
• Date: Fri, 12 Apr 2002 11:36:34 +0200
• In-reply-to: <J71LILJQMJJHEBOIGE1WTOYXLQNCB.3cb5ea9e@MChamp>

Well here is another Gosling quote:

    Design principles.
       + Keep it Simple
          + Redundancy is bad
          + "it's a nice idea" is too weak a criteria: only put in what's 
essential
          + Complex = hard to build, test. debug, tune, explain
       + Use What Works
          + its easier to add something later when you figure out the 
answer
          + Than it is to plster over a mistake that creates a legacy
          + Unnecessary risk increases chance of failure

Taken from, 
http://java.sun.com/people/jag/Presentations/TheStoryOfJava/img20.htm

Niels Peter


> This is probably ancient news to some of you, but James Gosling, in 1990
> http://java.sun.com/people/jag/StandardsPhases/index.html writes:
>
> "For a standard to be usefully formed, the technology needs to be 
> understood:
> technological interest needs to be waning. But if political interest in 
> a standard
> becomes too large, the various parties have too much at stake in their 
> own vested
> interest to be flexible enough to accommodate the unified view that a 
> standard
> requires....

• References:
  • "Phase Relationships in the Standardization Process"
    • From: Mike Champion <mc@x...>

• Prev by Date: RE: "Phase Relationships in the Standardization Process"
• Next by Date: Re: Naive Question about NS 1.1
• Previous by thread: Re: RE: "Phase Relationships in the Standardization Process"
• Next by thread: RE: "Phase Relationships in the Standardization Process"
• Index(es):
  • Date
  • Thread