Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2020 Theme Proposal] Compile go-ipfs to wasm #57

Closed
NatoBoram opened this issue Apr 21, 2020 · 3 comments
Closed

[2020 Theme Proposal] Compile go-ipfs to wasm #57

NatoBoram opened this issue Apr 21, 2020 · 3 comments

Comments

@NatoBoram
Copy link

NatoBoram commented Apr 21, 2020

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.

Milestones & rough roadmap

Desired / expected impact

  • Faster development cycles for JS-IPFS
  • Almost no efforts are required to maintain JS-IPFS
  • Better performance for JS-IPFS
  • Better reliability for JS-IPFS
  • Better portability of Go-IPFS
@momack2
Copy link
Contributor

momack2 commented Apr 21, 2020

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!

@NatoBoram
Copy link
Author

I would be, but I entered a crunch time at work so I won't have time anytime soon

@github-actions
Copy link

github-actions bot commented Oct 2, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Oct 2, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants