Quotations tagged json
Filters: Type: quotation × json × Sorted by date
[On SQLite] The JSON interface is like, “we save the text and when you retrieve it we parse the JSON at several hundred MB/s and let you do path queries against it please stop overthinking it, this is filing cabinet.”
— Paul Ford # 29th January 2018, 4:29 pm
I think the Web community has spoken, and it’s clear that what it wants is HTML5, JavaScript and JSON. XML isn’t going away but I see it being less and less a Web technology; it won’t be something that you send over the wire on the public Web, but just one of many technologies that are used on the server to manage and generate what you do send over the wire.
— James Clark # 2nd December 2010, 6:48 pm
JSON sucks. [...] Every time I need to (correctly) represent a large integer such as 4611686018427387900, I’m forced to do so in a string. It causes me to throw up in mouth a little.
— Theo Schlossnagle # 11th October 2010, 11:06 am
XML is better if you have more text and fewer tags. And JSON is better if you have more tags and less text. Argh! I mean, come on, it’s that easy. But you know, there’s a big debate about it.
— Steve Yegge # 15th June 2008, 6:09 pm
Seems easy to me; if you want to serialize a data structure that’s not too text-heavy and all you want is for the receiver to get the same data structure with minimal effort, and you trust the other end to get the i18n right, JSON is hunky-dory.
— Tim Bray # 22nd December 2006, 12:47 am
The good thing about reinventing the wheel is that you can get a round one.
— Douglas Crockford # 21st December 2006, 10:14 am
I read on Niall Kennedy that del.icio.us has come up with an API that returns a JSON structure, and I figured, sheez it can’t be that hard to parse, so let’s see what it looks like, and damn, IT’S NOT EVEN XML! [...] Who did this travesty? Let’s find a tree and string them up. Now.
— Dave Winer # 20th December 2006, 7:21 pm