Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd probably install a snapshotting filesystem before I let it change stuff on my system (such as installing packages and such).


That's what devcontainers are for. You create the config and the editor runs effectively inside of the docker container. Works surprisingly good. Vscode for example even Auto proxies opened ports inside of the container to the host etc.

Will also make using Linux tooling a lot easier on non- Linux hosts like Windows/MacOS


It's nice in theory.

In practice, they require a lot of sysadmin-related work, and installing all the software inside them is no fun, even if using scripts, etc.


It's a one time time investment that most people already have partially and just needs to be transcribed (existing compose/dockerfile)


> It's a one time time investment

No, because the software that needs to be installed into them keeps changing (new versions, new packages, etc.)

Sysadmin is a job for a reason. And with containers you are a sysadmin for more than one system.


I see, it's rare to interact with someone that hasn't discovered dependency management yet and hasn't made that part of their project. If you did manage to integrate that into your, it would consequently make it a one time time investment, because things are automatically pulled in with the versions specified.


Or isolate in a VM.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: