2 ms·
This seems a Chesterton's fence fail. protobuf solved serialization with schema evolution back/forward compatibility. Skir seems to have great devex for the c
by ndr 7mo ago
This seems a Chesterton's fence fail.
protobuf solved serialization with schema evolution back/forward compatibility.
Skir seems to have great devex for the codegen part, but that's the least interesting aspect of protobufs. I don't see how the serialization this proposes fixes it without the numerical tagging equivalent.
- gepheum 7mo agoHey, Skir does have numerical tagging, see https://skir.build/docs/language-reference#structs https://skir.build/docs/language-reference#structs
- ndr 7mo agoThis seems new and retrofit. The implicit version is brittle design for backwards compatibility. People/LLMs will keep adding fields out of order and whatever has been serialised (both in client/server interaction, and stored in dbs) will be broken.