Till Schneidereit

The issue here is that ComponentizeJS now uses a version of StarlingMonkey that uses wasi-0.2.3 bindings. Ideally ComponentizeJS would be able to handle this situation the same way a runtime...

I _think_ this should be fixed with #185. I'm not 100% sure though, as there might be other places where we should check for semver compatible prefixes, but check exact...

I just realized that this is covered by a test since #1444. @scoopr and @emilio, am I missing a reason for why this behavior is indeed correct? I see no...

Thank you for this writeup! ❤️ This all looks great and makes sense to me, with one exception: I think it might make sense to start with something a bit...

> They can return an error instead of compiling anything, but we could always layer the `compile` interface on top to extend this into a new world too. The key...

What I'm trying to convey is that I think these should be different interfaces, so they can be included in different worlds. Worlds that don't include the "compile some bytes...

> For wasi-libc specifically a native-like experience would be a `dlopen` function that interprets the input string as a file path. It would probe for the file, read the contents,...

The thing that seems very important to me is that the primitive used by libc should not require being able to acquire the wasm bytes to get a module ref....

To expand on my reasoning here: For environments that want to/can only handle precompiled binaries, we really don't want to require the `.wasm` file to be available, and we certainly...

I agree that JIT compilation is important—it'll not be supported in all environments though, so I think it should not be part of the default way to support `dlopen`. What...