News for hackers. Stuff that matters.
Re:Show HN: Skir – like Protocol Buffer but better by dewey on Sunday March 08, 2026 @02:36PM (#47299783)
> Skir is a universal language for representing data types, constants, and RPC interfaces. Define your schema once in a .skir file and generate idiomatic, type-safe code in TypeScript, Python, Java, C++, and more.

Maybe I'm missing some additional features but that's exactly what https://buf.build/plugins/typescript does for Protobuf already, with the advantage that you can just keep Protobuf and all the battle hardened tooling that comes with it.

Re:Show HN: Skir – like Protocol Buffer but better by gepheum on Sunday March 08, 2026 @03:11PM (#47300138)
Skir has exactly the same goals as Protobuf, so yes, that sentence can apply to Protobuf as well (and buf.build). I listed some of the reasons to prefer Skir over Protobuf in my humble opinion here: https://medium.com/@gepheum/i-spent-15-years-with-protobuf-t... Built-in compatibility checks, the fact that you can import dependencies from other projects (buf.build offers this, but makes you pay for it), some language designs (around enum/oneof, the fact that adding fields forces you to update all constructor code sites), the dense JSON format, are examples.
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.
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. """

Re:Show HN: Skir – like Protocol Buffer but better by hrmtst93837 on Monday March 09, 2026 @07:03AM (#47307457)
Buf plus Protobuf already give you multi-language codegen, a compact tag-based binary format with varint encoding, gRPC service generation, and practical tools like protoc, descriptor sets, ts-proto, and buf's breaking-change checks.

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.

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.