i just dove into clj & cljs w/o such a cost-benefit analysis b/c after writing some scheme and elisp, it seemed like it would be fun, maybe more fun than js, and for the most part, it has been.
good article overall. a point that was a little irksome was
> chrome devtools is way ahead of your cli repl (and even your editor-integrated repl) in a bunch of important ways
(emphasis added). b/c while i'm not saying the devtools is not ahead of figwheel+cider in some sense, enumerating specific want-to-haves would be more informative.
my main nice-to-have (and maybe there's something out there???) would be a way to set breakpoints for dropping into a repl. b/c of the scarcity of mutable state, it hasn't been such a problem, but there have been one of two times where i could've saved a few minutes by throwing a `(debugger)` or something in.
good article overall. a point that was a little irksome was
> chrome devtools is way ahead of your cli repl (and even your editor-integrated repl) in a bunch of important ways
(emphasis added). b/c while i'm not saying the devtools is not ahead of figwheel+cider in some sense, enumerating specific want-to-haves would be more informative.
my main nice-to-have (and maybe there's something out there???) would be a way to set breakpoints for dropping into a repl. b/c of the scarcity of mutable state, it hasn't been such a problem, but there have been one of two times where i could've saved a few minutes by throwing a `(debugger)` or something in.