7 ms·

Appears to me as a response to VS Code's remote capabilities.

• hhariri 5y ago
  We've announced Remote Development support today https://blog.jetbrains.com/blog/2021/11/29/introducing-remote-development-for-jetbrains-ides/ https://blog.jetbrains.com/blog/2021/11/29/introducing-remot...
  • noworriesnate 5y ago
    Cool! What's the relationship between JetBrains Fleet, JetBrains Projector[1], and Remote Development? [1] https://lp.jetbrains.com/projector/?utm_source=product&utm_medium=link&utm_campaign=TBA https://lp.jetbrains.com/projector/?utm_source=product&utm_m...
    • filereaper 5y ago
      Yes, I'm on the EAP builds and was confused by this exact set of overlapping products. It would be nice if JetBrains added a feature matrix or disambiguated when and where each product is suitable for. Also obligatory: https://xkcd.com/927/ https://xkcd.com/927/
  • tomjen3 5y ago
    That sounds awesome. One point though - VS Code also allows you to setup a reproducable dev environment locally or through an SSH connection. It isn't clear to me based on the video if that feature is exclusive to Space or not.
• lozenge 5y ago
  And VS Code's hosted offering (VSCode.dev and GitHub Codespaces). Fleet doesn't seem to run in the browser which could offer a better UX. The remote capabilities also look to be more seamless as VS Code is still local by default and even after you connect remotely, it still mostly offers to open/browse local files (which could be considered a pro)