4 ms·
Ask HN: Why wasn't Vagrant widely adopted by open source projects?
With GitHub Codespaces gaining in popularity, I was wondering why the problem of having to setup a whole open dev environment for submitting a tiny fix to an open source project was still the hassle it is. We have software like Vagrant, Docker, etc. which are supposed to take care of exactly this, yet relatively few open source projects provide a file. Why did adding a Vagrantfile not become as natural as adding a README?
- jnash 4y agoI build my software all the time using a normal boring build system. What's the problem here?
- linkdd 4y agoBecause running a VM or a Container is still not a trivial task. Will you use a Virtualbox backend? Hyper-V? VMWare? Something else? How much RAM and CPU will you require for it? What about networking configuration which can easily change from system to system?
- Am4TIfIsER0ppos 4y agoWhy is it not simple to build and run the project on the computer you would normally run it on? I know: the modern crap is voluminous. Think of Jeff Goldblum's line in Jurassic Park "that is one big pile of shit".
- endigma 4y agoI used to use it until it was broken 3/4 of the time due to gem this or gem that, ruby is not cut out for command line applications that I want to be portable or reliable or fast. I'd strongly reconsider using vagrant if it was rust or go or C or something else more reliable
- the__alchemist 4y agoA Django tutorial I used a while back used Vagrant in its workflow. I abandoned the tutorial due to Vagrant being so buggy and finicky. It didn't work due to what I assume was dependency mismatches.