Update API portability paragraph #152
Conversation
lukewagner
force-pushed
the
update-portable-api-para
branch
from
1ca4ed6
to
b584d71
Compare
| WebAssembly does not specify any APIs or syscalls, only an | ||
| [import mechanism](MVP.md#modules) where the set of available imports is defined | ||
| by the host environment. In a [Web](Web.md) environment, functionality is | ||
| accessed through the Web APIs defined by the [Web](https://whatwg.org) |
There was a problem hiding this comment.
Confusing to have two "Web" links lead to different places.
There was a problem hiding this comment.
Done, changed link to wikipedia "Open Web Platform" instead which gives a more comprehensive list anyhow.
|
IIUC one of @sunfishcode's objections was that this paragraph speaks to a different audience. Developers and implementors understand "portability" differently. To address this, maybe this paragraph could have its own sub-header? And the rest of Portability.md above also have a sub-header? |
lukewagner
force-pushed
the
update-portable-api-para
branch
from
3f8bdc7
to
ed9d5f6
Compare
|
That's a good suggestion @jfbastien. @sunfishcode any better? |
| @@ -4,6 +4,8 @@ WebAssembly's [binary format](BinaryEncoding.md) is designed to be executable | |||
| efficiently on a variety of operating systems and instruction set architectures, | |||
| [on the Web](Web.md) and [off the Web](NonWeb.md). | |||
|
|
|||
| ## Execution | |||
There was a problem hiding this comment.
How about "What platforms can WebAssembly run on?"
There was a problem hiding this comment.
How about "Assumptions for efficient execution"?
|
Yes, this is better. I think we can do more, but this is good for now. |
|
lgtm |
1 similar comment
|
lgtm |
|
Thanks, all. |
Update API portability paragraph
Capturing discussion from #146, though discussion can continue here. I made some further tweaks to clarify.