> Heterogeneity belongs in the type system, not in the runtime.

Is the intent that applications developed with this are compiled for target hardware on a machine-specific basis?

e.g. I define a machine file for my i5 and GTX3080, and another machine file for my gnarly datacenter rack, and the compiler compiles specifically for each?

That way the same source file is "provable" for different hardware configurations without relying on a runtime to be identicallu implemented?

Is there a backstory for this being named Vx? Seems a bit too close for comfort to the VxWorks OS, though there seems to be no connection.

Here we go again, why dont we try this again?

https://en.wikipedia.org/wiki/Transmeta

> Vx is the right language for the thing that must be correct and fast across ten kinds of silicon. It is not the right language for the thing you are still figuring out.

Sounds like a great language for an AI to use then :)

Why is it giving me Vlang vibe