microsoft/vscode-wasm

vscode-wasm is already a name of a popular VSCode Wasm extension. Rename this repo?

syrusakbary opened this issue · 2 comments

syrusakbary commented

First of all... great work on the project.

It came for my realization that you are using the same name vscode-wasm as another extension that is widely popular and used in VSCode: vscode-wasm, which has been around already for a few years.

https://marketplace.visualstudio.com/items?itemName=dtsvet.vscode-wasm
https://github.com/wasmerio/vscode-wasm

Having the same name might be confusing for users, so I want to suggest renaming this repo to something else (vscode-wasm-extensions could be a good name, but really anything other than vscode-wasm could work) so we minimize confusion between repos.

Note: this issue came after some discussion in HN. I think is fair to assume good intent, and give the opportunity for maintainers to work on a fix: https://news.ycombinator.com/item?id=35768888

dbaeumer commented

@syrusakbary thanks for reaching out. The name vscode-wasm is only for the GitHub repository. The extensions will be named very likely ms-vscode.wasm-wasi-core and the npm package to use its API will very likely be called @vscode/wasm-wasi. So I think from a VS Code user perspective there will be no name clash.

syrusakbary commented

Thanks for the quick response!

Yeah, I was aware the name is just for the repo.
If people search for vscode wasm in Google now they would have two repos with exactly the same name that do two very different things, which I think could be confusing for newcomers to the ecosystem. Hence creating the issue