| ▲ | overfeed 9 hours ago | ||||||||||||||||
>> ...there is no debate... > ...And so many languages have an opinionated formatter these days The crux of gp's post is for Go, there is no debate as 'go fmt' is the only one that matters. Black is great, but some people prefer Ruff, leading to ...debates about which formatter the team/org should use. Go's batteries-included philosophy makes those discussions moot on so many levels beyond formatting. | |||||||||||||||||
| ▲ | maleldil an hour ago | parent | next [-] | ||||||||||||||||
Bad example. Ruff's formatter has the same style as Black. It's documented as a "drop-in replacement". The difference is mostly performance. In any case, that's a single decision the project lead takes once. | |||||||||||||||||
| ▲ | ciupicri 6 hours ago | parent | prev [-] | ||||||||||||||||
As if projects haven't used to have a coding style. What's so hard in saying that code should be formatted with Black, yapf, ruff etc, beats me. | |||||||||||||||||
| |||||||||||||||||