unrepl

discussing specification of an edn-based repl and its implementations.
pesterhazy 2017-07-15T13:26:47.980441Z

@dominicm we considered transit, but it has some drawbacks

pesterhazy 2017-07-15T13:26:59.981155Z

It's not human readable

pesterhazy 2017-07-15T13:27:23.982800Z

And it requires an additional dependency

pesterhazy 2017-07-15T13:28:56.988723Z

Maybe it could be used as an alternative transport mechanism

pesterhazy 2017-07-15T13:29:43.991887Z

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

pesterhazy 2017-07-15T13:30:48.996647Z

You would need a streaming json parser I think

plexus 2017-07-15T13:41:46.042016Z

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.

plexus 2017-07-15T13:42:44.045806Z

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.

dominicm 2017-07-15T14:12:21.170908Z

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

dominicm 2017-07-15T14:13:05.174054Z

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

richiardiandrea 2017-07-15T14:48:27.336715Z

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