Why msg.proto? Why not json?
This seems like an odd dependency to me, and it seems like it adds no value.
This seems like an odd dependency to me, and it seems like it adds no value.
I'm going off of what I've seen myself, and what I've seen in the xi editor:
https://github.com/google/xi-editor
"The protocol for front-end / back-end communication, as well as between the back-end and plug-ins, is based on simple JSON messages. I considered binary formats, but the actual improvement in performance would be completely in the noise. Using JSON considerably lowers friction for developing plug-ins, as it’s available out of the box for most modern languages, and there are plenty of the libraries available for the other ones."
"Performance" in a server also means throughput. There's a reason why protobufs exist and it is all about performance (and type safety which is related) and there's no way JSON serialize/deserialize overhead, in both directions every time, is going to be a good choice here.
Low-friction interfaces for developers are great but I'm not sure I agree with the comparison here.