5 ms·
> If you want type safe RPC you have to use an RPC system that at least has types! If you want a type safe RPC, you have to use proper RPC system in the first
by dozzie 10y ago
> If you want type safe RPC you have to use an RPC system that at least has types!
If you want a type safe RPC, you have to use proper RPC system in the first
place. It doesn't matter if it is gRPC, SOAP, XML-RPC, JSON-RPC, or Apache
Thrift. REST doesn't even define serialization format or error reporting.
> you have to use an RPC system that at least has types! What stops me sending `{ name: 12, age: "Hello"}` to your JSON RPC system?
So you claim that JSON doesn't have types, right? And, by extension, Python
and Lisp don't have types, too, because of the very same arguments? You know
you're being ridiculous now, right?
- cpburns2009 10y agoJSON's types are limited (object, array, string, number, boolean, and null) and provides no standard way to define new types. It frequently devolves into ad hoc data structures with stringly typed values. I'm pretty sure that's what @IshKebab meant by JSON being "pretty much untyped".
- dozzie 10y agoI'm pretty sure that's not what he said. He used an argument that is not about how much one can express directly, but about dynamic typing nature of JSON.