Hacker News Reader

Comment by ipsum2 | Hacker News Reader

In addition, Microsoft refuses to open source their remote VS Code implementation: https://github.com/microsoft/vscode-remote-release

See issue: https://github.com/microsoft/vscode-remote-release/issues/17...

View on HN

Exactly - https://github.com/VSCodium/vscodium/issues/240

"And the remote server actively prevents OSS versions from connecting. Even if you enable the proposed apis needed, you will get an "Unauthorized client" error message."

That extension is a competitive advantage that's crippling Jetbrains. Just business as usual.

What's preventing Jetbrains from making their own remote plugin if it's really crippling them? Also Jetbrains IDEs are closed source software, unlike VS Code, why are we supposed to feel bad for them again? That they're not making even more money?

> Also Jetbrains IDEs are closed source software

Not all of them:

1. https://github.com/JetBrains/intellij-community

2. https://github.com/JetBrains/intellij-plugins

3. https://www.jetbrains.com/pycharm/download/ (see how the Community Edition is Open Source)

I note here, that JetBrains does have a somewhat analogous feature in their Professional license of PyCharm[0].

0: https://news.ycombinator.com/item?id=25722765

I was honestly very surprised that Jetbrains didn't already have a remote plugin.

I know that I wouldn't consider any new editor without one, as I almost always develop on a remote box.

I use JetBrain's remote python interpreter functionality[0] with great success and convenience. For anyone whose development environment is appropriate for its use, I honestly cannot recommend it highly enough. I generally can only use it when I'm running the full "Professional" license version, however.

This uses SSH and SCP to automatically deploy the code to the remote environment and run it with the interpreter on that machine, rather than your own local laptop/desktop. One advantage is that it does not require any special software to be installed on the remote server. VS Code's solution requires a pretty hefty installation consisting of basically an entire copy of VSCode onto the remote server.

The downside of JetBrain's approach... I believe that it requires a local copy of the files in order to perform the "LSP"-like syntax error highlighting / suggestion functionality that JetBrains software is so lauded for. This could be difficult/inconvenient if your codebase is particularly enormous, or if you aren't allowed to mirror it locally.

However, given the amount of support that JetBrains has for this kind of setup, I wouldn't be shocked to see an additional future option for something more in the style of "VS Code Remote Development"

0: https://www.jetbrains.com/help/pycharm/configuring-remote-in...

Cool, good to know that it exists. I may have to push someone I'm working with onto it (assuming he has Pro, which he almost certainly does).

Reply on news.ycombinator.com