reply

fun post, thanks for writing this up!

i’ll happily grant you the technical arguments…but even so, we’ve been here before, over and over: JSONPath, SPARQL, LINQ, YQL, XSLT, and even Facebook’s own dead last attempt, FQL. i’ve done deep dives into YQL, Azure Tables/LINQ, SimpleDB, and Facebook’s own Data Store API, one of their earliest. i’ve even developed one of these languages myself. i’m not proud.

they may all be technically better in various ways, but none of them have caught on broadly in the way that REST has. that may be “worse is better” at work. i guess we’ll see what the future brings.

in my own experience with Facebook’s Graph API in granary and Bridgy, the main limiting factor hasn’t been the URL-path-and-query-params interface, but instead their sprawling, complicated, inconsistent data model. i haven’t needed deeply rich or complex querying, though.

Standard