Stream: git-wasmtime

Topic: wasmtime / Issue #1835 Simple terminology for unfamiliar ...


view this post on Zulip Wasmtime GitHub notifications bot (Jun 06 2020 at 23:17):

rich-murphey commented on Issue #1835:

I restored the links, and and changed WASM to Wasm. I also used "Wasi" to be consistent.

My first reading of the intro also begged questions such as:
What is Wasm. What are it's limitations? (and given those:)
What is Wasm-bindgen?
What does WASI add?

So, i added a transition paragraph that touches on them and tries to tie them together for the next paragraph about Wasmtime.

Again simple terms are used, to try to make it easier for the reader. This understates the significance of the components.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 08 2020 at 22:20):

sunfishcode commented on Issue #1835:

"Wasm" is an abbreviation, while "WASI" is an acronym, and they really are written with different styles in practice today.

Is that too confusing? It's probably still possible to change "WASI" to "Wasi" at this point, if people feel strongly about it and there are no objections from the Subgroup.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 09 2020 at 01:04):

rich-murphey commented on Issue #1835:

WASI should be OK since it's following a consistent convention. If a definition is there, it shouldn't create confusion.

BTW, I'm not expecting you'll necessarily use any proposed words as is, and you all are welcome to excerpt or change anything I suggest as needed. I'm a somewhat recent convert to rust, and I what I hope to suggest are clarity for new users who are bootstrapping themselves, from less background, which is where I am coming from. It's challenging to write for two very different groups: new users and internals developers, not just for the desire for technical clarity, but conventions. So this is understandable.

view this post on Zulip Wasmtime GitHub notifications bot (Jun 15 2020 at 00:46):

rich-murphey commented on Issue #1835:

I've tried to clarify that high-level languages must be compiled to Wasm prior to loading using Wasmtime. Here's some recent discussion where confusion about this arose on reddit.

Embeddable Lua-like scripting for both native and browser (Wasm)?

view this post on Zulip Wasmtime GitHub notifications bot (Jul 10 2020 at 06:20):

kubkon commented on Issue #1835:

"Wasm" is an abbreviation, while "WASI" is an acronym, and they really are written with different styles in practice today.

Is that too confusing? It's probably still possible to change "WASI" to "Wasi" at this point, if people feel strongly about it and there are no objections from the Subgroup.

FWIW, I believe it should always stay as "WASI" since as you guys pointed out, it's an acronym after all.


Last updated: Dec 23 2024 at 12:05 UTC