March 2, 2026
XML goes fast, comments go furious
Libxml2 Enterprise Edition (AGPL, from the previous maintainer)
Faster XML gets an 'Enterprise' tag—then drops a licensing bomb and bans pull requests
TLDR: A former maintainer launched a faster, safer XML tool under a tougher AGPL license and won’t accept contributions, pointing devs back to the original project. Commenters are split between cheering speed/security and roasting the license, testing stance, and “Enterprise” branding—businesses are nervous, memes are thriving.
An ex-maintainer dropped “Libxml2 Enterprise Edition,” a souped‑up spin on the web’s workhorse for reading XML. It promises up to 10x faster parsing, fixes to denial‑of‑service bugs, and hardened 64‑bit guts. Plot twist: it’s under the AGPL—a strong “share your changes over the network” license—and the project won’t accept code contributions, sending would‑be helpers back to the original libxml2 instead.
Commenters instantly turned this into a popcorn event. One camp is hyped for speed and security, calling this the “XML revenge arc.” Another camp is side‑eyeing hard: “’Enterprise edition’ usually screams parody,” wrote one, while another dragged a rumored testing stance—fuzzing sometimes ≠ proper tests. The “no pull requests” rule had people truly baffled: if this fork fixes flaws, why push contributors to a slower, “more flawed” upstream? Cue memes of an “Enterprise” label slapped on a toaster.
The feature list also stirred drama—Python bindings and Schematron validation are gone—prompting “feature funeral” jokes and “fast but feature‑light” quips. Nerds debated build systems like it’s a sports league, but the real brawl is AGPL vs. MIT: fans say it protects users, critics say it’s a business booby trap. Love it or leave it, the comments are faster than the parser
Key Points
- •libxml2-ee is a C-based fork of libxml2 released under AGPLv3, emphasizing performance and security.
- •The parser is SIMD-accelerated with claims of up to 10x speedups and guaranteed linear behavior against DoS.
- •Security and robustness improvements include 64-bit hardening, avoiding unsafe string functions, and enhanced fuzz coverage.
- •Meson is the canonical build system; CMake and GNU Autotools are also supported with detailed build instructions.
- •Schematron validation and Python bindings are removed; numerous feature toggles and platform options (e.g., AVX, SIMD, iconv, zlib) are provided.