Reinventing XML, one data type at a time.
Transit: JSON Data Interchange Format
11–20 of 124 posts
Re: Transit: JSON Data Interchange Format
#12So it's basically a set of libraries used to marshal/unmarshal objects without using a schema or can it also be used as an RPC library?
Re: Transit: JSON Data Interchange Format
#13I can't help but wonder if it isn't simpler just to use gzipped JSON. I'd be interested to see a size comparison of the two. It seems like they're going to an awful lot of work to hand-roll a suboptimal text compression scheme here.
From the announcement blog post:
Transit is self describing using tags, and encourages transmitting information using maps, which have named keys/fields which will repeat often in data. These overheads, typical of self-describing formats, are mitigated in Transit by an integrated cache code system, which replaces repetitive data with small codes. This yields not only a reduction in size, but also an increase in performance and memory utilization. Contrast this with gzipping, which, while it may reduce size on the wire, takes time and doesn't reduce the amount of text to be parsed or the number of objects generated in memory after parsing.
Re: Transit: JSON Data Interchange Format
#14These posts by the author of transit-js clear up some things and go in depth about performance:
http://swannodette.github.io/2014/07/23/a-closer-look-at-tra... http://swannodette.github.io/2014/07/26/transit--clojurescri... http://swannodette.github.io/2014/07/30/hijacking-json/
Re: Transit: JSON Data Interchange Format
#15Very interesting
(just commenting to read it later)
Re: Transit: JSON Data Interchange Format
#16Why choose this over Google's Protocol buffers? https://github.com/google/protobuf
Re: Transit: JSON Data Interchange Format
#17Am I the only one amazed by what the Clojure community and core team are conjuring up? Doing client-side programming with things like CLJS, Figwheel, Reagent and core.async feels miles ahead of what we have in moden-js-land (es6/7, babel, webpack, React, promises). If you were to start a startup today, would you be comfortable going with something like Clojure/script?
I run my startup on Clojure and cljs.
Everything you've mentioned has been awesome for us. The arrows we take as pioneers are things like having to roll libraries for email-as-a-service, stripe, etc. Granted it's usually easy but can be time consuming.
Re: Transit: JSON Data Interchange Format
#18Reinventing XML, one data type at a time.
Hopefully something better than XML comes of it before the enterprise gets its grubby hands on it!
Re: Transit: JSON Data Interchange Format
#19Reinventing XML, one data type at a time.
My thoughts exactly. JSON is great for Javascript clients, but if you're dealing with clients written in multiple languages then there is already a good language-neutral serialisation format: XML. Just because it's not fashionable (with some) doesn't mean it doesn't work.
Edit: So why the downvotes? How about a conversation instead?
Re: Transit: JSON Data Interchange Format
#20Reinventing XML, one data type at a time.
Hopefully something better than XML comes of it before the enterprise gets its grubby hands on it!
Enterprise here. We like XML because it's explicit.
{ number: 1.0000000000000000000000000000001 }