[xsl] RE: Why are there no XSLT processors implemented in XSLT?

Subject: [xsl] RE: Why are there no XSLT processors implemented in XSLT?
From: "Bulgrien, Kevin" <Kevin.Bulgrien@xxxxxxxxxxxx>
Date: Tue, 1 May 2012 07:45:44 -0500
> -----Original Message-----
> From: Bulgrien, Kevin
> Sent: Tuesday, May 01, 2012 7:12 AM
> To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
> Subject: RE: Why are there no XSLT processors implemented in XSLT?
>
> > (As an analogy, many C compilers are implemented in C.)
>
> > The implication of this state of affairs is this: "For real,
> > manly XML processing don't use XSLT; instead, use Java."
>
> > Why are there no XSLT processors implemented in XSLT?
>
> While I might consider making a hammer with a hammer, probably
> it would be of limited benefit to try to make a screwdriver
> with a screwdriver?

> While I might consider making a hammer with a hammer, probably
> it would be of limited benefit to try to make a screwdriver
> with a screwdriver?

To restate with more direct language, highly specialized tools
probably are not useful for recreating themselves whereas general
purpose tools are probably more likely to be useful for creating
more specialized tools.  I do not see a problem with this.  I'd
rather solve a technical problem expediently with a good tool
than being too bothered about what tool was made to make the
tool.  I use awk a lot.  I've never once questioned whether awk
was as powerful as it could be because it was not written in awk.

A craftsman that successfully makes an exceptional tool probably
has the expertise to wisely select the tools he needs to make his
better than everyone elses - without saying that yet another could
not come along and springboard off of the other with some flash of
insight.  Here's to insight!

This message and/or attachments may include information subject to GD
Corporate Policy 07-105 and is intended to be accessed only by authorized
personnel of General Dynamics and approved service providers.  Use, storage
and transmission are governed by General Dynamics and its policies.
Contractual restrictions apply to third parties.  Recipients should refer to
the policies or contract to determine proper handling.  Unauthorized review,
use, disclosure or distribution is prohibited.  If you are not an intended
recipient, please contact the sender and destroy all copies of the original
message.

Current Thread