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
As we move towards 'wasm-first development', I'm wondering if gloo-worker could have a NoOp mode that would work on desktop. I.e. skip the serialisation and just pass the messages in-process. The rational is that once you've got things working for the web, you don't really want to have to re-architect your app to work on desktop. Ideally one could just flip a feature and gloo-worker go into no-op mode and run it all in process. Presumably in this mode it would be able to ditch most dependencies...?
We could create a not-gloo-worker crate and rename it so that the types matched, but that seems less elegant.
The text was updated successfully, but these errors were encountered:
As we move towards 'wasm-first development', I'm wondering if gloo-worker could have a NoOp mode that would work on desktop. I.e. skip the serialisation and just pass the messages in-process. The rational is that once you've got things working for the web, you don't really want to have to re-architect your app to work on desktop. Ideally one could just flip a feature and gloo-worker go into no-op mode and run it all in process. Presumably in this mode it would be able to ditch most dependencies...?
We could create a not-gloo-worker crate and rename it so that the types matched, but that seems less elegant.
The text was updated successfully, but these errors were encountered: