Maintain consistent styles for developers working across various editors

Part of a good software team&#x27;s toolbox.<p>Others:<p><a href="https:&#x2F;&#x2F;direnv.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;direnv.net&#x2F;</a> -- when you cd to a directory, do things like set variables.<p><a href="https:&#x2F;&#x2F;asdf-vm.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;asdf-vm.com&#x2F;</a> -- manage and use specific versions of software. Can work with direnv too!<p><a href="https:&#x2F;&#x2F;pre-commit.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pre-commit.com&#x2F;</a> -- git hooks that I personally found easier to manage than Husky.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;qoomon&#x2F;git-conventional-commits">https:&#x2F;&#x2F;github.com&#x2F;qoomon&#x2F;git-conventional-commits</a> -- enforce standard commit messages. Works with pre-commit!

What notable languages don&#x27;t have an opinionated auto-formatter? Like Python&#x2F;Black, Rust&#x2F;rustfmt, JS&#x2F;prettier, etc.

Here we are in the current year and we still i&#x2F;o source as raw form text. Personally, I’ve always hoped for standardized AST formats with comprehensive tooling, including source control. Many more problems vanish than are created with source as AST. For instance, this discussion.

I care whether experts can understand each others’ reviewed work, not whether they would use exactly the same amount of whitespace. Don’t reformat code you aren’t rewriting, and definitely not with a tool that doesn’t understand what a developer was communicating when he laid it out that way.