OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] how much complexity is unavoidable?

[ Lists Home | Date Index | Thread Index ]

> But my puzzlement is not over *why did Apache* create a more 
> complex product than you or James Clark did. It is over the 
> fact that *it is
> possible* to create a product that is every bit as functional 
> yet not as complex.
> 

This doesn't puzzle me. Work expands to fill the time available.

How much smaller would Xalan be if it didn't have the feature to run
parsing and transformation as separate threads? I've no idea; but I do
know that I haven't added such a feature to Saxon, and the reason is
that it seemed like an awful lot of work.

The latest Saxon release (7.3) has enhancements allowing the compiled
stylesheet to be serialized (in the Java sense), as well as reducing the
memory it uses. I would estimate that this has caused a 5% increase in
code size. This is pure feature-creep, and the more people you have on a
project, the more such features you get. 

Michael Kay





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS