Live data from Hacker News

Switching to Claude Code and VSCode Inside Docker

timsh.org

141–150 of 170 posts

Re: Switching to Claude Code and VSCode Inside Docker

#141

I don't get these posts. I'm using claude --dangerously-skip-permissions all day and haven't had a single issue. In my experience it doesn't just randomly start erasing your hard drives. Also having a proper CLAUDE.md probably helps.

Some people never create backups and they never had a problem either.

Re: Switching to Claude Code and VSCode Inside Docker

#142

Earlier quoted context omitted.

If you commit the .devcontainer.json and associated files your whole team gets a consistent, local-feeling, environment for free. Containerisation solved the "Works on my machine" gap between local and prod. This is just solving for the same gap between Dev 1 and Dev 2.

That's a different thing. You're talking about running the software under development in a container. I think the commenter was asking about running the dev tooling in a container, which I find a massive pain.

No, that’s what they’re talking about - running the tooling in a container. Dev tool chains are a pain in the ass to keep consistent in even small teams. Devcontainers solve that.

Re: Switching to Claude Code and VSCode Inside Docker

#143

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

> If you are a VSCode hater (like me) What are some reasons to hate VSCode?

I personally feel some inner sense of dissonance when I use software written in Electron when alternatives are available. Software targeted to the technical audience has no valid reason not to aim higher in terms of performance and fundamentals.

Re: Switching to Claude Code and VSCode Inside Docker

#144
post #137
post #121

Earlier quoted context omitted.

It's proprietary software masquerading as open-source, for one, and intentionally fosters dependence on its vendor for the plugins that support the most popular languages as well as key features (remote editing, WSL support, integration with the mainline plugin repos), for one.

But Cursor, a fork not developed by Microsoft, ships with remote editing, wsl support, etc

It's their reimplementation.

Re: Switching to Claude Code and VSCode Inside Docker

#145
post #37

[flagged]

Why is it that in every Claude Code related submission there's people proudly declaring out-of-context they are not using AI tools? If there's a post about Zig, you don't see people saying how they don't use Zig.

I am proud that I still use pre-standardization C instead of Zig

Re: Switching to Claude Code and VSCode Inside Docker

#146

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

> If you are a VSCode hater (like me) What are some reasons to hate VSCode?

I will give you one reason why I don't like it much:

- The push to use Github Copilot and no option to disable that crap.

I wish there was a fork of VSCode with all the telemetry and all of the proprietary crap disabled with 100% extension support...

Re: Switching to Claude Code and VSCode Inside Docker

#147
post #27

Earlier quoted context omitted.

I swear to you that if you program the way I do you (without any AI tools or even developer tools made after 2005) you will learn 100x more and achieve 100x more

Except you glossed over the part where the person said they lacked time. There is programming the art and programming to solve a problem. The art is great - I’ve written software for decades. Life dictates I no longer have as much time, but I still want to solve problems. AI helps me do that in the limited that I have.

The fatal flaw in your theory is that Docker, Claude, and whoever else will add an infinite amount of time spent debugging once you have a sufficiently complex problem, which is usually within 1-7 days of using it.

Please explain to me how I'm wrong. in the event you don't want to hear how I'm right, I am forstalling that while waiting for your reply

Re: Switching to Claude Code and VSCode Inside Docker

#148

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

VSCodium - Free/Libre Open Source Software Binaries of VS Code

https://vscodium.com/

Re: Switching to Claude Code and VSCode Inside Docker

#149
post #148

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

VSCodium - Free/Libre Open Source Software Binaries of VS Code https://vscodium.com/

Just so you know, the devcontainer VSCode extensions are considered proprietary by Microsoft and therefore not allowed to be installed in VSCodium. There are some open-source container plugins, but they are all a bit janky for the container use-case in my experience.

Re: Switching to Claude Code and VSCode Inside Docker

#150

Honest question: why do people prefer developing code inside a docker? I get the benefits of docker as a deployment unit, but wouldn’t configuring a dev container and using it a hassle nonetheless, compared to not doing them at all?

If you commit the .devcontainer.json and associated files your whole team gets a consistent, local-feeling, environment for free. Containerisation solved the "Works on my machine" gap between local and prod. This is just solving for the same gap between Dev 1 and Dev 2.

Devcontainers don't "feel" local to me, since my CLI tools are not available in them. Think ripgrep or fd, for example.
Post reply on HN