Clojurians Log v2

hi guys, what is the status of Clojure(Script) in Visual Studio Code? It is productive now? Comparing to for example Cursive. I was trying code in Clojure in VSC a few months ago and there was too many issues about editing code. How does it look now?

@kwladyka what was the issues? I don't think very much has changed in the last months, but O am using Calva for Clojure and ClojureScript, and I think @marc-omorain is at work with improving ClojureVSCode.

Hi @pez, as you can probably remember our talk my main issues was “code editing”, parsing, cursor positioning etc.

I have been at work with some of those issues since we talked, so things might have improved. And I know there is promising work being done on the #parinfer extension.

Among other things I have released a separate extension, Calva Format, for handling formatting (I think I remember you thinking it was important to that concerns of responsibility where a bit clearer between the different extensions). Still a conflict between Calva Format and Parinfer, but I have hopes we can cooperate between the projects to sort that out. I actually raised that concern earlier today in the #parinfer channel.

I'm still having some formatting issues and stuff with parinfer that prevent me from using vscode for my daily driver, but it seems to be coming along

Are you using the bleeding edge Parinfer extension, @mattly?

@pez I'm using the VSIX they posted last week, yeah?

idk if that's bleeding enough 😉

I think that's the VSIX I posted. I can post en even more bleeding one later today. 😃

It seems it is not as easy to get Parinfer to behave in vscode as it is in Atom. Hopefully it can be sorted out, but right now things get a bit like sometimes it works and sometimes not. I suspect performance issues, because I see the same in Calva Formatter and have almost tracked it down to performance there.

well magit keeps drawing me back to emacs

I'm spending half my time at work on Typescript stuff and VSCode is really nice for that

but my personal projects tend toward more obscure languages and emacs is a better fit for that

a lot of people at my work use VSCode though, and so I've been trying to get a feel for what a clojure/script dev environment looks like with it

having cursive/emacs/vim as the best-supported editors is IMO a huge barrier to entry

as Rich Hickey said, “This is what happens to us when we say you should use emacs. It's like somebody wanted to make music and you gave them a soldering iron. It's like: Here you go. Have at it. Start at the bottom.”

and as much love as there is for cursive, I feel it's got a lot of the same issues

ProtoREPL makes a really strong case for Atom, I would say.

yeah, but its clojurescript support is lacking

also most of the people I'm trying to bring over to clojure-land already use vscode 🙂

Yes, vscode seems to be really big. I love it myself. And even though I used to be an Atom user I switched to vscode long before I released Calva. And now developing Calva, of course I will stick with vscode no matter what. 😃 And I will try to bring over as much of the ProtoREPL magic as I can.

Latest Parinfer extension. Not developed by me, mind you. I have just built the package to make it easy for us to test and provide feedback to the developers.