What does HackerNews think of clojure-style-guide?

Using Clojure in the command line with Babashka | Sep 2020

I think the closest we have to a "agreed upon style guide" that is written down, is https://github.com/bbatsov/clojure-style-guide

State of Clojure 2016 – Results and Analysis | Feb 2017

Expand Context ↕

I couldn't get Parinfer to work with Vim. There's a port but it's buggy.

But the Neovim port is great. Installation requires a little patience, but it works well.

In any case, one should read the Clojure style guide on GitHub [0] and get used to writing code in normal editing modes first. Then move on to Parinfer or Paredit once you feel the shape of the code and sense why it's like that.

[0]https://github.com/bbatsov/clojure-style-guide

How to Name Clojure Functions | Jan 2016

I suspect I overuse the x->y naming convention for functions that take an x and return a y. Esspecially when there is only one kind of thing that that function ever takes.

So instead of:

    (-> x x->y y->z)

I'd have:

    (-> x y z)

Makes sense. Thanks for the post Stu!

P.S. Another useful tome about naming functions is: https://github.com/bbatsov/clojure-style-guide

Ask HN: Good Clojure codebases to read? | Jul 2015

If you're trying to build a website I really learned a lot by looking at Xavi's noir-auth-app. https://github.com/xavi/noir-auth-app

Not really a code-base, but the clojure style guide is a nice glance over.. https://github.com/bbatsov/clojure-style-guide

Ask HN: How do I get my team to write better code? | Nov 2014

Point them to some coding guidelines for the language/platform which you're developing.

For Clojure development: https://github.com/bbatsov/clojure-style-guide

For Scala: https://github.com/alexandru/scala-best-practices/ or http://docs.scala-lang.org/style/

Lisp Is Too Powerful | Apr 2013

Expand Context ↕

Eclipse was just an example. There is going to be a niche for massive projects.

That niche and Java deserve each other.

There's also going to be a niche for projects that live for a very, very long time and thus are touched by a massive number of programmers

There's some overlap, but more than anything, this niche is just the one that really needs a solid unit test suite and documentation. There are excellent unit test framework packages for Ruby, and high unit test coverage is very much a part of Ruby programming culture. The documentation quality for open source Ruby projects also seems very high overall.

Community style/idiom standardization in Ruby and Node is probably a function of having a constellation of very active, popular, and often interdependent open source projects in each. When you're writing Rails gems that depend on other Rails gems, everyone is reading everyone's code, so agreeing on some style guidelines as a community makes everyone's life much easier.

I think that if someone wrote a very popular open source project (analogous to Rails) in a Lisp dialect, we might see the same thing start to evolve. And I think we're already starting to see it happening with Clojure. There's a Clojure Style Guide that's gone up on Github very recently: https://github.com/bbatsov/clojure-style-guide