sbt-crossproject VS Simulacrum

SBT. It's not because of the pseudo-scala config language, that looks especially alien next to braceless Scala 3 code. Or the weird symbolic operators. The big problem is correctness; in almost every project I've had to use spray-resolver because I've encountered weird bugs because SBT reuses the same dirty JVM. I really thing Drip would help here. I'll keep using SBT because it has the best Scala ecosystem support and great plugins like sbt-crossproject. It would also be great to be able to write build.sbt files in modern, regular Scala.

The Cats ecosystem offers mature named abstractions providing algebraic laws virtually identical to those offered by Haskell and PureScript and that have stood the test of time, at the cost of relying on a "design pattern" approach to implementation you have to squint a bit to see ("typeclasses" based on higher-kinded types and implicit arguments) and that sometimes doesn't play nicely with Scala's colored local type inference. The selling point of this, coupled with parametricity ("tagless-final style"), is the ability to reason algebraically about your code.