@U064X3EF3 First issue I found is that the "clj on Windows" page has a link to the "TDEPS jira", but it's broken.

@U5FV4MJHG Note that there is a powershell installer for clojure, but this approach has a few downsides. E.g. it's hard to shell out to "clojure" from Clojure/Java without invoking powershell as well, it only works from the powershell shell basically, unless you define some wrapper .bat file. There is an alternative installer called clj-msi which wraps deps.clj, a native binary, which is a port of the clojure bash/powershell script to clojure itself and compiled as a single binary (among other targets, but this is what clj-msi uses). https://github.com/casselc/clj-msi https://github.com/borkdude/deps.clj Another way to get deps.clj installed as clj / clojure on Windows is via #C01JDDEBRU1 clojure: there it's called clj-deps. https://github.com/littleli/scoop-clojure You can find conversations about clj-msi in the history of this channel

@U04V15CAJ Fantastic info! Thank you!

@U5FV4MJHG In case you need it, the JIRA TDEPS link should be https://clojure.atlassian.net/browse/TDEPS

@U04V70XH6 Thanks!

Is it possible for me to submit a PR for that wiki page? I would be happy to fix all the links, but I'm not sure if that's the right process or how to do it for a GitHub wiki.

There's no PR process for it. Alex would have to give you direct edit permissions (he had to restrict all the wikis due to spammers). I was a bit surprised I didn't have edit permissions -- I went straight to it to fix it but...

I would rather spend the time rerouting the official instructions to the msi etc

No rush or pressure from me. Sorry there isn't an easy way for me to take it off your plate!

Because it's unofficial, it's burried at the very bottom in alternatives, but where it says: > There is also a Clojure based launcher compiled with GraalVM as a native executable which works with cmd.exe as well as powershell -- see https://github.com/borkdude/deps.clj to get started with it, or just run the following from PowerShell: PowerShell -Command "iwr -useb https://raw.githubusercontent.com/borkdude/deps.clj/master/install.ps1 | iex" and you're ready to type deps at cmd.exe or the powershell prompt to use it. Remark how it's called deps and not clj or clojure, that means it is safe to try this one out on top of the default PowerShell based clj on windows command. > That's the best way in my experience to get a smooth Clojure on windows. Otherwise, WSL2 is the best way, but it's more involved.

But the reason WSL2 is best, is because even if you get Clojure working, everything else will be a struggle as well, tooling, IDEs, even Java

@U0K064KQV the problem with wsl2 argument is following: user wanted banana, and we delivered babana, and gorilla... and the whole jungle.

Ya, but that's just the development reality of Windows. Microsoft even knows it, so invested in bringing the whole jungle to it.

You can try just getting the banana, above works well using deps.clj. but you'll probably want a few more things, like git, emacs, a better shell, etc. Those things will each be another headache to get working correctly on Windows.

git and emacs work just fine for me on windows, even clojure-lsp worked out of the box to my surprise

shell is a pain though

Prior to WSL2, I would always use Git Bash. That worked well for me, but I haven’t tried it recently.

@U0K064KQV it looks the same from the opposite direction though. Windows devs scratch their forefaces when they have to deal with bash on unices. It's just a matter of perspective and experience.

You mean, trying to build a Windows WPF app on a Mac or Linux computer? Cause I'm not talking about the differences in workflows, like PowerShell vs SH abd windows tools vs Unix tools, or registry based config vs file, etc. I mean specifically to Clojure development, a lot of things are never tested on Windows, or don't spend as much time, and make Unix like assumptions. Maybe something shells to curl for example, or is literally implemented as a sh script, etc. Or it assumed a Unix directly structure, or environment variables, etc.

And my experience is that, apart from Microsoft owned development tools and languages, most other open source dev tools, languages, runtime and all treat Windows like that as well.