Fork me on GitHub
#unrepl
<
2017-09-12
>
bozhidar09:09:49

The practical issue is that repackaging cider-nrepl into a combination of utility library, that would be useful for something like unrepl and the built-in socket repl, plus the existing middleware is some work, that no one really wants to do. 🙂 From a technical standpoint there’s absolutely nothing hard, but someone was to implement this and also a new Elisp client library for unrepl and the necessary abstraction layer in CIDER to make it compatible with different REPL backends. All is easy, but all requires a relatively big amount of work to make it a reality.

cgrand09:09:47

The built-in socket repl is not supported yet, right?

cgrand10:09:54

A slightly different point of view is to use unrepl as the abstracting layer: • a socket repl can be upgraded to unrepl over the wire (CLJ only, CLJS planned) • out of a nrepl connection one can recreate a “pair of streams” repl (demo code in clj, you would need a bridge in elisp), once this is done, this repl can be upgraded to unrepl

cgrand10:09:01

And don’t forget that unrepl doesn’t require additional dependencies on the target

cgrand10:09:15

so even if all you have is a serial line to the repl you can enjoy the “full unrepl experience”™

dominicm21:09:19

I like the idea of unrepl over something dumb like serial or telegraph pole.

dominicm21:09:50

I'd quite happily use it as a http alternative for internal applications