prettier is hipster gcc

Prettier is the worst approach to code quality I've ever seen, even worse than neglect, because it specifies everything and ignores the fact that the same snippet can have various meanings and the ideal formatting for them is different. If you configure every last ESLint rule to work in a particular way you can achieve a very similar outcome in terms of readability and the difference will be that slightest freedom which enables devs to express their intent rather than subordinating formatting to syntax entirely.

Okay, maybe prettier isn't worse than completely ignoring code quality, but it's still a terrible approach.

Auto code formatters are for normies that write code because they have to to make money. No craftsman would ever let a computer reformat their carefully crafted code

#itishowitis

@12bitfloat Okay but consider: the programmer's ultimate goal is to save time and code automation is the exponential form of that.

it took me a quick moment to see what could a code formatter that at most has syntax parsing have anything to do with a compiler. <---- and that is all I could get. Someone help a dumb homie out to understand?

@lbfalvy well, unless when you have to fight with it

@vintprox Bad tools are bad, that has little to do with the problem they're trying to solve.