4 ms·
Yep, and it totally gets the job done. (Hey, Steve!) I’m just perpetually surprised that 6 years past 1.0 we don’t have a Rust native implementation of the equi
by chriskrycho 5y ago
Yep, and it totally gets the job done. (Hey, Steve!) I’m just perpetually surprised that 6 years past 1.0 we don’t have a Rust native implementation of the equivalent. What I’ve slowly concluded is: we as an industry more broadly just don’t do that much XML anymore, so the incentives aren’t there. (And here I mean XML as XML. Obviously we have XML-related stuff everywhere in the form of HTML, but it’s a bit of a different world.) And the other piece is that for the XML we do have, the Rust implementations and the binding to libxml are good enough.
- steveklabnik 5y agoHey hey! :) I would agree with this post, for sure. The surprise, and the analysis both. There is of course always a bit of chicken and egg with this kind of thing; people don't use tons of XML with Rust because there aren't good libraries, and good libraries don't exist because people don't use a ton of XML with Rust. Normally this stalemate is broken by something being useful enough for someone to go through and implement a library, but I guess that hasn't come up yet, or that the bindings are indeed good enough.