Clojurians Log v2

I am on macOS for a long time now but am dipping a toe back into Windows to flesh out cljs build/test script support for Git Bash

have rotated among the 3 for a while, just recently using windows more for arcadia / unity, neanderthal, and graal / native-image -- definitely interested in stats on windows-using clojure folks.

fwiw, I put this note in the release notes of the latest clj-kondo: > It is unclear what is needed to run the Windows binary on other Windows systems. Until we find that out, Windows is considered experimental, or as GraalVM likes to call it: early adopter. See: #276.

might be that Windows users have been scared away by lack of support - but since that is changing we might attract more? eventually? We have @carkh though! Nice to have someone who lives in Windows here!

bunch of macbook toting, starbucks dwelling yuppies in this community =)

back in my days there were no linux or macbooks, now get out of my lawn =)

what a ride it has been though, from turbo pascal to clojure ...

Over the year; I've been having only a few problems with clojure and windows really. It's only the recent'ish clojure cli that's been troublesome

people are really starting to adopt it, and i have to make it work now

fwiw, the unofficial clj / clojure tool has been helpful here

@sogaiu what editor are you using on windows ?

i use emacs and vscode

emacs cider ?

no, i am not a nrepl fan

i love it with lein

it's good it's working for you 🙂

not quite with clojure cli, but we'll get there eventually !

i hope sooner rather than later!

When I’m doing Clojure work on my Windows laptop, I mostly use Atom/Chlorine on the Windows side and clj on the Powershell side, so that I can start up REBL and a Socket REPL.

Prior to the PS version of CLI, I ran clj on WSL to get a Socket REPL up and Atom/Chlorine on the Windows side (but no REBL, sadly). Chlorine has logic to understand how to map Windows filesystem paths to WSL paths when doing load-file so that combo works.

The nice thing about the Socket REPL approach is that you can attach your editor to any process with no dependencies. Just add the JVM option when starting the process. In my ~/.lein/profiles.clj file I have

:socket {:jvm-opts ["-Dclojure.server.lein={:port 55555 :accept clojure.core.server/repl}"]}

lein with-profile +socket repl

That's a nice take on it, remoting is a good solution. Though i don't see the added value of poweshell, or wsl with its slow disk access.

next wsl should be better though, so wait and see =)

End of the day vanilla windows is competent enough to start a jvm with a couple jars, we've been doing it for years, it's a bit frustrating to suddenly have to fight with powershell and work around it

I'm always the grumpy one, i remember how pissed i was on the uptake of lein back in the days =)

anyways gnight