clean-code-linters

Understood since Babbage: AofA is a scientific endeavor. • Start with a working program (algorithm implementation). • Develop mathematical model of its behavior. • Use the model to formulate hypotheses on resource usage. • Use the program to validate hypotheses. • Iterate on basis of insights gained. Knuth's methodology (slide 2) can be used to analyze programs we currently use, which have no obvious mathematical content. e.g. how do these fine code linters spot errors in your code? https://github.com/showcases/clean-code-linters but also does it manage your keystroke events an present information to you in a handy interface? algorithms are managing all of that

Hey everyone, creators of pre-commit here. Thought it was a good idea to clarify what makes our project different from most other systems. Even thought pre-commit is written in python we really don't care about the language that was used to write the hook/linter. If there's a good linter out there written in ruby, you should be able to use it and not have to install ruby/gems/etc. With pre-commit you just say you want scss-lint (https://github.com/causes/scss-lint) in your pre-commit config file and run pre-commit install. When you commit, pre-commit downloads, install scss-lint (without root) and runs the hook against the files you've changed. Currently we support ruby, node and python and we definitely want to expand the system to support linters in other languages like Go, C/C++ and PHP. We'd really like to support all of these linters