Re:Show HN: Skir – like Protocol Buffer but better
by gepheum on Monday March 09, 2026 @09:02AM
(#47308488)
Thanks for the comment. I am very familiar with Buf+Protobuf, I think it's a great system overall but has many limitations which I think can be overcome by redesigning the language from scratch instead of building on top of the .proto syntax.
In the Skir vs Protobuf part of the blog post [https://medium.com/@gepheum/i-spent-15-years-with-protobuf-t...], only 2 out of 10 pertain to "syntax" (and they're a bit more than syntax). Since you mention compatibility check, Buf's compatibility check prevents message renaming, which is a huge limitation. With Skir, that's not the case. You also get the compatibility checks verified in the IDE.
Re:Show HN: Skir – like Protocol Buffer but better
by danlitt on Monday March 09, 2026 @10:40AM
(#47309761)
Sorry, you are wasting your time arguing, I am pretty sure this "user" is an LLM.
edit: Apparently not!
Re:Show HN: Skir – like Protocol Buffer but better
by hrmtst93837 on Monday March 09, 2026 @10:51AM
(#47309904)
I could say the same thing about you. Come up with some evidence and we can talk about it.
Re:Show HN: Skir – like Protocol Buffer but better
by AlexeyBelov on Tuesday March 10, 2026 @04:26AM
(#47320472)
They are using an LLM. I've seen accounts that are very obviously LLM bots, but have a human in the loop to reply when you accuse them. Then, of course, they go back to posting obvious LLM text.
If Skir wants to be more than prettier syntax it needs concrete wins, including well-specified schema evolution rules that map cleanly to the wire, clear prescriptions for numeric tag management and reserved ranges, first-class reflection and descriptor compatibility, a migration checker, and a canonical deterministic encoding for signing and deduplication. Otherwise you get another neat demo format that becomes a painful migration when ops and clients disagree on tag semantics.