News for hackers. Stuff that matters.
Re:Show HN: Skir – like Protocol Buffer but better by gepheum on Sunday March 08, 2026 @03:05PM (#47300080)
Thank you so much for taking the time to dig into the compile source code and the thorough comment you left.

For dense JSON: the idea is that it is often a good "default" choice because it offers a good tradeoff across 3 properties: efficiency (where it's between binary and readable JSON), persistability (safe to evolve shema without losing backward compatibility), and readability (it's low for the reasons you mentioned, but it's not as bad as a binary string). I tried to explain this tradeoff in this table: https://skir.build/docs/serialization#serialization-formats

I hear your point about the tagline "like protos but better" which I hesitated to put because it sounds presumptuous. But I am not quite sure what idea you mean to convey by "fresh"?

Re:Show HN: Skir – like Protocol Buffer but better by computomatic on Sunday March 08, 2026 @03:38PM (#47300469)
Not the parent but I infer “fresh” as meaning a new approach to an old problem (with the benefits of experience baked in). A synonym of “modern” without the baggage.
Re:Show HN: Skir – like Protocol Buffer but better by gepheum on Sunday March 08, 2026 @03:50PM (#47300619)
Fair. I changed the tagline on the website to "A modern alternative to Protocol Buffer". Thanks for the feedback.
Re:Show HN: Skir – like Protocol Buffer but better by refulgentis on Sunday March 08, 2026 @03:57PM (#47300741)
100%, danke
Re:Show HN: Skir – like Protocol Buffer but better by refulgentis on Sunday March 08, 2026 @03:57PM (#47300743)
Cheers :) (other replier was right on "fresh", "fresh" definitely wasn't right)