Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore semantic changes #27

Open
strangemonad opened this issue Dec 30, 2017 · 0 comments
Open

Explore semantic changes #27

strangemonad opened this issue Dec 30, 2017 · 0 comments

Comments

@strangemonad
Copy link
Owner

Protobufs only capture trivial widening while enforcing consistent ordering. This is not heavy handed solution to a 5% problem (95% of the time the problems proto serialization solves aren’t a real issue)

What’s more interesting is how a field of entity might evolve semantically. Eg a field starts as a Boolean, but always true. Then it’s made to be true or false. Later you realize you needed a ternary (or larger enum). Then maybe you need to store different data with each enum value. Or maybe it needs to be an open ended code that’s based on integers than 3rd parties can add to (eg VNC frame encodings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant