4 ms·
Native binary is not a clear statement. On Android is CPU-native, really native? Or is CLR the future of Windows? CPU-native does not mean much. It means that y
by hawski 8y ago
Native binary is not a clear statement. On Android is CPU-native, really native? Or is CLR the future of Windows? CPU-native does not mean much. It means that you have a competition of almost all languages, that have head start and better tooling.
"Is FFI cheap on all interesting platforms?" is a better question, than "Does it compile to CPU-native binary on all interesting platforms?". In this space you only kinda get some JVM languages, but on Windows you would have to do something more special. Scheme to some extent. Also Haxe.
If you don't care about it you can read the rest of this thread with all other favorite languages. I for one cheer for Myrddin, Pony and Zig.
I was thinking lately about an imperative language, that would be easily compiled to other first class languages. To serve as a cross-platform core of application. It would be quite limited - for example no heap allocations. Something maybe akin to Google's Wuffs language. Just an idea on the one edge of the problem.