3 ms·
This sentence: "Binary protocols ARE easier than JSON." Does not mean anything. Who defines the "difficulty" of a protocol based on serialization?! What is t
by BoorishBears 7y ago
This sentence: "Binary protocols ARE easier than JSON."
Does not mean anything.
Who defines the "difficulty" of a protocol based on serialization?!
What is that even supposed to mean?
The protocol can be hard to understand, it can make unreasonable demands of users, it can have a ton of bloat or complex backwards compatibility rules.
But the serialization method literally orthogonal to complexity of the protocol itself
Implementing a protobuf serializer or implementing a JSON serializer would be completely 100% outside of the scope of a protocol that uses either.
Doubly so when you're talking about JSON, which has serializers just about everywhere, so you can't even say "oh well the protocol is easy to understand but the serialization method is hard to implement".
If anything using a custom binary serialization implementation would be the worst of both worlds, now consumers have to implement custom serialization AND you have to solve all the issues other solutions did like endianness, backwards compatibility... not having gaping security vulnerabilities...
This is like saying a protocol is "difficult" because you used it over HTTP so now somehow it inherited the entire complexity of HTTP.
Their protocol's complexity isn't defined by it's serialization any more than it is by the transport they're using.
I won't even bother replying to the rest of that, just very vague handwavy rhetoric that's not saying anything much.