3 ms·
"What's missing in REST, btw, is a standard method of serializing structs, lists and scalar types." What benefit would this provide? I assume he's talking abou
by natrius 18y ago
"What's missing in REST, btw, is a standard method of serializing structs, lists and scalar types."
What benefit would this provide? I assume he's talking about this:
"We're all writing code, again and again, every time we support a new interface that could be written once and then baked into the kernels of our languages, and then our operating systems."
But I've never had to write new code just to parse the data from a REST API. You can usually request JSON, and there are plenty of libraries out there for that already. No new code required.
- sh1mmer 18y agoI agree. I'm not sure what his point is given that the request/response format of the data normally provides the serialisation. RESTful services in that respect are no different to RPC ones.
- jonknee 18y agoI think his problem is that he programs in Frontier and he hasn't built any support for JSON. Library support is a rough spot when you write your own programming language, develop in it exclusively, and happen to be one of the only people in the world developing in it. He created his own XML spec for XML-RPC and wants everyone to use that instead of JSON.