Re:Show HN: Skir – like Protocol Buffer but better
by nine_k on Sunday March 08, 2026 @03:07PM
(#47300100)
The entire original post, it seems, is dedicated to explaining why Skir is better than plain Protobuf, with examples of all the well-known pain points. If these are not persuasive for you, staying with Protobuf (or just JSON) should be a fine choice.
[ Parent
| on HN ]
Re:Show HN: Skir – like Protocol Buffer but better
by waynesonfire on Sunday March 08, 2026 @05:11PM
(#47301524)
Why do I have to work so hard just to understand why I should care? Moving me off protobuf requires something at least 10x better--that’s a very high bar. A library that accomplishes such a remarkable feat would slap you in the face with it in the first sentence.
Re:Show HN: Skir – like Protocol Buffer but better
by nine_k on Sunday March 08, 2026 @05:24PM
(#47301648)
If you are fine enough with protobufs so that you're not actively looking for alternatives, maybe you should not spend the effort.
Re:Show HN: Skir – like Protocol Buffer but better
by gepheum on Sunday March 08, 2026 @05:57PM
(#47301982)
+1
Copying from blog post [https://medium.com/@gepheum/i-spent-15-years-with-protobuf-t...]:
""" Should you switch from Protobuf?
Protobuf is battle-tested and excellent. If your team already runs on Protobuf and has large amounts of persisted protobuf data in databases or on disk, a full migration is often a major effort: you have to migrate both application code and stored data safely. In many cases, that cost is not worth it.
For new projects, though, the choice is open. That is where Skir can offer a meaningful long-term advantage on developer experience, schema evolution guardrails, and day-to-day ergonomics. """