Fork me on GitHub
#unrepl
<
2018-02-16
>
devn05:02:12

My feels: Why worry about it? I’m excited by what’s going on in this channel.

devn05:02:25

unrepl has a compelling story

ghadi05:02:14

agreed. I was hoping we could talk technical approaches. Both unrepl and PREPL are machine-targeted REPLs; they share something fundamental

dominicm10:02:44

There is proliferation cost. Unrepl may have to support prepl if it becomes common for that to be the repl exposed via the socket server.

cgrand10:02:18

@dominicm not a big deal.

cgrand13:02:32

I mean: one can use it as a mere transport.

cgrand10:02:23

However it would be sad to have to tunnel through out messages. Prepl has the same upgradability issue than current unrepl (but that I’m going to address) – well unrepl has an answer already (bye messages) but I’m not happy with it.