11 ms·
> But is unfortunate that they used literally the name of the most famous extension for WebAssembly in VSCode (vscode-wasm), which has been around already for a
by capableweb 3y ago
> But is unfortunate that they used literally the name of the most famous extension for WebAssembly in VSCode (vscode-wasm), which has been around already for a few years, as it might confuse people on what is what:
At this point, where Microsoft frequently ends up naming something identically to something else already existing (and sometimes quite popular) I'm done believing it's "unfortunate" and not on purpose. Once or twice maybe it's some unfortunate accident, but at this frequency?
- duped 3y agoIt's more likely that they just don't care. There's a certain cavalier attitude from the VS Code project in general.
- jeroenhd 3y agoIt's similar to how Google chose "Go" for their language despite the existence of another programming language named the same. Big companies don't care unless you have a trademark.
- syrusakbary 3y agoLet's give them the benefit of the doubt, and let next actions speak for themselves. I've created an issue in their repo, so they are fully aware of the issue and they have the opportunity to amend it :) https://github.com/microsoft/vscode-wasm/issues/62 https://github.com/microsoft/vscode-wasm/issues/62
- capableweb 3y ago> So I think from a VS Code user perspective there will be no name clash. That went well :)
- syrusakbary 3y ago(crying in silence)