3 ms·
It's about agility (feedback loops), and enough of the problems with it as a transport mechanism can be addressed by transport encodings that we put up with the
by hinkley 2y ago
It's about agility (feedback loops), and enough of the problems with it as a transport mechanism can be addressed by transport encodings that we put up with the rest.
Is there a similar format that is more amenable to SIMD but has similar ergonomics? That remains to be seen. But if someone makes a compelling case then I'm sure that not only could I be convinced but I could convince others.
Code is meant to be read by humans, and only incidentally by computers. Transport formats are the same thing. HTTP is an even worse format than JSON, and we have really done very little to change its line format in 35 years. It's adequate to the task.
- jvanderbot 2y agoFrom the moment I understood the weakness of my encodings, it disgusted me.
- klysm 2y agoIt not changing is not an indication of its adequacy. It’s merely an indication of backwards compatibility and lock-in effects. It’s not practical to change it even if we did have something better.
- AgentOrange1234 2y agoAren’t “all” the servers and browsers speaking in gzipped html to one another anyway? Couldn’t we do a similar kind of invisible conversion if we had some format better enough to be worthwhile?
- klysm 2y agoIt would be way better to use a binary representation of the structure