JUXT Clojure Radar 2021 | Hacker News Reader

JUXT Clojure Radar 2021

juxt.pro

83 pointsdenisw11 comments

Interesting enough, JUXT has put Clojure Deps (https://clojure.org/guides/deps_and_cli) into "Adopt" and apparently seen the ecosystem quickly adopting it. Great to see that the ecosystem is getting less fragmented this quickly.

This is what they write about Clojure Deps:

> We have many older Clojure projects that use Leiningen, and a small number that use Boot (now on hold), but in recent years we’ve switched to deps.edn and clj. We like that builds are simple and fast, and since tools around deps.edn have accumulated rapidly we now use it confidently on all new projects, so we’re placing deps.edn in Adopt.

If you plan on creating your own radar, or you're just interested in how we went about it, there's also a blog post about the process at https://www.juxt.pro/blog/radar-2021.

You're also welcome to use our ClojureScript Radar graphic at https://github.com/juxt/radar.

i'm so happy to see paredit mentioned, it's that tiny gem that never failed to be awesome in decades..

thanks to all involved https://www.emacswiki.org/emacs/ParEdit

How does it compare with smartparens?

Can't honestly say. Some people on #emacs told me that with some config SP was a superset of paredit. It's just that paredit was first and did 90% of my needs. It was also that weird mode that made me think structurally. It's some sort of a tradition you know.

Clojure looks like almost my ideal programming language, nice tooling, features that work well together, and not too hard to learn thanks to great beginner resources, awesome REPL, frontend support.

But I do like my types, so basically I'm conflicted.

In clojure you will likely use spec for your data instead of using types.

This is a different approach worth checking out.

I thought spec wasn't that great? Or was this some time ago and it has improved meanwhile?

I also saw TypedClojure but not sure what to choose.

Before going typedclojure. There is also malli, there is also schema.

People have this urge for types, but I would give it a shot and apply types/validation when you really need or miss important edgecase etc.

Spec is good if you need something robust and highly composable. Its always a tradeoff, but it has the best flexibility.

Is there a better model than this for assessing dependencies? I've never given the problem any thought before this article. The organisation here is appealing, and it is a fast way of communicating thoughts on the ecosystem strength.

I like the form. It's often hard to get even a brief idea of the landscape of an ecosystem that you're not familiar with.

Reply on news.ycombinator.com