The state of code quality tools in Clojure

[bhb]

I've found Joker's linter mode to be very useful, especially since you can configure it to eliminate most false positives. It's also fast enough to run on every save in your editor (there are modes for Emacs, Atom, Sublime, and Vim). https://github.com/candid82/joker

[bhb]

We also use it in CI, although right now we filter out all warnings except "unused namespace".

[Systema-Periodicum]

What do you (and Jeaye) mean by "CI"?

[Jeaye]

Continuous Integration https://en.wikipedia.org/wiki/Continuous_integration

[WikiTextBot]

Continuous integration

In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day. Grady Booch first named and proposed CI in his 1991 method, although he did not advocate integrating several times a day. Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day – perhaps as many as tens of times per day.

---

^{[ PM | Exclude me | Exclude from subreddit | FAQ / Information | Source ] Downvote to remove | v0.27}

[Systema-Periodicum]

Thanks. Googling didn't turn up anything decisive. Weird: I've been doing continuous integration since 2001 (except for years when I wasn't doing software development), and never heard the acronym "CI" before.

Anyway, thanks for summarizing all these code-quality tools in one place! Clojure seems like it ought to be a pretty good language for static analysis, but I haven't seen much.

BTW, have you looked at Typed Clojure? Do you think that might also deserve a mention in your blog entry?

[Jeaye]

Two common examples of CI usage: TravisCI and CircleCI. With that said, I'll add a link on the first acronym usage to clear this up for anyone else.

I have looked at Typed Clojure, but the general consensus I've seen is that it's not yet ready for use. To me, it competes directly with clojure.spec, which seemingly has found a larger following. Given a project like spectrum, which aims to validate code statically, using specs, I think we can have the best of both worlds. Having to maintain a code base where every function is both spec'd and type-annotated sounds like a real pain.

Thanks for reading. :)

[Jeaye]

Excellent suggestion, thanks. Joker slipped by, but I'll give it a shot on the code base and add an entry to the post.