Xee: A Modern XPath and XSLT Engine in Rust

Post by pezezin » Sat, Mar 29, 2025, 12:14 AM UTC

baq wrote: post #62

vessenes wrote: post #13

This, thirty years later, is the best pitch for XML I’ve read. Essentially, it’s a slow moving, standards-based approach to data interoperability. I hated it the minute I learned about it, because it missed something I knew I cared about, but didn’t have a word for in the 90s - developer ergonomics. XML sucks shit for someone who wants to think tersely and code by hand. Seriously, I hate it with a fiery passion. Happ…

XML is a big improvement over YAML. There, I said it.

Post by crabique » Sat, Mar 29, 2025, 1:24 AM UTC

bbkane wrote: post #138

never_inline wrote: post #48

Earlier quoted context omitted.

JQ is the most feature-rich of the bunch. It's defacto standard and I usually just default to it because it offers so much - assignment, various builtins such as base64 encoding. The disadvantage is that it's not easily embeddable in your own programs - so programs use JSONPath / Go templates often.

I also don't think there's a specification written for the jq query language, unlike https://jmespath.org/ , which as you mentioned also has more client libraries. I too am probably going to embed jmespath in my app.I need it to allow users to fill CLI flags from config files, and it'll replace my crappy homegrown version ( https://github.com/bbkane/warg/blob/740663eeeb5e87c9225fb627... )

Post by intrasight » Sat, Mar 29, 2025, 1:32 AM UTC

hyhjtgh wrote: post #59

infogulch wrote: post #53

Earlier quoted context omitted.

I just pulled the 100GB number out of nowhere, I have no idea how much overhead parsed xml consumes, it could be less or it could be more than 2.5x (it probably depends on the specific document in question). In any case I don't have $1500 to blow on a new computer with 100GB of ram in the unsubstantiated hope that it happens to fit, just so I can play with the Wikipedia data dump. And I don't think that's a reasonabl…

Xml and textual formats in general are ill suited to such large documents. Step 1 should really be to convert and/or split the file into smaller parts.

Post by intrasight » Sat, Mar 29, 2025, 1:37 AM UTC

jlarocco wrote: post #100

weinzierl wrote: post #68

Earlier quoted context omitted.

"This, thirty years later, is the best pitch for XML I’ve read." I wish someone would write "XML - The Good Parts" . Others might argue that this is JSON but I'd disagree: - No comments is a non-starter - No proper integers - No date format - Schema validation is a primitive toy compared what we had for XML - Lack of allowed trailing commas YAML ain't better. I hated whitespace handling in XML, it's a miracle how YAM…

It's funny to hear people in the comments here talk about XML in the past tense. I know it's passé in the web dev world, but in my work we still work with XML all the time. We even have work in our queue to add support for new data sources built on XML (specifically QIF https://qifstandards.org/ ). It's fine with me... I've come to like XML. It's nice to have a standard, easy way to do seschemas, validators, processo…

Post by mdaniel » Sat, Mar 29, 2025, 1:59 AM UTC

smartmic wrote: post #128

smartmic wrote: post #125

Earlier quoted context omitted.

Well, it's not as if this is the first free alternative. Here is a wonderful, incredibly powerful tool, not written in Java, but in Free Pascal, which is probably too often underestimated: Xidel[1]. Just have a look at the features and check its Github page[2]. I've often been amazed at its capabilities and, apart from web scraping, I mainly use it for XQuery executions - so far the latest version 0.9.9 has also impl…

Forget to add, for latest XQuery up to 4.0, there is also BaseX [1] — this time a Java program. It has a great GUI/IDE for XQuery rapid prototyping. [1] https://basex.org/basex/xquery/