Solutionism SBT has an extremely non trivial start up, and spin up time. Even using a client JVM (more aggressive JITing). You need to know the hot paths, befo

Solutionism SBT has an extremely non trivial start up, and spin up time. Even using a client JVM (more aggressive JITing). You need to know the hot paths, before you can JIT them. And as a CLI tool, by the time you start optimizing your hot paths your tool will exit. Now C/C++/Rust/Go compilers can be slow, when your compiling A LOT of crap. But the tools will spring to action extremely quickly on smaller jobs. And while build farm services exist, they’re useful for handling instances where you have GiB’s of sources, or sources which expand into GiB’s of input. Overall a generic build server API sounds good, but this doesn’t solve the core problem Scala has which can be summarized by running: sbt -version and seeing it take 1-2 minutes to display an error message.