> Keep in mind that PanGui is designed to be language-agnostic and will be transpiled to many languages
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?
According to the FAQ the current implementation is in C#:
> 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?)
Apparently, they ask the users to provide the feedback for the model going forward once they release that? (I'm as confused as you are)
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.
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?