Thanks for the link. It's easy to dismiss Oracle technologies (because ... Oracle), but we should consider the implications. As a reminder, Oracle won the Jav

Thanks for the link. It's easy to dismiss Oracle technologies (because ... Oracle), but we should consider the implications. As a reminder, Oracle won the Java enterprise database market for a decade by embedding Java in the VM, and optimizing it internally. This stack (GraalVM producing OCI-functions-compatible functions running on their function container) is similar: it uses (relatively) open standards, but the GraalOS container can optimize the GraalVM code for a given processor (or even memory). I doubt they've done much publicly other than cobble the stack together, but it tracks the product-evolution razors-and-blades approach that JavaSoft started in 1998: the GraalVM AOT can be free, and running on the cloud is possible (via OCI-fn containers), but cloud optimization can cost. So they can build share using GraalVM that they can harvest in GraalOS. And functions as a server depend implicitly on data services running in the cloud, i.e., databases. Migrating use-cases there builds their legacy business. That's the pitch, I think. The army of Java is never more than 1-3 years behind every sophisticated new approach :)