HackerTrans
TopNewTrendsCommentsPastAskShowJobs

barefootliam

no profile record

comments

barefootliam
·11 months ago·discuss
These problems are a large part of why later versions of XSLT were developed.
barefootliam
·11 months ago·discuss
This is neither correct nor helpful, i think. There are examples of dynamic pages using XSLT, and the purpose is not compression at all.

A very simple one - https://wendellpiez.github.io/XMLjellysandwich/IChing/

You might as well say JavaScript is just a compression format for Web assembly language.
barefootliam
·11 months ago·discuss
3.0 adds JSON support, maps, arrays, to 2.0 - and many other other changes, including streaming and optimizable recursion with the oddly-named xsl:iterate, but the JSON support is biggest for the in-browser uses.

4.0 will add parse-html() too.
barefootliam
·11 months ago·discuss
XQuery has a different focus from XSLT. XQuery doesn’t have apply-templates, the document-based implicit dispatch that is so central to XSLT, and it doesn’t have the multiple inheritance possible with overloading templates, but it is stronger in the area of modules, and it assumes (in design) an index, a database.

Programmers tend to prefer XQuery syntax, but note that XPath 3 moves XSLT in that direction too, and XSLT 4 will take it further.

The main strength of XSLT for me is that, together with XML, it enables people who do not consider themselves programmers to do advanced text processing.
barefootliam
·11 months ago·discuss
0.02% of public Web pages, apparently, have the XSLT processing instruction in them, and a few more invoke XSLT through JavaScript (no-one really knows how many right now).

It’s likely more heavily used inside corporate and governmental firewalls, but that’s much harder to measure.
barefootliam
·11 months ago·discuss
When i first encountered the early GNOME 1 software back in the very late 1990s, and DV (libml author) was active, i was very surprised when i asked for the public API for a library and was told, look at the header files and the source.

They simply didn’t seem to have a concept of data hiding and encapsulation, or worse, felt it led to evil nasty proprietary hidden code and were better than that.

They were all really nice people, mind you—i met quite a few of them, still know some—and the GNOME project has grown up a lot, but i think that’s where libxml was coming from. Daniel didn’t really expect it to be quite so widely used, though, i’m sure.

I’ve actually considered stepping up to maintain libxslt, but i don’t know enough about building on Windows and don’t have access to non-Linux systems really. Remote access will only go so far on Windows i think, although it’d be OK on Mac.

It might be better to move to one of the Rust XML stacks that are under active development (one more active than the other).