Post
The obvious solution to all this mess is to make libraries ship source code instead of compiled blobs of whatever.
Maybe there is a reason for this absurd choice that they don't even consider changing, but I can't see it.
Overall we expect this problem will sort itself out going forward: both by sbt itself improving over time, and by projects choosing other tools that provide great alternatives.
0
0
0
0
I think the underlying reasoning is Scala trying very hard to fit into the Java/JVM ecosystem, i.e., Maven Central and JAR files are the way of the land.
Also... Scala compilation times. Things are improving, but start compiling too many dependencies in your average enterprise project, and we’ll be right back to this: 3d.xkcd.com/303
To be fair, things aren't anywhere as bad in other JVM languages like Clojure and Kotlin (despite not exactly loving Gradle as a build tool either). Scala problem was mostly self-inflicted when the community embraced sbt.
Also, sharing and adding the #scala hashtag so I don’t feel too hypocritical after all my pep talks about the discoverability of niche content on Anostr. 🤣
0
0
0
0