<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ssh on emsenn.net</title>
    <link>https://emsenn.net/tags/ssh/</link>
    <description>Recent content in Ssh on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/ssh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote Development Environments</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/texts/remote-development-environments/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/software-engineering/texts/remote-development-environments/</guid>
      <description>&lt;p&gt;A remote development environment is any arrangement where the&#xA;developer&amp;rsquo;s editor runs locally but code execution, file storage,&#xA;and tooling run on a separate machine. The practice is older than&#xA;the term — Unix terminals connected to shared servers in the 1970s&#xA;were remote development environments — but the modern form emerged&#xA;around 2019 with VS Code Remote SSH and has since split into three&#xA;distinct architectures.&lt;/p&gt;&#xA;&lt;h2 id=&#34;ssh-based-remote-development&#34;&gt;&lt;a href=&#34;#ssh-based-remote-development&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;SSH-based remote development&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The simplest architecture: a developer connects to a remote machine&#xA;over SSH, and the editor handles the split transparently. The remote&#xA;machine runs the language server, file system, terminal, and build&#xA;tools. The local machine handles rendering and input.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
