xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Stevens <...@latchkey.com>
Subject Re: -1 to Anakia
Date Mon, 16 Jul 2001 22:37:29 GMT
> Hi Kids.  I hate to rain on the parade, but I think it would look pretty
> funny to use Anakia instead of XSLT for the Xalan project.  Further, I
> think the use of JDOM in Anakia is moving the opposite direction of a high
> performance for dynamic transformations.
> I don't usually take a non-moveable stand on things, but at least the Xalan
> project will be using Anakia over my dead, bloodied body.  Nor do I think
> the rest of apache should adapt it... I've had arguments Jon before about
> why I think XSLT & JAXP 1.1 is better.
> If someone pulls out the ". Anakia seems to perform much faster than
> Xalan's XSL processor at creating pages. (23 pages are generated in 7-8
> seconds on a PIII 500mhz running Win98 and JDK 1.3 with client Hotspot. A
> similar system using Ant's <style> task took 14-15 seconds -- nearly a 2x
> speed improvement.) " I'll scream.  Like all benchmarks, claims are easily
> made, but details sometimes not so fourth coming.  And, no, I don't want to
> get into a benchmark war with these guys.  I will say the problems with
> Stylebook have very little to do with XSLT or Xalan... it is much more a
> factor of the stylebook code itself (and sometimes how it is using Xalan
> and the DOM).
> I would simply ask you all to double-check your logic about adapting
> Anakia, and whether or not it's really the direction you want to go.
> BTW, the Anakia page is at: http://jakarta.apache.org/velocity/anakia.html.
> I obviously have very strong objections to it's claims.
> -1.
> -scott


I challenge you to come out with performance numbers that show XSLT
rendering the entire Jakarta site faster than Anakia does it. The source
code is in CVS. Have fun. I *seriously* doubt you can do it.

Let me remind you that my performance numbers are with Velocity caching
turned off, Anakia doesn't have to compile stuff into Java byte code and
Anakia's doesn't have to cache every single object and Anakia still kick's
the shit out of Stylebook. You can't argue with that.

So, until you have a better tool created, your arguments against Anakia are
clearly based on your own distaste for anything that does a better job than
your own personal tools that you created.

This is like arguing with Eduardo about JSP. Of course he is going to put
his weight behind JSP and -1 anything else, because he has spent many hours
creating it and is paid to love it. That however, still doesn't mean that it
is a superior technology than what other people have come up with to do the
job with.

That said, Anakia is not perfect (and I'm the first person to admit it).

However, it is currently the best tool that we have today to generate
documentation and websites. It kicks the shit out of Stylebook and Ant's
<style> task. So, unless you step up and create something
better/faster/cheaper/easier, I am not going to consider your -1 as being



In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org

View raw message