Live data from Hacker News

Mitchell reflects as he departs HashiCorp

hashicorp.com

171–180 of 192 posts

Re: Mitchell reflects as he departs HashiCorp

#171

We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.

I remember meeting you at a DC Ruby conference after a talk you gave on middleware as a design concept. This was years ago, in the early days of Vagrant I think. Amazing to see how much you’ve accomplished since then. Congrats on your achievements and best of luck with your future hacking!

Re: Mitchell reflects as he departs HashiCorp

#172
post #108

We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.

Just the Link. It all started here. https://news.ycombinator.com/item?id=1175901 Vagrant: A tool for building and distributing virtual development environments (vagrantup.com) 129 points by mitchellh on March 8, 2010 | hide | past | favorite | 28 comments I still remember reading that post on HN. And subsequently Vagrant took off. Cant believe it is nearly 14 years! Thank You Mitchell for everything as I am (still) u…

This is great to read now and reflect on where they eventually went in the next 13 years. The basic questions "why Chef" and "why Virtual Box" and so on with requests to support other hypervisors and provisioning tools. Now Packer and Terraform provision and deploy machines to damn near any platform using damn near any provisioning tool, but neither Mitchell himself nor the HashiCorp team in general had to learn all of those tools and platforms. Instead, they provided orchestration systems that allow for a common configuration language and execution model but delegate the logic of how to use the APIs of specific platforms and provisioners to plugins. Seed the ecosystem with plugins representing the most common platforms and toolchains your company is already familiar with and extend from there to stuff you either figure out later or let the community contribute.

This feels like open source and community creation at its best. It's why GNU/Linux systems did what they did. A bunch of professors and hackers tried to clean-room recreate Unix but never finished the kernel. Meanwhile, some grad student made a kernel but no userspace. Then some entirely different teams put these together along with a package manager, installer, and remote filesystems users could fetch ISOs and packages from, and finally you've got a usable system that didn't require a beast the size of Microsoft to do everything in-house. None of them could have done it alone.

It also makes the events of the past year kind of poignant. I see a lot of commenters talking about HashiCorp needing the license change to capture the value of what they created and not allow other companies to siphon it off. But isn't that the point of civilization? We all stand on the shoulders of giants. We generally don't want the first person to come up with an idea and their direct descendants to be the only people who ever profit off of that idea. That's aristocracy. Mitchell is a billionaire, isn't he? None of Linus Torvalds, Richard Stallman, or Ian Murdoch ever became billionaires, but they weren't exactly starving in the street, either. Exactly how much value does a single person need to capture? It's the community we want to see thrive, isn't it? Not just our single company. Every employee of that company can work elsewhere if they need to and every investor has other investments. They aren't going to starve either if the company someday stops growing.

I get not wanting the Amazons and Googles of the world to take open source inputs and put them into proprietary sinkholes where further innovation gets stuck inside of a single company. But isn't that the point of the GPL? Anything they add they also have to give back. You don't need BUSL for that.

Re: Mitchell reflects as he departs HashiCorp

#173

We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.

Just want to say thank you, from a engineer who in 2010 kickstarted a career by using vagrant to create reproducible dev environments.

Re: Mitchell reflects as he departs HashiCorp

#174

Thanks for the overall contribution to the space, IaC has definitely come a long way. But man don't ever give us another HCL please!

HCL is great, no scoping issues, easy to read and write, great auto format support, easy to incorporate into a go program(and extend with functions). I pick it up very consistently and am happy every time; while each time I have to write YAML I die inside.

Re: Mitchell reflects as he departs HashiCorp

#175

We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.

Thank you for all the great products that you have created! Your vision on infrastructure has always been inspiring to me and you are one of the few engineers who has truly moved the field as a whole forward.

Re: Mitchell reflects as he departs HashiCorp

#176
post #108

Earlier quoted context omitted.

Just the Link. It all started here. https://news.ycombinator.com/item?id=1175901 Vagrant: A tool for building and distributing virtual development environments (vagrantup.com) 129 points by mitchellh on March 8, 2010 | hide | past | favorite | 28 comments I still remember reading that post on HN. And subsequently Vagrant took off. Cant believe it is nearly 14 years! Thank You Mitchell for everything as I am (still) u…

Is there somewhere a list of these big stuff that launched in the HN, eg this and Dropbox https://news.ycombinator.com/item?id=8863 .

PagerDuty: https://news.ycombinator.com/item?id=758653

Re: Mitchell reflects as he departs HashiCorp

#177
post #155

Earlier quoted context omitted.

Terraform supports different clouds but with completely different syntax. The marketing on the website just informs you what you can use any cloud you want. The message is against other tools such as cloud formation (AWS only) or GCM (Google only), ARM (Azure only) and so on. To give you an analogy it would be like Firefox saying that they are "multi-OS" meaning that you can install Firefox if you have Windows and yo…

Strictly incorrect. The syntax is the same for every cloud - either HCL2 or JSON. What you are calling syntax is actually the resource model. Every project which claims to bridge this resource model ends up implementing a lowest common denominator time sink which doesn’t stand up to basic scrutiny. Your analogy also does not demonstrate whatever it is you seem to think it does - Firefox is indeed multi-OS.

It is ok. Parent already said that that they mean something different with "multi-cloud" https://news.ycombinator.com/item?id=38649796

Re: Mitchell reflects as he departs HashiCorp

#179
post #154

Earlier quoted context omitted.

Pulumi and Crossplane Or OpenTF if you want to same thing minus the licensing mess

> Crossplane I tried to understand what is it, how it works, what is it good for, but ... never managed to. It still has the same "build control planes without needing to write code" on its website. okay, it says "orchestrate applications and infrastructure". that's at least makes sense when the context is Terraform and Pulumi. okay, in the quickstart the whole thing seems like code. but okay. ah, so you can use k8s…

Pulumi -> Same end result as Terraform but you use Code (python, go, typescript) to describe resources instead of hcl

Crossplane -> Same end result as Terraform but you use K8s resources in YAML to describe your infra.

I hope that helps. But I agree that the crossplane/upbound marketing is super confusing.

Re: Mitchell reflects as he departs HashiCorp

#180

We've gone full circle! I originally launched Vagrant here on HN in 2010, which was at the top of HN very briefly for the day. Now here I am 14 years later witnessing my departure post in that very same spot. A strange experience! Thanks for the support over the years. A lot of the initial community for the projects I helped start came from here.

I've been using Vagrant for ~10 years, on a daily basis!

Thank you, @mitchellh !

Post reply on HN