Just learned about scala-cli-- very cool-- and thinking about its possibilities for use in containers built off of scripts that non-devs could write: technically skilled people, currently writing elaborate and inscrutable bash scripts, but not up the traditional development workflow. The technical issues I have not been able to answer with regards to building containers including scala-cli are:
How do I nail down a JVM and Scala version-- which must be pulled on container build-- so that there is no possibility scala-cli will check for and download the latest release, service pack, or hotfix? For example corretto:11 will actually download 11.0.19-- which I can also specify, but actually there are a couple of sub-version numbers after that which you only see during the download-- again, I can specify those, but how do I know there won't be a subsequent hotfix or patch released for that version? Having containers which start many times per day each check and install new JVMs and scala versions every time-- taking many times the runtime of the actual script runtime is something I must guarantee will not occur.
Related to [1], can I disable checking for new scala and jvm versions completely?
How can I set a default JVM version and scala version without specifying it on the command-line?
Love scala, and would love it if there were current answers to these questions, but if not, I'll probably try to steer them towards groovy, which looks a lot more mature in its scripting environment and predictable in terms of the questions above.