clojure-style-guide VS CppCoreGuidelines

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

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.

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.

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).

Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.

It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-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

Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.