Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WASM runner #106

Open
gedw99 opened this issue Feb 24, 2024 · 1 comment
Open

WASM runner #106

gedw99 opened this issue Feb 24, 2024 · 1 comment

Comments

@gedw99
Copy link

gedw99 commented Feb 24, 2024

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 ..

@progrium
Copy link
Contributor

I don't quite follow but would love you to join the discord and tell us more about how you're wanting to use Cue and WANIX!

Btw, is this issue actionable or can I close it? Or would you rather move to discussions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants