alt Hacker NewsI think the target application is writing the same algorithm in multiple places with a guarantee that the logic will be based on a single source of truth. Not unlike Protocol Buffers work to standardize data layout across platforms.
It still feels overcomplicated compared to the standard solution of writing a library in a compiled language you like, exposing a C ABI compatible interface, and hooking it up to any language that can work with that (i.e. any language).
Replies
C code called from other languages has terrible ergonomics. Writing it sucks, debugging it sucks, maintaining it sucks.
I don't know if fusion is the solution, but I know C isn't.
You don't need a C ABI here because the language could in theory generate both the library and the cross language bindings, the underlying mechanism then becomes a mere implementation detail.
I feel like there is a huge missed opportunity that Fusion Lang overlooked.
> writing the same algorithm in multiple places with
This seems for me to be reasonable. Like for a video game with server written in Go/C++/Rust and client written in C#/Javascript, where the same calculations should be done on both sides.