Re^2: Model-View-Controller: Template Toolkit vs. XSLT


more useful options
	PerlMonks

Re^2: Model-View-Controller: Template Toolkit vs. XSLT

by DrHyde (Prior)

on Oct 15, 2004 at 08:36 UTC ( [id://399428]=note: print w/replies, xml )

Need Help??

in reply to Re: Model-View-Controller: Template Toolkit vs. XSLT
in thread Model-View-Controller: Template Toolkit vs. XSLT

You forgot the biggest problem with XSLT. That is, that it is clearly trying to be Lisp (just look at all those brackets!) but without the readability or power of Lisp.

From taking one brief look at some XSLT code at a previous job, I can state with absolute certainty that use of XSLT is always wrong. To parse and run XSLT you need a more capable, easier to use programming language to be available anyway, so why not use it instead.

Comment on Re^2: Model-View-Controller: Template Toolkit vs. XSLT

Replies are listed 'Best First'.

Re^3: Model-View-Controller: Template Toolkit vs. XSLT
by hardburn (Abbot) on Oct 15, 2004 at 15:53 UTC

That is, that it is clearly trying to be Lisp (just look at all those brackets!) but without the readability or power of Lisp.

I think there's a fundamental difference here. LISP looks like that because it has to look like that. It's a direct consequence of being minimalistic and functional. XSLT looks like that because the designers thought that XML is Good. There isn't an underlieing, theoretical reason why XSLT has to be implemented that way, as there is with LISP.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

[reply]

In Section Meditations