@gjnoonan: Thanks!

@bozhidar: You talked about cljs repl support for Cider was tricky due to recent clojurescript changes. Why is that the case since it works so well in inf-clojure?

because inf-clojure just runs the default cljs repl and sends text to it

the interactions between cider, nrepl & piggieback are way more complex

e.g. var definition location is not tracked by nrepl’s eval op

but it gives other benefits I suppose?

so we had implemented a hack relying on loading dummy files in the repl, instead of using eval

but the behaviour of piggieback changed, because of an upstream change in cljs

and this broke cider...

yep, cider is way more powerful

there are limits to what you can do just by piping plain text in a repl

e.g. eldoc is not enabled in inf-clojure, because evaluating all the time the necessary code is super slow there for some reason

and implementing something like cider’s debugger would be impossible

although one can always use a repl debugger with inf-clojure (e.g. clj-debugger)

inf-clojure exists mostly as a simpler tool, for people who don’t need all the power (and complexity) that comes with cider

@bozhidar: ok, I’ve been very happy with using cljs+inf-clojure but I still prefer Cider for ordinary Clojure development

but cider is definitely the way to go if you do a lot of Clojure programming

yeah, sadly I haven’t had much time to refine the cljs support in cider

but I hope it will be solid by the time we reach version 1.0

@bozhidar: Cool! I would like to help out but not sure where to start

The issues (https://github.com/clojure-emacs/cider/issues?page=2&q=is%3Aissue+is%3Aopen) and the readme would be my suggestions

there’s plenty of things that don’t work the same way on cljs as they do on clj

and this was the issue I referred to on the podcast https://github.com/clojure-emacs/cider/issues/1088

this requires some work to be done in cljs and nrepl themselves

but if something like this gets implemented it will benefit the entire community