Stream: git-wasmtime

Topic: wasmtime / Issue #2435 Roadmap of wasmtime

Wasmtime GitHub notifications bot (Nov 20 2020 at 10:41):

daubaris opened Issue #2435:

Feature

Adding a roadmap of wasmtime.

Benefit

I think most of the users and yet-to-be users would be interested in seeing what is the future of the project. Similarly, a roadmap could potentially reveal if the project is focused on achieving some specific major goals, such as specific platform support. Moreover, a clear list, for example, for a release could attract more contributors as it would be clear what needs to be done.

At the present moment, it is certainly vague what needs to be improved (besides checking issues) and what new features could be developed (besides new proposals).

Implementation

It could be added as a new document to the existing docs folder.

Wasmtime GitHub notifications bot (Nov 20 2020 at 10:43):

daubaris edited Issue #2435:

Feature

Adding a roadmap of wasmtime.

Benefit

I think most of the users and yet-to-be users would be interested in seeing what is the future of the project. Similarly, a roadmap could potentially reveal if the project is focused on achieving some specific major goals, such as specific platform support. Moreover, a clear list, for example, for a release could attract more contributors as it would be clear what needs to be done.

At the present moment, it is certainly vague what needs to be improved (besides checking issues) and what new features could be developed (besides new proposals) and what are the overall goals.

Implementation

It could be added as a new document to the existing docs folder.

Wasmtime GitHub notifications bot (Nov 20 2020 at 10:44):

daubaris edited Issue #2435:

Feature

Adding a roadmap of wasmtime.

Benefit

I think most of the users and yet-to-be users would be interested in seeing what is the future of the project. Similarly, a roadmap could potentially reveal if the project is focused on achieving some specific major goals, such as specific platform support. Moreover, a clear list, for example, for a release could attract more contributors as it would be clear what needs to be done.

At the present moment, it is certainly vague what needs to be improved (besides checking issues), what new features could be developed (besides new proposals) and what are the overall goals.

Implementation

It could be added as a new document to the existing docs folder.

Wasmtime GitHub notifications bot (Dec 03 2020 at 20:25):

michaelvoronov commented on Issue #2435:

Heavily +1, we are especially interested in interface types MVP implementation in Wasmtime. There are some proposals (like module linking and let from function reference) that should be supported first, and module linking has the nice tracking issue with all neccessary information, but absence of global roadmap doesn't allow us to make a long-term plans.

Wasmtime GitHub notifications bot (Dec 03 2020 at 20:27):

michaelvoronov edited a comment on Issue #2435:

Heavily +1, we are especially interested in interface types MVP implementation in Wasmtime. There are some proposals (such as module linking and let from function reference) that should be supported first, and module linking has the nice tracking issue with all neccessary information, but absence of global roadmap doesn't allow us to make a long-term plans.

Wasmtime GitHub notifications bot (Dec 18 2020 at 01:03):

cfallin commented on Issue #2435:

Hi all: it doesn't directly address the wasmtime planning (w.r.t. Wasm feature support and other runtime efforts), but I've put up an RFC just now with a proposed roadmap for Cranelift in 2021 (bytecodealliance/rfcs#8), which may be relevant for planning purposes as wasmtime relies on and benefits from Cranelift improvements (and Cranelift lives in this repo) :-)

Wasmtime GitHub notifications bot (Dec 20 2020 at 15:11):

sunfishcode commented on Issue #2435:

The recent 1-year-update blog post lays out a roadmap for a lot of the things that we'll be focusing on in Wasmtime.

Last updated: Dec 23 2024 at 12:05 UTC