hw-xml has a very specific place it is designed for, which is succinct indexing and lookup within large files, not whole-document parsing (i.e. its designed for a very specific out-of-band sort of usage). it also has a lot of sharp edges and needs care to be used correctly – i suspect the benchmarking doesn’t exercise its strong point, but does indicate that xeno would be preferable for other cases, and the low-dep-footprint is a huge plus. xml is certainly a place where there’s little in the way of “one size fits all” answers.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Building web apps in 2024 - learning resources, libraries etc | 9 | 6604 | April 7, 2024 | |
Vector type proposal discussion, blog | 11 | 1467 | April 5, 2021 | |
All my projects (2008-2023) | 6 | 1319 | June 26, 2024 | |
Looking for feedback on Library, specifically ways to simplify | 12 | 834 | June 19, 2023 | |
(Haskell in Haskell) 3. Parsing - Cronokirby | 2 | 658 | December 29, 2020 |