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
Crazy idea, but why not. The current problem is that RR supports only plugins which are written in Golang. What if we go beyond and think about WIT (Wasm) and wasm-based-modules. Having a good interface written in WIT (https://component-model.bytecodealliance.org/design/wit.html) we basically would be able to connect plugins written in any language which supports WASM and WIT. The good example is how Zed editor handles extensions: blog. In the same way, we'd be able to connect any extension to RR.
The issue is, that in Go, unlike Rust, WIT is not fully supported yet.
Having such extensions, we'd be able to have middleware in PHP for example, or better gRPC streaming integration an so on.
The text was updated successfully, but these errors were encountered:
Plugin
None
I have an idea!
Crazy idea, but why not. The current problem is that RR supports only plugins which are written in Golang. What if we go beyond and think about WIT (Wasm) and wasm-based-modules. Having a good interface written in WIT (https://component-model.bytecodealliance.org/design/wit.html) we basically would be able to connect plugins written in any language which supports WASM and WIT. The good example is how
Zed
editor handles extensions: blog. In the same way, we'd be able to connect any extension to RR.The issue is, that in Go, unlike Rust, WIT is not fully supported yet.
Having such extensions, we'd be able to have middleware in PHP for example, or better gRPC streaming integration an so on.
The text was updated successfully, but these errors were encountered: