You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whole reason for this is so hat CueLang can be used as a language running through wanix. So you can do real time programming
I think I can also get it running on cloud flare . Running golang on cloud flare as WASM just requires a few changes to golang code.
passing CueLang as “ ops “ streams through wanix would open up the possibility of react programming. Cue does not allow mutations on the schema . It’s part of its fundamental philosophy so it adheres to a schema evolution policy that new code must not break old code. So a recompile at runtime all the way down the tree is needed ..
The text was updated successfully, but these errors were encountered:
I think there was some discussion about using wazero or a different WASM runtime .
Not sure which way people are leaning on this but I just wanted to add some of my thoughts on this.
I am playing around with using CueLang with wanix and the CueLang WASM runtime uses wazero .
https://github.com/cue-lang/cue/blob/v0.7.1/cue/interpreter/wasm/abi_c.go
The whole reason for this is so hat CueLang can be used as a language running through wanix. So you can do real time programming
I think I can also get it running on cloud flare . Running golang on cloud flare as WASM just requires a few changes to golang code.
passing CueLang as “ ops “ streams through wanix would open up the possibility of react programming. Cue does not allow mutations on the schema . It’s part of its fundamental philosophy so it adheres to a schema evolution policy that new code must not break old code. So a recompile at runtime all the way down the tree is needed ..
The text was updated successfully, but these errors were encountered: