Comment

Comment on Why Journiv Doesn't Use CalDAV (And Why That Makes It More Open)

thelocalhostinger@lemmy.world ⁨4⁩ ⁨weeks⁩ ago

Good blog post, thanks for sharing.

I fully agree with your points about real openness, I think this “file over app philosophy” is the way to go for every self hosted app – make it possible get the data out of there.

What I did not quite understand is why using XML is slower? Why is that – are parsers just slower in general? I do not have a lot of experience with XML, but I always thought it pretty much doesn’t matter whether you send your data via JSON or XML. And how does your JSON structure solve the problem of “content heavyness”?

source

Sort:hotnew top

rockstar1215@lemmy.world ⁨5⁩ ⁨days⁩ ago
Hello, Sorry for the late reply. I do not use lemmy that often and only saw this now when I came here to post about new release. You’re right to call that out. I made an oversimplified claim. Let me clarify, XML vs JSON performance is nuanced:

Parsing speed: JSON is generally faster to parse than XML because:

Simpler syntax (no opening/closing tags, no attributes vs elements decisions)

Less data structure overhead

More direct mapping to native data structures in most languages

Payload size: XML is typically more verbose due to:

Opening and closing tags

Namespace declarations

Attribute syntax

This means larger network transfers

However:

Well-optimized XML parsers can be very fast

The difference matters more for high-volume APIs than occasional journal syncs

For large text content (like journal entries), the actual content dwarfs the format overhead
source