3 ms·
http is a text protocol. Best to deal with values as text, and dynamically as other types when needed.
by ams6110 15y ago
http is a text protocol. Best to deal with values as text, and dynamically as other types when needed.
- colanderman 15y agoMost data sent over HTTP that's parsed by scripts is either XML or JSON, both of which are highly structured. XML in particular has a rich type system.
- ams6110 15y agoYou are leaving out simple urlencoded data sent with GET and POST. I'd say that is a huge chunk of what's parsed by scripts. Also XML and JSON are, at the bottom of it all, text, with (perhaps) type metadata.
- colanderman 15y agoEverything "at the bottom of it all" is just "text", a sequence of octets. The point of a type system is to make sure you adhere to the structure inherent in that series of octets.
- flatline 15y agoSince there is already a very nice, albeit quirky, dynamically typed langauge for the web, I think there is room for something different. If you want to build robust applications with larger teams - as is increasingly the case with JavaScript - it would be really nice to have features of a statically typed language. Same goes with the performance overhead for processor-intensive apps, which we are also seeing more of with JavaScript. We are learning enough about the potential for powerful browser-based apps that we could conceivably start to come up with something better. On the other hand, and to your point, nobody wants to reinvent SOAP.
- technomancy 15y agoSurprised nobody's mentioned Ur yet: http://www.impredicative.com/ur/ http://www.impredicative.com/ur/