Jon Pretty

Sbt, for all it does weird, is the one tool you need. You don’t even need scala. It takes minutes to get going. Terribly convenient when onboarding new devs, setting up a new box, starting a workshop with 30 people not one of which took the time to go through the prerequisites

I'm not sure minutes is acceptable in general. I still see a clear distinction between development (handled by the IDE, or an ad-hoc set of composable tools in my case) and the build.

build is a team common and development is a developer local. Each developer should be able to use its own formatting

Having wasted literal days to whitespace in code review, I disagree with this statement. I see where you’re coming from, mind, and used to agree, but it turns out having the team follow an agreed on code style and automate it is much less painful than the alternative

We put it in the build because it's practical, not because it have to be.

Well. I put it in the build because there currently is no reasonable alternative that I know of. Same goes for headers ((C) stuff in the corporate world), for example. But sure, if there were other alternatives, I’d certainly consider moving this stuff away from the build

Incidentally, I've become quite disappointed with the whole idea of source-code formatting. I'm planning to rip it out of the Fury build as soon as other things stop being much higher priorities...

I hated the very idea with a passion, up until the time I started working in a team of people who could not agree among themselves (and, far worse, agree that I was right) about various formatting rules and would waste hours arguing about it during code reviews.