Jon Pretty

Can you remind me what they were, just to remind me whether I addressed them, or just promptly forgot...?

Plugins. You addressed them very explicitly by stating they were never going to be a part of Fury :)

What kind of plugins do you have in mind?

Static code analysis, code formatting, linters, ... all the things that I like not to think about but are outside of Fury’s scope. I understand the reasoning, but it’s important to me to need one tool, not n, to be able to compile and build my projects.

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