Re: Proposed Design Principles

+1 on extensibility --- forcing everything in as non-optional
leads to bloatware.

Additionally, there needs to be some architectural framework for
language extensibility that is symmetrically mirrored on the UA
i.e. as you deploy a language extension, there needs to be a
reliable mechanism for the UA to discover what plugin or UA
extension would handle the newly introduced language extension.

John Joseph Bachir writes:
 > On Tue, 27 Mar 2007, Maciej Stachowiak wrote:
 > >
 > >
 > > I'd appreciate feedback on these. Are any important principles missing? 
 > > Are any of these wrong? Do they need refinement?
 > How about "optional extensibility is more important than new features".
 > Instead of introducing new features, introduce a system by which users may 
 > add their own features.
 > Yes, I dream of syntactic macros in HTML.
 > But my fantasies aside, I think some note about the value of extensibility 
 > should be included.
 > -- 
 > John Bachir
 > aim/yim/msn/ johnjosephbachir
 > 713-494-2704
 > irc://

Best Regards,

Title:  Research Scientist      
Google: tv+raman 

Received on Wednesday, 28 March 2007 20:46:28 UTC