Till Schneidereit

I agree that this is a good direction. I also agree with @ajklein on making sure we don't treat the identified set of relevant VMs as immutable after stage 2...

> I think option 3 corresponds to the previously documented semantics in JS.md If I'm not misunderstanding something, that's not really the case: at most it delays resolving the promise...

This looks good to me as a solution to the problem at hand. However, I do wonder if it wouldn't make sense to be more strict about this: I could...

> @tschneidereit Did you see @linclark's explanation of the motivation for JSC's implementation strategy in webpack/webpack#6433 ? I did see that, yes. Your and @kmiller68's comments[1][2] in #741 led me...

Hey all👋🏻 I work on Wasmtime (I manage the Fastly team doing much of the development work), and represent the Bytecode Alliance, so I don't think it'd be appropriate to...

Microsoft's [Krustlet](https://github.com/deislabs/krustlet/) project might be a better approach, depending on details of your use case. If that doesn't work, note that we'll have Go bindings for Wasmtime soon, too.

@haraldh is this something you might be able to look into? Addressing this looks like it'd help make `--tcplisten` quite a bit more useful :)

> But is the idea to keep full implementations of proposals within the `wasmtime` tree (as it seems to be the case for `wasi-nn`), or just `wasmtime`-specific glue to more...

> And I am also not opposed to having a separate repo for the sake of re-use. To clarify, I most definitely don't want to say that we should somehow...

> It would be good for GC objects be "immutable prototype exotic objects" in JS, i.e. the prototype is fixed. I haven't followed the GC proposal all that closely in...