Live data from Hacker News

Why Clojure?

gaiwan.co

301–302 of 302 posts

Re: Why Clojure?

#301

Earlier quoted context omitted.

I gave Clojure a shot some years ago and even wrote an important tool used daily by all employees at our company in Clojure. The problem for me was maintenance. If I had to make any change to that code, I had to dive into the REPL just to understand it. Whereas with something like Java, even if something is poorly written and not documented, I can get at least a minimum understanding of the code just looking at the t…

What about core.typed. I find gradual type systems to be hard to work with for some reason.

core.typed main problem for many years was that it was maintained by 1 (busy) student.

i don't know about nowadays though, he probably has graduated long ago!

nowadays i'd just use core.spec/malli/other honestly (for what i use clojure for).

Re: Why Clojure?

#302
post #94
post #88

Earlier quoted context omitted.

What language ecosystem does this right?

Go

And rust. And elixir. And caml, which, after many years, settled on dune. And, apparently, common lisp, which settled on ASDF sometime before I reached puberty. And, probably, every language born after java.

Which is all the weirder : rich hickey could (should ?) have figure that "building infra" was one of the aspect where clojure was a great fit ("lein as an ant+maven killer.") To be fair, it wasn't as much in the zeitgeist at the time.

Still, a new language nowadays must have, on aday one, a package manager and a linter and a formatter and a test runner, etc... - just like it must have an LSP.

It's funny looking a zig trying to fight this.

It's funny watching roc reinventing that weel.

I guess jblow will rationalize against it for jai.

I wonder if someone is going to standardize "the rest" of the toolchain. ("Language dependency manager protocol", anyone ?)

Post reply on HN