<story><title>Fleet, a Lightweight IDE from JetBrains</title><url>https://blog.jetbrains.com/blog/2021/11/29/welcome-to-fleet/</url></story><parent_chain><item><author>chkhd</author><text>I just hope the remote development features will actually work adequately in this.&lt;p&gt;They tried to get that stuff working with existing IDEs multiple times [0][1][2][3], but they are all broken in their unique ways.&lt;p&gt;Whenever I see them announce something new in the remote development space I always jump in right away and try it out, discover it is broken too, and then go back to using VS Code remote dev features.&lt;p&gt;For local dev I still use JB stuff, but it is simply too broken and awkward for remote.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;help&amp;#x2F;pycharm&amp;#x2F;configuring-remote-interpreters-via-ssh.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;help&amp;#x2F;pycharm&amp;#x2F;configuring-remote-in...&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lp.jetbrains.com&amp;#x2F;projector&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lp.jetbrains.com&amp;#x2F;projector&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.jetbrains.com&amp;#x2F;blog&amp;#x2F;2021&amp;#x2F;11&amp;#x2F;29&amp;#x2F;introducing-remote-development-for-jetbrains-ides&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.jetbrains.com&amp;#x2F;blog&amp;#x2F;2021&amp;#x2F;11&amp;#x2F;29&amp;#x2F;introducing-remot...&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;code-with-me&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;code-with-me&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>mellosouls</author><text>Agree. I paid for PyCharm on the basis that a) it all just worked in the community edition, and b) it offered remote development in professional (this was a main selling point over community).&lt;p&gt;I quickly discovered that b) was false (or extremely oversold) compared to VSCode and switched back, couldn&amp;#x27;t get PyCharm working remotely and saw the loooong-standing issues on the bug tracker that indicated it wasn&amp;#x27;t a priority despite the marketing.&lt;p&gt;I still admire the plug-in-and-go-ability of PyCharm, but no longer trust it to fork out money for features which are clearly not what they are implied to be.&lt;p&gt;Perhaps the latter has changed; I&amp;#x27;ll await the reviews.</text></comment>
<story><title>Fleet, a Lightweight IDE from JetBrains</title><url>https://blog.jetbrains.com/blog/2021/11/29/welcome-to-fleet/</url></story><parent_chain><item><author>chkhd</author><text>I just hope the remote development features will actually work adequately in this.&lt;p&gt;They tried to get that stuff working with existing IDEs multiple times [0][1][2][3], but they are all broken in their unique ways.&lt;p&gt;Whenever I see them announce something new in the remote development space I always jump in right away and try it out, discover it is broken too, and then go back to using VS Code remote dev features.&lt;p&gt;For local dev I still use JB stuff, but it is simply too broken and awkward for remote.&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;help&amp;#x2F;pycharm&amp;#x2F;configuring-remote-interpreters-via-ssh.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;help&amp;#x2F;pycharm&amp;#x2F;configuring-remote-in...&lt;/a&gt;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;lp.jetbrains.com&amp;#x2F;projector&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;lp.jetbrains.com&amp;#x2F;projector&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.jetbrains.com&amp;#x2F;blog&amp;#x2F;2021&amp;#x2F;11&amp;#x2F;29&amp;#x2F;introducing-remote-development-for-jetbrains-ides&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.jetbrains.com&amp;#x2F;blog&amp;#x2F;2021&amp;#x2F;11&amp;#x2F;29&amp;#x2F;introducing-remot...&lt;/a&gt;&lt;p&gt;[3] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;code-with-me&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;code-with-me&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>kombine</author><text>This is also the main reason I switched from PyCharm to VS Code at the start of the pandemic, which I think was really a really fortunate circumstance for the latter IDE. Even though PyCharm is a superior IDE, its remote development features were really broken, while VS Code nailed it.</text></comment>