Okay, there’s a few things you plausibly need transpilation for (like web), but mostly shouldn’t language-agnostic not mean “transpiled to a whole bunch of target languages”, but instead just mean library with idiomatic clients for a bunch of different languages, with transpilation for a small number of platforms where the usable languages are limited?
> Second, you might ask: why write it in C# first?
I interpret their strategy as sticking to a subset of C# which works with NativeAOT -- for compilation to native libraries -- while also working in the .NET runtimes shipped with Godot and Unity (is IL2CPP still around?)
The API looks really good however, especially if it's NativeAOT-compatible and works in a way that is reminiscent of Rust's egui, something which .NET deserves to have. But that's an IF we will need to see realized.