Libxml2 Alternatives

Similar projects and alternatives to Libxml2

Expat

1 8 0.0 C Libxml2 VS Expat

The Expat XML Parser (by coapp-packages)
Xerces-C++

1 112 5.5 C++ Libxml2 VS Xerces-C++

Apache Xerces-C validating XML parser
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
TinyXML

3 4,831 5.6 C++ Libxml2 VS TinyXML

TinyXML2 is a simple, small, efficient, C++ XML parser that can be easily integrated into other programs.
PugiXML

5 3,802 7.6 C++ Libxml2 VS PugiXML

Light-weight, simple and fast XML parser for C++ with XPath support
Libxml2

1 533 9.8 C Libxml2 VS Libxml2

Read-only mirror of https://gitlab.gnome.org/GNOME/libxml2
TinyXML++

0 93 0.0 C++ Libxml2 VS TinyXML++

Discontinued This project is obsolete. TinyXML-2 offers a very similar C++ interface.
pdfalto

1 194 3.6 C Libxml2 VS pdfalto

PDF to XML ALTO file converter
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Nokogiri

20 6,100 9.5 C Libxml2 VS Nokogiri

Nokogiri (鋸) makes it easy and painless to work with XML and HTML from Ruby.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Libxml2 alternative or higher similarity.

Suggest an alternative to Libxml2

Libxml2 reviews and mentions

Posts with mentions or reviews of Libxml2. We have used some of these posts to build our list of alternatives and similar projects.

SVG Based GUI
1 project | news.ycombinator.com | 24 Jan 2021

Starting off, SVG is an XML encoding, which is a rather hairy thing to deal with. Just to get a feel for LOCs:
https://github.com/GNOME/libxml2
There's also the web's (horrible) tendency to make a diarrhea of special-purpose tags and attributes--many of which could be easily subsumed by basic turing-completeness. Compare to postscript, which was a relatively simple, turing complete, stack machine to begin with.
And of course, if we start special-purposing things, we're no longer compliant with the standard, and it would be chaos to call it SVG at that point.