unrepl

discussing specification of an edn-based repl and its implementations.
ghadi 2018-02-14T18:36:18.000640Z

So what do we think of PREPL so far?

dominicm 2018-02-14T19:36:47.000383Z

My opinion is: - It solves a problem - That problem was already solved by unrepl in a better way - Unrepl provides more very important features e.g. dynamic classpath loading & completion

dominicm 2018-02-14T19:36:55.000169Z

prepl will need to grow far more in order to impress me

dominicm 2018-02-14T19:42:48.000321Z

Having two repls makes things worse in a way, because you now need to target both prepl and socket if you're a client. Because some people will still want to use socket repl.

richiardiandrea 2018-02-14T21:41:24.000027Z

I share the same feeling @dominicm

mikeb 2018-02-14T23:21:21.000224Z

Also, why did he put prepl in the core namespace making every app startup even slower and not a sub namespace where only tooling that needed it could reference it?

ghadi 2018-02-14T23:34:25.000383Z

it's not in the core namespace @mikeb... and it doesn't really slow things down to load a few more functions

mikeb 2018-02-14T23:55:22.000415Z

Ah missed that second file for prepl var on my phone, but it did add a bit to core. Still a few vars here, a few more there and it adds up and it's already an issue.