Fork me on GitHub
#clojurebridge
<
2015-07-02
>
stephan15:07:43

@jellea: you’re sure light table will be used as editor at clojure bridge berlin? I remember cursive being recommended for everyone at the coaches meeting

cfleming15:07:18

@stephan: @jellea: The Cursive setup is still not as easy as it could be, and the UI by default is pretty busy. I spoke to some ClojureBridge folk at clj/west, and I have a plan to make all that better. It’ll be a little while though.

cfleming15:07:43

It’s definitely a priority of mine to make Cursive accessible for things like ClojureBridge.

stephan15:07:56

hehe damn, I didn’t use cursive before but tried it out some days ago to get used to it before clojurebridge

stephan15:07:14

after a while I really liked it 😄

cfleming15:07:22

There’s nothing wrong with that simple_smile

stephan15:07:31

all right, light table it is then.

cfleming15:07:45

I’m not sure - I don’t actually know what the decision was in that case.

cfleming15:07:11

Just that Cursive is not as totally-newbie-friendly as I’d like right now.

cfleming15:07:04

I’m actually helping out at a ClojureBridge in Auckland in September, and I’d like to get at least some of the people on Cursive if possible, to see how it goes.

cfleming15:07:26

If I have time, hopefully I’ll have a standalone download-and-start version by then.

stephan15:07:18

sounds great!

jellea15:07:56

@stephan: we’re going to use Nightcode.

stephan15:07:19

Ok, I’ll try it out over the weekend

seancorfield15:07:00

@stephan: The main issue with LightTable now is OS X Yosemite — it can be very slow and laggy there due to a bug in node-webkit. The upcoming 0.8 release will address that (by virtue of switching to atom-shell!) but it’s still a ways off.

seancorfield16:07:16

LightTable is great everywhere else — and on earlier OS X versions — but virtually unusable on Yosemite 😞 At work we used LightTable all-day, every-day for all our work… until Yosemite… then we all switched (back) to Emacs.

seancorfield16:07:43

NightCode is beginner-friendly enough to be a reasonable choice but it still feels a bit "IDE-ish" (and as I found when I tried it recently, the git integration cannot handle large histories so it isn’t usable in a lot of real world environments — such as at our workplace).