3 ms·

..and is not even open source (EDIT: I'm wrong, see below). Zed's remote server on the other hand seems to be OSS. One could probably install it themselves with

..and is not even open source (EDIT: I'm wrong, see below). Zed's remote server on the other hand seems to be OSS. One could probably install it themselves without relying on the automatic download. https://github.com/zed-industries/zed/tree/633b665379c18a06959102c3857889b8bcbde4bb/crates/remote_server https://github.com/zed-industries/zed/tree/633b665379c18a069...

echoangle 2y ago
Interesting, I didn’t know the VS Code server component wasn’t open source.
- hu3 2y ago
  it is though
eddythompson80 2y ago
? The remote server (reh) is part of the vscode repo itself https://github.com/microsoft/vscode/tree/main/src/vs/server/node https://github.com/microsoft/vscode/tree/main/src/vs/server/... there is a vscodium and codeoss builds of it too (reh builds). The extension that invokes it isn’t, but there are a few implementations of it that are, and I think vscodium bundles one with their build. It’s just some shell scripts that download the reh build and run it with the correct args.
- frankjr 2y ago
  Hmm, are the docs outdated then or are they talking about something else? > The Visual Studio Code Remote Development extensions and their related components use an open planning, issue, and feature request process, but are not currently open source. https://code.visualstudio.com/docs/remote/faq#_why-arent-the-remote-development-extensions-or-their-components-open-source https://code.visualstudio.com/docs/remote/faq#_why-arent-the...
  - eddythompson80 2y ago
    That’s the extension which launches the server. The server itself, which is what runs on the remote machine, is part of the vscode repo itself. You can see this open source extension for an example of what the extension does as well as an explanation of what it does https://github.com/xaberus/vscode-remote-oss https://github.com/xaberus/vscode-remote-oss Mainly just sets up the UI/connect commands in vscode UI and launched REH (the vscode server) on the remote machine. The actual server is just a different binary you build from the same repo. Non-Microsoft OSS builds of vscode work with SSH fine.
    - frankjr 2y ago
      Thank you for pointing this out.

echoangle 2y ago

Interesting, I didn’t know the VS Code server component wasn’t open source.

hu3 2y ago
it is though

eddythompson80 2y ago

? The remote server (reh) is part of the vscode repo itself https://github.com/microsoft/vscode/tree/main/src/vs/server/node https://github.com/microsoft/vscode/tree/main/src/vs/server/... there is a vscodium and codeoss builds of it too (reh builds). The extension that invokes it isn’t, but there are a few implementations of it that are, and I think vscodium bundles one with their build. It’s just some shell scripts that download the reh build and run it with the correct args.

frankjr 2y ago
Hmm, are the docs outdated then or are they talking about something else? > The Visual Studio Code Remote Development extensions and their related components use an open planning, issue, and feature request process, but are not currently open source. https://code.visualstudio.com/docs/remote/faq#_why-arent-the-remote-development-extensions-or-their-components-open-source https://code.visualstudio.com/docs/remote/faq#_why-arent-the...
- eddythompson80 2y ago
  That’s the extension which launches the server. The server itself, which is what runs on the remote machine, is part of the vscode repo itself. You can see this open source extension for an example of what the extension does as well as an explanation of what it does https://github.com/xaberus/vscode-remote-oss https://github.com/xaberus/vscode-remote-oss Mainly just sets up the UI/connect commands in vscode UI and launched REH (the vscode server) on the remote machine. The actual server is just a different binary you build from the same repo. Non-Microsoft OSS builds of vscode work with SSH fine.
  - frankjr 2y ago
    Thank you for pointing this out.