linter

The problem is that without a linter there's no punishment for missing semicolons.

In various ways the linter is more strict than pep8.

Yes: Check in a unittest that runs your linter, and check in the config as well (eg jshintrc).

Really, every JS developer should be using a linter and tweak it to fit their coding preferences.

Basically whenever we notice codestyle discussion in PRs repeating a custom linter will come to establish convention (/rule).

Atom editor, for example, has tons of linter plug-ins, as well as other helpful things, to ease creating code.

Most linters let you trivially change this line length in a way which either affects the linter permanently, or on a per-project basis.

So really the argument should be that everyone should use a linter.

Instead, ship an extensible, plugin-based linter with your language's toolchain (e.g.

I've recently started to integrate a linter to all of my tool chains, and I don't want to live without one.

Using a linter with Emacs made it a non-issue; I get a warning in my editor immediately when I miss one.

An indentation mistake - something that can be caught trivially by a linter - is not significantly different by nature than any other single-character mistake, like an incorrect constant or misspelled identifier (harder to find with a linter).

To paint these tools with an overfly broad brush, they linter-like in that they perform shallow intra-procedural analysis to identify common bug patterns (e.g., if (x!= null) { y = x.f } z = x.f // possible NPE; x was previously checked for null or foo(String s) { if ("x" == s) // oops, should use.equals() for Java String comparison.

If you're looking for a full-featured IDE, I don't think you need to look any further than PyCharm, however, Sublime with it's PEP 8 Linter, and CodeIntel plugins will give you a lighter-weight yet effective solution.