Menu

I wrote my third XML parser. Here's why this one was different.
πŸ“°
0

I wrote my third XML parser. Here's why this one was different.

DEV CommunityΒ·PaulΒ·about 1 month ago
#kxSscOTW
#why#kotlin#atom#fullscreen#author#string
Reading 0:00
15s threshold

Hi, I'm Pasha, and I write XML parsers. Not because the world needs another one. The world has xmlutil by Paul de Vrieze, which I will say specific nice things about further down. The world has JAXB. The world has, depending on how you count, several hundred XML libraries on Maven Central. Adding to the pile is not on anyone's wishlist. And yet, here I am. The first one I wrote years ago for a previous employer, behind a closed-source repo I no longer have access to. The second one, staks , is mine and works very well β€” if you write Kotlin and only Kotlin, and you are happy hand-rolling a small DSL per record. The third one is xml-fluss, which I just released, and the rest of this post is about why it exists. So, let's get going. The feed that started it I have a soft spot for OPDS catalogs β€” Atom-flavored XML feeds for ebook libraries. They are exactly the kind of thing XML was invented for and exactly the kind of thing modern tooling makes you suffer to read.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More