Fork me on GitHub
#editors
<
2017-08-03
>
grav10:08:19

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

dominicm10:08:28

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

grav10:08:28

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

dominicm10:08:16

Neovim is great 😉 vim

dominicm10:08:32

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

grav10:08:38

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.

grav10:08:53

How is Vim re: linting, completion etc?

dominicm11:08:56

@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.

dominicm11:08:05

(I wrote those two libraries)

grav11:08:29

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

dominicm11:08:13

Yeah, don't take on vim if you're not used to vim yet 🙂

mattly17:08:27

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

mattly17:08:31

still haven't gotten it working

mattly17:08:48

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

mattly17:08:17

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

mattly17:08:57

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

mattly17:08:46

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

seancorfield17:08:10

(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)

mattly17:08:05

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

seancorfield17:08:46

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...

seancorfield17:08:50

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

mattly17:08:03

I'm connected to my boot process via nrepl

mattly17:08:00

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

seancorfield17:08:58

(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)

mattly17:08:39

do you use ink?

seancorfield18:08:45

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

seancorfield18:08:05

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