[00:20] SketchCow: how can it need more memory? they only ever had 4MB, and then only if you got the top model [00:20] anyway, I tried doubling it and it didn't boot [00:23] *** DFJustin has joined #jsmess [00:24] *** DFJustin has quit IRC (Remote host closed the connection) [00:26] *** DFJustin has joined #jsmess [00:54] oops [00:54] SketchCow: I just got your email [01:06] SketchCow: uploaded loader.js in the loaderlab with a fix [01:06] I think the cause was a change to browserfs, not the loader itself [01:06] either way I should have tested it better [01:37] *** phe has quit IRC (Quit: Leaving) [08:02] *** zino has joined #jsmess [08:08] *** db48x has quit IRC (Read error: Connection reset by peer) [08:08] *** db48x has joined #jsmess [10:17] *** phe has joined #jsmess [13:07] *** zino has quit IRC (Read error: Connection reset by peer) [17:13] *** db48x has quit IRC (west.us.hub irc.Prison.NET) [20:30] *** db48x has joined #jsmess [21:22] so uh [21:22] does emularity serve up a wasm build if your browser supports it yet [21:23] good question [21:24] I'm doing it somewhat manually in my stuff [21:24] I basically preload the .wasm file with an XHR, then jam it into the Module.wasmBinary or whatever the property is called [21:24] I think db48x did some work to make wasm stuff better integrated though [21:25] if I have a .js and a .wasm that emscripten made, will I be able to integrate that with emularity or do I need to do things on the emscripten side first [21:25] you can, yes [21:25] I'll want a .zip filesystem like we have, not a weird data bundle [21:25] okay [21:26] here lemme show you what I do, then maybe db48x will come along and say "no you n00b, just pass it as an argument *rollseyes*" [21:28] https://pastebin.com/59cRLGHA [21:42] bai: are just loading the wasm no matter what? [21:42] you're not testing for support first? [23:41] yeah heh [23:41] haven't gotten around to doing an autodetect thing yet [23:51] I don't see anything in emularity that suggests wasm loading is in there [23:51] I also don't see a reasonable way to feature detect wasm? [23:51] just closed issues and postulating on the web site [23:52] is the initial wasm feature set consistent between ff and chrome that you can just detect the mimetype support for it of all things [23:52] they're talking about hypothetical feature detection within wasm, like different instructions being supported