3 ms·
They really need to rewrite it in go. Ruby has been a disaster for this particular project. Don't even get me started on the Nokogiri issues. Everything they've
by malandrew 12y ago
They really need to rewrite it in go. Ruby has been a disaster for this particular project. Don't even get me started on the Nokogiri issues. Everything they've written in go has functioned better IMHO.
- FooBarWidget 12y agoAre you using their all in one package or do you install from rubygems? The former should give you no problems. If you are doing the latter... well... you shouldn't.
- sciurus 12y agoEven if you use their all-in-one package, you can still have dependency problems installing vagrant plugins. https://github.com/mitchellh/vagrant/issues/3769 https://github.com/mitchellh/vagrant/issues/3769 https://github.com/mitchellh/vagrant/issues/4278 https://github.com/mitchellh/vagrant/issues/4278
- FooBarWidget 12y agoYeah but those are plugins, the Vagrant author can't do anything about what third parties do. You mentioned Go as a better language, but Go does not solve that problem it does not support loadable modules at all. If Vagrant were written in Go it wouldn't have supported plugins at all.
- dandandan 12y agoIt was much more stable for me when I was installing it through rubygems and managing our middleware's dependencies with bundler directly. We've switched to the embedded ruby and it's a struggle but we deal with it since it's probably MUCH less work to support now that it's standardized across all vagrant installs.