#Go is under corporate control and has a weird obsession with static linking if I'm not mistaken, though this may be fine for certain applications... In fact, in Java you'll often create a "fat JAR" that contains all dependencies so... Still, something is off about Go's vibes. Yeah, I'm vibe-checking programming languages now. Sue me.
@TobiasFrech Apparently Graal is written in Java. Do you happen to know what its bootstrap story is? As far as I know, even OpenJDK is notoriously difficult to bootstrap from scratch. This makes me worried about supply chain attacks (not sure that's the right term).
@taylan OpenJDK is the upstream source project. There are many (!) distributions, which provide certified Java runtimes. For the Adoptium project I do know they care a lot about reproducible builds, SBOMs and supply chain in general. As do others! I do not know what the "building from scratch" story for GraalVM is. But you can end up with native build of your Java program, which does not need a runtime environment anymore. Quarkus is a mostly RedHat funded project. As such it is also OSS.
Maybe #OCaml is the language I want. You can create standalone binaries with it, right?
Hmm, looks like it's kind of like C by default, meaning you would need shared libraries present on the target system, and unlike C there's no direct support for linking everything statically, though it's possible apparently:
I should write some kind of application in a bunch of different programming languages to get a proper taste for them. Hmm, maybe an IRC bot.
Writing an IRC bot means you get to see whether the language can easily be used for "real-world" use-cases (TCP/IP networking and filesystem access being typical litmus tests IMO), it lets you see how well you can mangle strings and bytes and work with Unicode in the language, and you can work with a couple data structures like to make the bot remember things. You can make it extensible with additional feature modules to test how well things compose in the language.