Port to Scala, compiled with GraalVM's native-image?

[dwijnand]

I'm not sure if I'll do it, but I'm wondering: what if this were ported to Scala, set up to compile with GraalVM's native-image? Pros:

1. it wouldn't have additional runtime dependency, like hub/jq/cs (i.e. Fast+cleanly fail on missing: cs, hub or jq #1)
2. it would fix the Windows/BAT support issue (Windows/BAT support #4), except for the fact that it needs to be compiled on Windows
3. could expose the resolved scala version in all cases (i.e. fully resolve Expose internals to support returning the resolved scala version #17)
4. easier to test

Cons:

1. less introspectable/auditable
2. harder to customize
3. more complicated setup / harder to distribute
4. introduces a build time

So, more generally: how would you feel about this change? Would you feel as comfortable using and depending on scala-runners if this went through?

[SethTisue]

Would you feel as comfortable using and depending on scala-runners if this went through?

I would. Especially since it's still early and there isn't yet much of an existing userbase for this.

And I think it's important for Scala that this becomes a workable way to make command-line things, so I think it's a good use of our team's time to dogfood that.