Dev onboarding, then and now

I don&#x27;t see how replacing the &quot;it works on my machine&quot; with &quot;it works in this VM&quot; is much better. It is the same problem.<p>You just added the overhead of running another whole computer in your computer to solve it.<p>Also the author states he is locked into using VS Code, which seems like a risky dependency to have.

The first issue about the machine being macOS or Windows but the code assuming Linux has never been a problem in my experience. Now containers or Nix do make it easier.<p>If the system is deployed on Linux then you run Linux in a VM. (Which also deals with some of the other issues) I have done that since the early 2000 or even before we remotely logged in to a machine running the correct OS (X Windows is useful) albeit I was on site so a fast connection to the server.<p>Now whether it is good design to make assumptions that only Linux matters is another question. I am old enough that I had to use multiple Unix systems SunOS Solaris NeXTStep and Linux. And good practice was to compile C++ with two different compilers as the error messages and edge cases were not very edge.

Kind of a long way to say that the author uses Docker for development environments.

Containers: Nobody gets the installation right. We give up, let&#x27;s ship everything!<p>Nix&#x2F;Guix: Why? We literally solved this issue 20 years ago.

Some painpoints wrt DevPod:<p>In order to get devpod ssh to work, DevPod injects itself into your host machine (where all the devcontainers run). When you ssh into your devcontainer, devpod&#x27;s ssh implementation acts as a proxy into the container, allowing you to get an in-container shell without having to run sshd inside the container. But people are already injecting VS Code into remote machines, so maybe this doesn&#x27;t matter to you.<p>DevPod&#x27;s ssh implementation does not handle newlines properly; full-screen displays can get garbled on many terminals. But most DevPod users are using the terminal inside VS Code, which seems to work fine.

Has anyone faced any challenges integrating these tools with specific IDEs or version control systems? How did you address issues like plugin compatibility or build automation within these environments?

I have found that a nix devshell (with direnv) to be the most miraculous solution to weird such as these.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;numtide&#x2F;devshell">https:&#x2F;&#x2F;github.com&#x2F;numtide&#x2F;devshell</a>

Tbh I&#x27;ve found nix and flakes as remarkable in terms of solving that issue.

This is a solved problem, and the solution is Nix, not Docker

<a href="https:&#x2F;&#x2F;coder.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;coder.com&#x2F;</a>

You should never run a command you don&#x27;t understand.<p>The whole premise of this article is shaky.