Subject: Re: [xsl] Saxon .Net API performance From: Michael Kay <mike@xxxxxxxxxxxx> Date: Wed, 01 Sep 2010 23:50:16 +0100 |
Thanks AndrewI am acutely aware of your difficulty, having spent many years working for managers who did not understand the benefits of refactoring in software engineering (or rather, the costs of not refactoring). Frankly, there are far too many managers making engineering decisions without the engineering knowledge needed to make them. But I think that professionally, you should aim to sell it on the true benefits - reduced lifetime costs, increased longevity, greater reuse, higher quality, hgher productivity, ..., rather than trying to construct an artificial case based on performance benefits. For if performance benefits are your primary goal, refactoring may or may not be the most appropriate way to achieve them.
Some of our XSLT is unwieldy, and upgrading to XSLT 2.0 will help us organise our code more effectively. What will really help me sell this change to the people holding our purse strings is performance improvements. Apart from grouping, what features of XSLT 2.0 can I take advantage of to improve performance?
Michael Kay Saxonica
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Saxon .Net API performanc, Imsieke, Gerrit, le- | Thread | Re: [xsl] Saxon .Net API performanc, Andrew Welch |
Re: [xsl] XSLT 1.0 question on keys, Michael Kay | Date | Re: [xsl] Saxon .Net API performanc, Michael Kay |
Month |