Skip to content

"Just" an API vs requiring upstream features #553

Open
@penzn

Description

@penzn

I think #549 and WebAssembly/wasi-threads#48, present a qualitative change, however minor, from 'just an imported API' to where WASI would need some core features. I didn't think this should've prevented #549 from going forward, but I think it would be good to start a discussion on this.

In my view WASI is taking these dependencies on upstream standard, we can debate whether one is causing the other or they are independent:

  • Component Model itself is a core proposal, at least far as APIs are concerned
  • Certain features must be implemented in core wasm instead of APIs, as we have seen with threads

This is concerning, because so far there is not much traction in supporting component model or other core features mandated by the current WASI direction in browsers (treads draft hasn't been presented yet, for example). This would create divergence between WASI and 'stock' web environment, while more convergence would be preferrable in my opinion, as there are currently some challenges with running the same code both ways.

Originally posted by @penzn in #549 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions