Fork me on GitHub
#unrepl
<
2017-07-15
>
pesterhazy13:07:47

@dominicm we considered transit, but it has some drawbacks

pesterhazy13:07:59

It's not human readable

pesterhazy13:07:23

And it requires an additional dependency

pesterhazy13:07:56

Maybe it could be used as an alternative transport mechanism

pesterhazy13:07:43

Is it very easy to write a transit parser in, say, elisp?

pesterhazy13:07:48

You would need a streaming json parser I think

plexus13:07:46

Transit parsers are available on more platforms than edn parsers are, but if you do have to implement it I think it's as least as hard as writing an EDN parser. I agree with the other arguments.

plexus13:07:44

the nice thing about the socket repl + blob approach is that each tool is free to make its own version of the blob. If dealing with EDN is too cumbersome in environment X, then make a blob that uses some other transport. Shouldn't be too hard.

dominicm14:07:21

I'm thinking of transit-json when I say it is easier to parse.

dominicm14:07:05

But perhaps that's just because I'm not thinking about the tagged part

richiardiandrea14:07:27

Note that transit-json is not streamable, whereas Clojure's transit is. Got bitten by this. Current implementation I would add.