better-monadic-for VS sbt-assembly

I agree with that one - but isn't that already fixed by https://github.com/oleg-py/better-monadic-for ?

Better Monadic For to make various improvements to for-comprehensions.

There is https://github.com/oleg-py/better-monadic-for/ but it's still not ideal. And Scala 3 comes with some improvements, but still leaves a lot to be deserved.

sbt-assembly is still my go-to. So what I'd prefer is the combination of sbt-assembly (to build my .jar that I can just java -jar anytime I want) and sbt-jib (to construct my OCI image including my assembly .jar for deployment in some container orchestration environment).

You may also use sbt-assembly to produce an uber JAR that embeds the Scala stdlib together with your code, which means that now for running your program you only need a JRE like java -jar app-assembly.jar. This option is great because now if you start adding dependencies to your project those are also included in this massive JAR.

Sbt-assembly defaults to silently concatenating configs. But even if it didn't, the configs wouldn't be in any particular order when resolving.

Ticket of record is https://github.com/sbt/sbt-assembly/issues/391

With the sbt-assembly plugin you can create JAR-files with all of its dependencies (fat JARs). sbt assembly creates this target/scala-2.12/apply-at-vdb-assembly-0.1.0-SNAPSHOT.jar which has a size of around 42MB: