4 ms·
Running a script that interprets a different script to transform a document just complicates things. What do I do when the transform fails? I have to figure out
by basscomm 11mo ago
Running a script that interprets a different script to transform a document just complicates things. What do I do when the transform fails? I have to figure out how to debug both XSLT and JavaScript to figure out what broke.
I don't have any desire to learn JavaScript (or use someone else's script) just to do some basic templating.
- shadowgovt 11mo agoWhat does one do when transform fails right now? You have to debug both XSLT and a binary you don't have the source for; debugging JavaScript seems like a step up, right?
- basscomm 11mo agoI used to be able to load the local XML and XSLT files in a browser and try it. When the XSLT blew up, I'd get a big ASCII arrow pointing to the part that went 'bang'. It still only kind of works in FireFox XML Parsing Error: mismatched tag. Expected: </item>. Location: https://example.org/rss.xml Line Number 71, Column 3: </channel> --^ Chrome shows a useless white void. I enabled the nginx XSLT module on a local web server serve the files to myself that way. Now when it fails I can check the logs to see what instruction it failed on. It's a bad experience, and I'm not arguing otherwise, but it's just about the only workaround left. It's a circular situation: nobody wants to use XSLT because the tools are bad and nobody wants to make better tools because XSLT usage is too low.