isd changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | This channel is logged at: https://freenode.irclog.whitequark.org/sandstorm/
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 260 seconds]
_whitelogger has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 265 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 260 seconds]
jryans has quit [Ping timeout: 268 seconds]
jryans has joined #sandstorm
<jimpick> I've been playing around a lot this week with WebAssembly and WASI ... I think it would be a cool experiment to take the C++ Raw API example app and compile that as a WASM file using the WASI system calls, and then have a little shim app to run it and connect it to file descriptor 3 + map the fs system calls to /var ... lots of options for creating the shim app (maybe Deno?)
<jimpick> the neat thing is that you could just swap out the WASM file with a different one and have a completely different app
<jimpick> (plus modify the package capnp file and republish)
<jimpick> also, it might be possible to run the app entirely client-side, offline, in a service worker in a web browser, and sync the filesystem
<JacobWeisz[m]> I usually prefer stuff run on the server, personally, but especially for porting compatibility, I imagine it'd be nice if more client side apps could work with Sandstorm.
<JacobWeisz[m]> Bear in mind offline operation would almost certainly require webkeys or offer templates in some form, as the actual subdomain a grain is on changes every time the grain is opened.
<jimpick> Yeah, offline would be tricky. But that's sort of my specialty. :-)
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm