Discussion about all editors used for Clojure/ClojureScript
grav 2017-08-03T10:25:19.782386Z

Anyone using VS Code for cljs dev? How is the experience? Which extension do you use?

dominicm 2017-08-03T10:26:28.805587Z

Someone said they were having issues with the repl integration in the #parinfer channel.

grav 2017-08-03T10:27:28.825296Z

Ok. Iā€™m using Cursive currently, and the dev experience is ok, but Iā€™d like something more light-weight

dominicm 2017-08-03T10:28:16.840780Z

Neovim is great šŸ˜‰ :vim:

dominicm 2017-08-03T10:28:32.845622Z

But if that's not your thing, I hear that Atom's repl (ProtoREPL) is really great.

grav 2017-08-03T10:48:38.225807Z

Hehe. Iā€™m sure Vim is great. I really dig the static analysis that Cursive can do, and afaik, VS Code as well. Atom might be able to, but I find it rather slow compared to VS Code.

grav 2017-08-03T10:48:53.230286Z

How is Vim re: linting, completion etc?

dominicm 2017-08-03T11:05:56.558208Z

@grav completion works great (https://github.com/clojure-vim/async-clj-omni -- shares emacs' engine). Linting is as good as the tools you can find for it, people are reporting success with joker. I'm wrote this https://github.com/SevereOverfl0w/clojure-check (still in alpha) for eastwood & kibit.

dominicm 2017-08-03T11:06:05.561053Z

(I wrote those two libraries)

grav 2017-08-03T11:08:29.607553Z

Looks impressive! I guess the problem I have with Emacs and Vim is that I need to understand a bit too many concepts to get everything setup and running. Cursive is more fire and forget, even if that abstraction breaks down sometimes

dominicm 2017-08-03T11:11:13.658979Z

Yeah, don't take on vim if you're not used to vim yet šŸ™‚

mattly 2017-08-03T17:09:27.120296Z

I was the person having issues with the vscode repl in #parinfer

mattly 2017-08-03T17:09:31.122488Z

still haven't gotten it working

mattly 2017-08-03T17:09:48.132131Z

I stareted #vscode in hopes of finding other people interested in that editor

mattly 2017-08-03T17:10:17.148472Z

it seems pretty nice and I have friends who work primarily in Javascript, Elixir, and Go who swear by it

mattly 2017-08-03T17:10:57.171543Z

I really want to like Atom but I'm having issues with resource usage

mattly 2017-08-03T17:13:46.266530Z

I have a colleague who's on the Atom team and his response was pretty much "yep, that happens sometimes"

seancorfield 2017-08-03T17:45:10.365931Z

(I do all my "officey" stuff inside a Windows 10 VM, including Slack, with just Atom, Terminal, Docker, and a stack of JVM processes on the Mac side... oh, and SourceTree)

mattly 2017-08-03T17:45:22.373019Z


mattly 2017-08-03T17:46:05.398409Z

I left Atom running overnight with nothing open and it's already up to 2GB

seancorfield 2017-08-03T17:46:46.422737Z

That's with Atom running since some time yesterday for me. I don't currently have a REPL running... just starting that up this morning...

seancorfield 2017-08-03T17:48:50.495486Z

OK, that just added a Boot process taking 630MB and Atom Helper crept up to 253MB.

mattly 2017-08-03T17:51:03.574184Z

I'm connected to my boot process via nrepl

mattly 2017-08-03T17:53:00.645882Z

just found your proto-repl-setup repo on github, gonna take a look at that

seancorfield 2017-08-03T17:58:58.862567Z

(just checked, it's up to date, but it doesn't include settings since I share it between Mac and Windows right now and some things aren't cross-platform in the settings, unfortunately)

mattly 2017-08-03T17:59:39.888581Z

do you use ink?

seancorfield 2017-08-03T18:54:45.849084Z

Yeah, it's "standard" in Jason's "opinionated" setup.

seancorfield 2017-08-03T18:55:05.861968Z

So it can show documentation and results inline in the editor.