Fork me on GitHub
#cursive
<
2015-11-05
>
cfleming00:11:16

@stuartsierra: Sorry, I’ve been tied up with urgent things, but I haven’t forgotten I need to verify your fix.

cfleming08:11:17

@ricardo: It should be really fast too, so there’s really no reason not to have it enabled.

cfleming08:11:33

Hopefully people won’t need soft wrap now, which is dog slow

ricardo08:11:07

I didn’t get to demo Cursive at that FP meet up, since we didn’t have time to get into code, but people were pleasantly surprised to hear there’s good tooling.

ricardo08:11:54

Including a comment of “but that usually comes after widespread enterprise adoption…”. So you’re ahead of the curve there.

cfleming08:11:11

I’m hoping that Cursive will help that happen!

cfleming08:11:52

I think Cursive is actually an important piece of driving Clojure adoption.

ricardo08:11:15

I had to re-tool the talk at the last minute, when I realized more attendees knew little about Clojure other than it was as LISP-like.

ricardo08:11:20

The language by itself is threatening enough as it is.

cfleming08:11:34

Yeah, no doubt. At some point I’ll get some time to finish the standalone, and have a more friendly getting started experience. I’d like to integrate exercism and/or 4clojure, and I’d like something like a typing tutor for paredit.

snowell12:11:06

That just makes me bummed that I haven’t been able to get the in-IDE REPL working

snowell12:11:17

Because I want the purtyness

stuartsierra13:11:56

@cfleming: No worries, thanks for keeping up with it.

cfleming21:11:30

@snowell: What’s the issue with the in-IDE REPL? Is that for CLJS?