3 ms·
>why are we rewriting Vagrant in Go? From [1] I dont think Ruby would ever be able to compete in that space. Even Hashicorp, the company that was born out of
by ksec 5y ago
>why are we rewriting Vagrant in Go?
From [1]
I dont think Ruby would ever be able to compete in that space. Even Hashicorp, the company that was born out of vagrant left Ruby and Chose Go.
I am thinking someday Crystal post 1.0 would be able to put up a fight in that space.
I still remember I wrote somewhere, that one day Vagrant will be rewritten from Ruby to Go and got some very negative feedback from someone. ( It was in the Parker era.... )
Vagrant, and the whole HashiCorp products are all infrastructure product it makes sense to be running on Go rather than Ruby.
Nothing to say or ask really. But Thank You and congratulation. At some point I thought you have abandoned Vagrant. Its nice to see Hashicorp continue to update and take care of their first product. And honestly all the HashiCorp product are so much better or simpler than their competitors ( cough K8s cough ). Really wish you and your company continue to move forward with great products and services.
[1] https://news.ycombinator.com/item?id=23457496 https://news.ycombinator.com/item?id=23457496
- bsaul 5y agoCould you give more info on hashicorp VS kubernetes ? I had the feeling they complemented each other.