Clojurians Log v2

a question please: what's the advantage of using brew on linux?

I'm setting up wsl2 atm

never used brew on osx because I work on windows usually, but I got the impression it was mostly a mac thing

@filipematossilva Different flavors of Linux have different installation commands and packaging processes. That's partly why the Clojure CLI is just a shell script with no-autoupdate on Linux -- it's a lot of work getting it packaged into all the different distro repos, and they all have different requirements about how to handle dependencies etc. Clojure CLI already has a brew formula so once you've installed brew on your Linux system, via whatever package management commands your flavor of Linux needs, then it

...it's always brew install clojure and brew upgrade clojure everywhere.

(and scoop install clojure / scoop update clojure on Windows, if we end up standardizing on Scoop there)

So, "convenience", both for users and for the maintainers (at least in the case of Clojure).

ok I see, that makes sense

thank you for the context

I don't use scoop or chocolatey or any of those windows ones, but my impression was that chocolatey was the most popular one

is clojure only on scoop?

Someone in the community made a Scoop manifest and put up a repo and there's talk of maybe adding that to the build for the CLI -- no decisions made yet.

I've no idea about Chocolatey. If that can be done easily and someone from the community volunteers, it becomes an option. But the Windows support requires community volunteers since it's a niche platform for Clojure -- most support has always been Mac/Linux 😐

I'm actually super curious about the windows user numbers

is there some hard data about it?

Clojure has Chocolatey package, but it is version 1.6.0 no more updates.

Plus, Chocolatey requires elevated access right (UAC) which is something I don't like and some people may not have access to (corporate machines).

I wanted to build the package for Chocolatey first, but I got frustrated very quickly and I end up building package for Scoop instead. That's the story.

@filipematossilva While I have no hard numbers, I'll offer this anecdotal evidence: Leiningen supported Mac/Linux for a long time before Windows support was added; Boot similarly supported Mac/Linux for quite a while before Windows support was added; Clojure's on CLI and tools.deps.alpha supported Mac/Linux out of the box but are only slowly getting a stable (alpha) Windows installer -- and tooling based on t.d.a. used to rely on (clojure-env) which shelled out to run clojure -Sdescribe which never worked on Windows, and that has only changed "recently" and not all tooling has caught up yet. So Windows has always been a bit of a "second-class citizen" in the Clojure world -- primarily because none of the Clojure/core team use Windows and the vast majority of Clojure developers also did not use Windows (so there was almost no one able to volunteer to build Windows-based versions of any of the Clojure tools).

That has changed over the years as Clojure has grown and the raw number of Windows users has increased. Hard to say if the percentage has increased. It may have, as Clojure has attracted more beginners (from other languages that have had solid Windows support for years).

I'm very 👍 on scoop, and try to avoid chocolately now. scoop feels a lot closer to homebrew, choco seems more like apt (which I don't love)

ok, scoop and brew are starting to look more like things I should pay attention to

thanks for all the feedback on it!

@seancorfield yeah I feel like windows tooling suffers from that effect a lot...

https://github.com/lukesampson/scoop/wiki/Chocolatey-Comparison