3 ms·

I think that you are wrong on VS Code Remote not being open source. Here is the relevant repository: https://github.com/microsoft/vscode-remote-release https://

by ablekh 6y ago

I think that you are wrong on VS Code Remote not being open source. Here is the relevant repository: https://github.com/microsoft/vscode-remote-release https://github.com/microsoft/vscode-remote-release. Corresponding official documentation (https://code.visualstudio.com/docs/remote/remote-overview https://code.visualstudio.com/docs/remote/remote-overview) states that Visual Studio Codespaces is essentially a managed service of Visual Studio Code Remote Development. BTW, there is also an interesting alternative, the `code-server` project (https://github.com/cdr/code-server https://github.com/cdr/code-server). P.S. FYI: The TLS certificate on https://gitsense.com https://gitsense.com has expired.

sdesol 6y ago
I vaguely remember a post a while back (maybe a year ago) where they said they can't make a part of their remote technology open-source. Maybe things have changed, but I was quite sure it was something they were keeping close to them. Also thanks for pointing out the certificate issue. I was actually leaving it that way on purpose, but I guess it can reflect poorly on my product, so I should just update the landing page with something non-descriptive.
- ablekh 6y ago
  Perhaps, you're right (or maybe not :-). Frankly, all this stuff, while interesting and eventually useful, is a bit low on my current priority list ... Re: certificate - You're welcome.
jedieaston 6y ago
That repo doesn’t have any code in it, it’s used purely for issue tracking and syncing with the VS extension repo, I believe.
- ablekh 6y ago
  My bad. Apparently, you're correct. It seems that relevant code is a part of VS Code codebase. Perhaps, this is it (though, I very well might be wrong on this, too): https://github.com/microsoft/vscode/tree/master/src/vs/workbench/services/remote https://github.com/microsoft/vscode/tree/master/src/vs/workb....

by ablekh 6y ago

sdesol 6y ago

I vaguely remember a post a while back (maybe a year ago) where they said they can't make a part of their remote technology open-source. Maybe things have changed, but I was quite sure it was something they were keeping close to them. Also thanks for pointing out the certificate issue. I was actually leaving it that way on purpose, but I guess it can reflect poorly on my product, so I should just update the landing page with something non-descriptive.

ablekh 6y ago
Perhaps, you're right (or maybe not :-). Frankly, all this stuff, while interesting and eventually useful, is a bit low on my current priority list ... Re: certificate - You're welcome.

jedieaston 6y ago

That repo doesn’t have any code in it, it’s used purely for issue tracking and syncing with the VS extension repo, I believe.

ablekh 6y ago
My bad. Apparently, you're correct. It seems that relevant code is a part of VS Code codebase. Perhaps, this is it (though, I very well might be wrong on this, too): https://github.com/microsoft/vscode/tree/master/src/vs/workbench/services/remote https://github.com/microsoft/vscode/tree/master/src/vs/workb....