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

RE: how much complexity is unavoidable?

• To: "'K. Ari Krupnikov'" <ari@c...>,<xml-dev@l...>
• Subject: RE: how much complexity is unavoidable?
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Wed, 20 Nov 2002 09:44:53 -0000
• Importance: Normal
• In-reply-to: <f0f8yzp9pae.fsf@p...>
• Reply-to: <michael.h.kay@n...>

> 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

• Follow-Ups:
  • Re: how much complexity is unavoidable?
    • From: ari@c... (K. Ari Krupnikov)

• References:
  • Re: how much complexity is unavoidable?
    • From: ari@c... (K. Ari Krupnikov)

• Prev by Date: RE: Namespaces and XML Schema validation
• Next by Date: RE: XSL transformation
• Previous by thread: Re: how much complexity is unavoidable?
• Next by thread: Re: how much complexity is unavoidable?
• Index(es):
  • Date
  • Thread