It is Friday and I'm tired, so maybe I need another re-read.
It is Friday and I'm tired, so maybe I need another re-read.
It’s also hyper strict, which is ok for a new project, but won’t play nicely with any legacy app.
Though I’m surprised DHH didn’t write his own RuboCop from scratch.
> That’s why we’re shipping a default linter, cleverly called RuboCop, in the next version of Rails. Not such that I, or anyone, can mandate what style your codebase ought to be written in, but such that you can find and enforce your own.
So every new Rails project has preset of linting style, which defaults to whatever the Rails team chose, but the point is that people are free to adjust the config file to whatever they prefer. So the same style is applied through the codebase.
His point is actually that linters lacking configuration are draconian.
> Some languages, like Go, have a built-in linter, which applies a universal style that’s been set by the language designers. That’s the most totalitarian approach.
I'd doubt it's the "built-in" aspect; it sounds quite a bit like it's the "universal style" that the author doesn't like.
This is from DHH, the Rails guy.