2 ms·
> My tip: embrace the toughest linting rules your team can stand. How good is the Flow type checker, vs ESLint or the Google closure compiler? While I don't d
by dahart 10y ago
> My tip: embrace the toughest linting rules your team can stand.
How good is the Flow type checker, vs ESLint or the Google closure compiler?
While I don't disagree with anything the author said, most of the time I feel like ESLint is just a huge nag about white space. It's defaults have a bunch of rules that in my opinion enforce style without improving code safety at all, despite what the intro docs say. Someone I work with read some opinions like this one and got the idea that ESLint represents correct JS standards, and won't allow the white space rules to be relaxed. I'm stuck being forced to put a space after my comment characters, and not being able to line up blocks of repetitive code. It is admittedly nice to not have any white space style arguments. OTOH, I never really had white space arguments before, and the difference in both friendliness and code safety between using ESLint and the Google closure compiler is huge.