Clojurians Log v2

Seeing this error when running clojure -m figwheel.main -O advanced -bo dev within my CLJS project.

Nevermind, this is an issue with Figwheel and not the CLJ CLI on Windows. Sorry!

I don’t know if activity has fizzled on the windows launcher, but was listening to Dave Yarwood on the latest defn podcast and it made me think of the launcher. He mentioning he chose go for a project because it is a cross platform solution that builds self contained stand-alone binaries. Perhaps another line for the decision grid?

I get the impression the last piece of the puzzle to decide is how to package the PS installer. I've been using Scoop since I learned about it and that works very nicely, but I don't know what the trade offs are of various approaches.

The real issue, I think, at this point is that the Clojure/core team have to rely on volunteers from the community who are sufficiently Windows-savvy to carry this over the finish line -- and no one has stepped up yet to do that. Several people have put forward conflicting options -- that all conflict with the basic intended approach of the PS script work done so far.

not sure if it's relevant to clj-on-windows, but wrt things from "elsewhere" working on windows, i'm waiting on the specifics of wsl2 before proceeding to get windows support working for a few projects.

Well, I already use WSL (1) and start a Socket REPL there and connect to it from Atom/Chlorine on Windows native and that works fine.

I've also just discovered that Emacs inf-clojure works with a Socket REPL so staying entirely inside WSL and using Emacs with a Socket REPL is also now an option.

iiuc, wsl2 differs in a number of ways -- i don't know the details (it's still insiders only, right?), but waiting to hear reports of actual usage and/or hope to try it out once it emerges for real. i imagine most folks who have tried porting their macos / linux / other nix stuff to windows have encountered many unexpected and expected issues, and wsl2 / powershell core, etc. are things that are likely to make this overall process easier. i had my recent share of burn-out working to get stuff working on windows, so i'm happy to wait -- w/ wsl2 around the corner, it doesn't seem worth trying wsl (1). (i've used inf-clojure with a socket-repl in a number of situations -- both with clojure clr / arcadia's socket repl and with jvm clojure's. there are a few odd things that i was hoping would get fixed, but last i checked, for whatever reason have not been addressed for some time, for example: https://github.com/clojure-emacs/inf-clojure/issues/153 https://github.com/clojure-emacs/inf-clojure/issues/152 -- my sense is that there isn't anyone currently with sufficient motivation / resources to attend to some of these matters) very much appreciate the efforts on the chlorine front -- particularly how things are attended to in a timely fashion!

With WSL 2, it runs as an actual VM, rather than "natively" on top of Microsoft-written syscall support. But you can't run WSL 2 on Windows Home, only Pro, because it's fully virtualized.

that is an unfortunate limitation :(