You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note, this is part of the 2020 Theme Proposals Process - feel free to create additional/alternate proposals, or discuss this one in the comments!
Theme description
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable target for compilation of high-level languages like C/C++/Rust, enabling deployment on the web for client and server applications.
Core needs & gaps
While having multiple concurring implementations of the same thing is great, it would be even better if they didn't have to be coded twice. Moreover, some of the benefits of writing the reference implementation in Go are gone if it's going to be completely re-written in JavaScript.
Why focus this year
There's already considerations of re-writing the whole thing in Rust (#54) because of the disadvantages of maintaining two separate implementations. Focusing efforts on the Go implementation would take less time and bring the same benefits as re-writing it in Rust, namely reduce implementation, maintenance and quality control efforts.
Hey Nato! Are you interested in taking this on? We actually already chose our focus for 2020 (Content Routing Performance), but that doesn't mean this can't move forward. There's active work underway on Rust-IPFS and I'd love to see the wasm prototype graduate into a more serious browser contender as well. If you have some cycles to spend on this that'd be awesome!
Note, this is part of the 2020 Theme Proposals Process - feel free to create additional/alternate proposals, or discuss this one in the comments!
Theme description
Core needs & gaps
While having multiple concurring implementations of the same thing is great, it would be even better if they didn't have to be coded twice. Moreover, some of the benefits of writing the reference implementation in Go are gone if it's going to be completely re-written in JavaScript.
Why focus this year
There's already considerations of re-writing the whole thing in Rust (#54) because of the disadvantages of maintaining two separate implementations. Focusing efforts on the Go implementation would take less time and bring the same benefits as re-writing it in Rust, namely reduce implementation, maintenance and quality control efforts.
Milestones & rough roadmap
go-ipfs
towasm
(Support WASM Architecture kubo#5694)ipfs.wasm
Desired / expected impact
The text was updated successfully, but these errors were encountered: