WebAssembly / WebAssembly/component-model
[Question] Proposal for WebAPI calls without JS glue
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
I am lost with current proposals. As I know Interface types proposal was created for direct WebAPI calls from WebAssembly. (Answer from Emscripten team https://github.com/emscripten-core/emscripten/issues/15710#issuecomment-987263141 )
But it was renamed to component model and slowed down? How WebAssembly WebGL applications supposed to be faster than pure JS?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the current component model proposals and the linked Emscripten discussion about Interface Types. Clarify the relationship between Interface Types and the component model, then establish whether direct Web API and WebGL calls without JavaScript glue are supported and what performance expectations are justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100