awesome-guidelines
clojure-style-guide
| awesome-guidelines | clojure-style-guide | |
|---|---|---|
| 3 | 15 | |
| 9,553 | 3,974 | |
| - | - | |
| 5.4 | 2.9 | |
| about 1 month ago | 3 months ago | |
| JavaScript | ||
| Creative Commons Zero v1.0 Universal | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-guidelines
clojure-style-guide
-
XML is better than YAML
Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals
Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):
{:a 1 -
How to be more idiomatic?
As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.
-
What makes Clojure better than X for you?
Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.
-
Poignant perspective I found about Clojure's community in r/ExperiencedDevs
Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).
-
How to learn Clojure idioms?
Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.
-
4-space indents?
It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide
-
Clojure Coding Guide
The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232
-
Wrote one of my first clojure programs (tic-tac-toe). Any constructive criticism would be greatly appreciated.
Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw
- Want to get into closure, but struck at practice
- [clojure-noob][code-review]I've written my first piece of code in clojure, can you guys review it ?
What are some alternatives?
betterscan-ce - Code Scanning/SAST/Static Analysis/Linting using many tools/Scanners + OpenAI GPT with One Report (Code, IaC) - Betterscan Community Edition (CE)
prettier - Prettier is an opinionated code formatter.
husky - Git hooks made easy 🐶 woof!
Crafting Interpreters - Repository for the book "Crafting Interpreters"
every-programmer-should-know - A collection of (mostly) technical things every software developer should know about
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
30-days-of-elixir - A walk through the Elixir language in 30 exercises.
Kalman-and-Bayesian-Filters-in-Python - Kalman Filter book using Jupyter Notebook. Focuses on building intuition and experience, not formal proofs. Includes Kalman filters,extended Kalman filters, unscented Kalman filters, particle filters, and more. All exercises include solutions.
awesome-ux-design-styles - Curated list of UX styleguides and design systems
papers-we-love - Papers from the computer science community to read and discuss.