Xee: A Modern XPath and XSLT Engine in Rust • Hacker News Board

Re: Xee: A Modern XPath and XSLT Engine in Rust

#241

Post by dfawcus » Sun, Mar 30, 2025, 12:14 PM UTC

therealmarv wrote: post #5

Great to see that somebody else creates a true open source XSLT 3 and XPATH 3 implementation! I worked on projects which refused to use anything more modern than XSLT & XPATH 1.0 because of lack of support in the non Java/Net World (1.0 = tech from 1999). Kudos to Saxon though, it was and is great but I wished there were more implementations of XSLT 2.0 & XPATH 2.0 and beyond in the open source World... both are so m…

> I worked on projects which refused to use anything more modern than XSLT & XPATH 1.0 because of lack of support in the non Java/Net World (1.0 = tech from 1999).

For some things that may just be down to how uses are specified. For YANG, the spec calls out XPath 1.0 as the form in which constrains (must and when statements) must be expressed.

So one is forced to learn and use XPath 1.0.

Re: Xee: A Modern XPath and XSLT Engine in Rust

#242

Post by vessenes » Sun, Mar 30, 2025, 8:04 PM UTC

caspper69 wrote: post #110

IgorPartola wrote: post #91

Earlier quoted context omitted.

That’s a flame war that’s been raging for decades for sure. I do wonder what web application markup would look like today if designed from scratch. It is kind of amazing that HTML and CSS can be used for creating beautiful documents viewable on pretty much any device with a screen AND also for creating dynamic applications with pixel-perfect rendering, special effects, integrations with the device’s hardware, and eve…

Had we had better process isolation in the mid-90s, I assume web application development would mostly be Java apps, with a mini-vm for each one (sort of a qubes like environment). We just couldn't keeps apps' hands out of the cookie jar back then.

Well we had flash. It wasn't great. Or it wasn't great enough to keep around without a major browser or OS provider pushing it.

I will remind you that Swing sucked, hard in the 1990s. And HTML was pretty easy to write.

Re: Xee: A Modern XPath and XSLT Engine in Rust

#243

Post by rambojohnson » Mon, Mar 31, 2025, 4:46 PM UTC

geodel wrote: post #41

rambojohnson wrote: post #20

[flagged]

Maybe similar reason as people deploy 100 requests a week micro service on multiple kubernetes clusters across 3 AZs to make sure it is highly available.

or like watching someone lovingly restore a fax machine with carbon fiber casing and a neural net to optimize transmission speed. I’m torn between admiration and existential despair.

Re: Xee: A Modern XPath and XSLT Engine in Rust

#244

Post by winstonewert » Tue, Apr 01, 2025, 9:31 PM UTC

gschizas wrote: post #225

winstonewert wrote: post #216

Earlier quoted context omitted.

I think I can see something of where you're coming from. But a question: You complain about dates in JSON (really a specific case of parsing text in JSON): > If they implement dates, sometimes it's unix-time, sometimes it's 1000x off from > that, sometimes it's a ISO8601-inspired string, and fuck sometimes I just get an > HTTP date. And so on. Sure, but does not XML have the exact same problem because everything is j…

> Sure, but does not XML have the exact same problem because everything is just a text? No, you can specify what type an attribute (or element) is in the XSD (for example, xs:dateTime or xs:date). And there is only one way to specify a date in XML, and it's ISO8601. Of course JSON schema does exist, but it's mostly an afterthought.

It sounds to me like you are thinking something like: if they use XML, they'll have a well defined schema and will follow standardized XML types. But if they use JSON they may not have a well-defined schema at all, and may not follow any sort of standardized formats.

But to my mind, whether they have a well-defined schema and follow proper datatypes really has very little to do with the choice of XML or JSON.

Re: Xee: A Modern XPath and XSLT Engine in Rust

#245

Post by jedwards1211 » Wed, Apr 02, 2025, 10:02 PM UTC

Finnucane wrote: post #197

winstonewert wrote: post #177

Earlier quoted context omitted.

What actually prevents JSON from being used in these spaces? It seems to me that any XML structure can be represented in JSON. Personally, I've yet to come across an XML document I didn't wish was JSON, but perhaps in spaces I haven't worked with, it exists.

in addition to all the things listed above, json has no practical advantage. json offers no compelling feature that would make anyone switch. what would be gained?

simplicity and ease of use is a pretty compelling feature to a lot of people, if not you