libxml

The actual parsing code uses libxml, which isn't elisp, but is one of the most widely-deployed parsers around.

And when one of the usual system libraries is compromised (glibc, libssl, libxml), everyone need to update their containers.

At least libxml should use the faster native XML support behind the scenes if available.

So they copied libxml's source, then hacked it up, breaking things like character encoding.

We did a lot of XML parsing at company A, for which we used the open source libxml.

Not that I'm aware of - rvest uses the R package XML which uses the C library libxml.

I can't speak on the performance difference between libxml and cheerio, but jsdom seems to be way slower than cheerio.

I have been using libxml and libxslt for years and as far as I remember I never encountered a bug.

The gemfile.lock and friends make this a bit less of a problem, but you also get to lock things like libxml version or ffmpeg or...

He already uses libxml, so cheerio or jsdom would be alternatives.

It doesn't surprise me that you beat libXML or any library that builds the XML structure into a complete DOM before you can process the first record.

Python package X depend on libxml-foo or libmagick-bar-6.6.7..

"Fast: uses libxml C bindings" Where exactly are these located?

It's easy to think "oh, this script just requires python 2.7", but most of the time you actually have many more dependencies than that (libxml, graphviz, latex, eggs, etc.) A Dockerfile requires some work to setup, but it tracks your requirements in an automated way.