Out of topic but I can't help to notice the og:image of the web page is 57 MiB. https://www.datocms-assets.com/2885/1702507860-mitchell-hc19...
Mitchell reflects as he departs HashiCorp
101–110 of 192 posts
Re: Mitchell reflects as he departs HashiCorp
#102Just a side thought, with all due respect: > The controversial worldviews such as multi-cloud that we founded this company on are now mainstream and broadly accepted. Emm .. no. It is not mainstream. Multi-cloud may be forced choice for some regulated fintech, but no sane project will double the infra codebase just to get from "lock-in". I see no other benefits. And double the codebase is quadruple the bugs. This is…
Multi-cloud doesn’t mean you duplicate your infra deployment across multiple cloud platforms for redundancy. It means you integrate the best features of each cloud to run your stack. Cloudflare for cdn, GCP for load balancing, aws for compute, snowflake for big data, etc etc… It is absolutely mainstream.
> Cloudflare for cdn, GCP for load balancing, aws for compute
Isn't this cause you to pay twice the already expensive Egress fee ?
Re: Mitchell reflects as he departs HashiCorp
#103Out of topic but I can't help to notice the og:image of the web page is 57 MiB. https://www.datocms-assets.com/2885/1702507860-mitchell-hc19...
I believe the idiomatic term would be “off topic” :)
Re: Mitchell reflects as he departs HashiCorp
#104Congrats on leaving! The thing I always most respected about Mitchell was that he was actually often coding. So many "leaders" these days, are all talk and no action or skill. Maybe they had some git commits once upon a time, but I always felt like Mitchell was always coding throughout. Too bad what happened with the licensing stuff at the company though.
> Too bad what happened with the licensing stuff at the company though.
OOTL here. What happened?
Re: Mitchell reflects as he departs HashiCorp
#105We'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.
Followed your work since that launch - thanks for everything! Enjoy your family and find some new fun things to explore.
Re: Mitchell reflects as he departs HashiCorp
#106Earlier quoted context omitted.
Heh, I have mostly worked on AWS but we stopped using CloudFormation because the experience was so much worse than Terraform with the lengthy deploys, no diffs, significant time delays supporting new AWS features, and deadlocks. They’ve added diffs but turning debugging into a half hour or longer break is still a problem.
Another point - you can jump on AWS support to help you with Cloudformation. They'll wash their hands when its Terraform :) And chasing where the var value actually came from in TF drove me mad few times!
They also did that for Cloud Formation in my experience. It’s better now that you can tell CF to forget about resources but I still get people asking for help dealing with a hung stack.
Re: Mitchell reflects as he departs HashiCorp
#107Congrats on leaving! The thing I always most respected about Mitchell was that he was actually often coding. So many "leaders" these days, are all talk and no action or skill. Maybe they had some git commits once upon a time, but I always felt like Mitchell was always coding throughout. Too bad what happened with the licensing stuff at the company though.
> Too bad what happened with the licensing stuff at the company though. OOTL here. What happened?
They switched to a proprietary license for all their products. Their CEO said some stuff in an interview. Their stock is plummeting.
Check online yourself. Disclaimer, I am the author of a similar tool: https://github.com/purpleidea/mgmt/
Re: Mitchell reflects as he departs HashiCorp
#108We'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) using Vagrant. First Child is always going to be a hectic job beyond comprehension. Hopefully you will have more free time to play with Zig and may be even Crystal once your child grows a little more. Best of Luck.
Edit: I guess HN momentarily went down due to this announcement on front page.
Re: Mitchell reflects as he departs HashiCorp
#109Earlier quoted context omitted.
This is a weird take. If anything, Nomad, Consul and Vault are on the ascent, as the realities of the CNCF ecosystem set in for people with results to deliver.
The BSL licensing thing has turned off a lot of the more hobbyist/tinkerer-centric users who really rocketed HashiCorp's products up the ladder in their orgs. It's a bit like Elasticsearch, I think—it's gotten big enough it won't be a quick death, but I don't see Hashi's products growing/dominating as much now as I did a couple years ago. (As an aside, I'd like to thank Mitchell for his work over the years, Vagrant e…
It's true that the licensing change is a turnoff, but Terraform redefined an industry. What's the alternative?
(I'm hoping Mitchell is going to have an answer to that)
Re: Mitchell reflects as he departs HashiCorp
#110Congrats on leaving! The thing I always most respected about Mitchell was that he was actually often coding. So many "leaders" these days, are all talk and no action or skill. Maybe they had some git commits once upon a time, but I always felt like Mitchell was always coding throughout. Too bad what happened with the licensing stuff at the company though.
> Too bad what happened with the licensing stuff at the company though. OOTL here. What happened?