ooof
so, anyhow, long story short, because dev.coracle.social ate my last attempt at posting because i accidentally pressed something that changed context
the javascript runtime for #WASM on #golang does not have support for writing to files, or filesystem path mapping or anything
there is polyfills to enable this with wasm code but to make it transparently work with Go code that is using the os library filesystem access code is probably a non starter at this point unless i'm building it from scratch and can abstract all of that stuff, anything that uses os library direct, nope, would require a fork of the go stdlib to achieve that
so, for now, making my #realy run inside a browser would mean heavily modifying badger to be able to work with the hobbled js/wasm runtime filesystem access correctly
nobody has done it yet, but on the other hand, badger now has fragments of code involving supporting the js platform which means they probably are going to eventually do this, maybe next year, maybe the Go project has work in progress to enable filesystem access in the WASM builds
for now, only with WASI (eg wasmzero) and only under nodejs, not in a browser
so in practise what this means is that i could run #realy in a browser, if i created a network enabled event store and was able to tunnel access to it through a public routeable address
that's a lot of rigmerole
i'm going to stop this madness now, nice idea, but basically not gonna happen without me writing a whole frickin database that is hip to this silly platform
Showing page 1 of
1 pages
