Live data from Hacker News

Mitchell reflects as he departs HashiCorp

hashicorp.com

151–160 of 192 posts

Re: Mitchell reflects as he departs HashiCorp

#151

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 once (March 2014) emailed hashicorp to retrieve a lost vagrant licence key. I got a direct reply from you Mitchell with instructions on what to do. Blew my tiny mind, those were rare bygone days in our industry. Thank you for all you've created.

In 1992 I replied to an email from Steve Jobs that was shipped in the default email client of the NeXT workstation I was using. I checked the 'read receipt' box in the client. He replied, ignoring my question and berating me for violating his privacy by using the read receipt feature.

Re: Mitchell reflects as he departs HashiCorp

#152

I got really excited about Consul when I read about it here many years ago. I wrote a ruby library for it ( https://github.com/WeAreFarmGeek/diplomat ) which became rather popular, and was used by quite a few large organisations. Hashicorp sent me a care package to thank me - a T-shirt and a card signed by Mitchell himself - I wore that T-Shirt until it was threadbare and I still have the card. Its a small thing on t…

is this the same team that got greedy recently - which then lead to forking Terraform - or there's been some personnel changes?

Re: Mitchell reflects as he departs HashiCorp

#153
post #90

> the GitHub Octoverse report found that HashiCorp Configuration Language (HCL) has once again emerged as one of the top languages used in open source projects "Hashicorp Configuration Language (HCL) with a 56,1% increase in popularity is the fastest-growing language according to GitHub" Fastest growing and "top" are not the same thing, but I have to assume that you know that @mitchellh. Embarrassed for you. https://…

From the 2023 Octoverse report[1], "In 2023, Shell and Hashicorp Configuration Language (HCL) once again emerged as top languages across open source projects, indicating that operations and IaC work are gaining prominence in the open source space." The accompanying chart shows it as #11, ranking above Dart, Kotlin, and Ruby. I think this is a case where the citation bears out the claim, and there's no need for Mitche…

Ah, thanks. I get to be embarrassed instead! I'll take it.

Re: Mitchell reflects as he departs HashiCorp

#154
post #109

Earlier quoted context omitted.

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)

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 CRDs to define cloud stuff (like S3 buckets and GCP GCS buckets and whatnot), not bad, but super verbose.

Re: Mitchell reflects as he departs HashiCorp

#155
post #88

Earlier quoted context omitted.

> Doing the same infra, across multiple clouds, is a different thing, it's not a Hashi thing. Not sure about this. Here is what official site says: "Provisioning infrastructure across multiple clouds increases fault tolerance, allowing for more graceful recovery from cloud provider outages." https://www.terraform.io/use-cases/multi-cloud-deployment

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.

Re: Mitchell reflects as he departs HashiCorp

#156

Earlier quoted context omitted.

Nomad is dead in the water. When you talk to Consul support engineers, they assume you're using kubernetes, and are confused if you tell them you're using Nomad, _a product that their company makes_.

Nomad will be there when managed k8s gets too expensive. I was looking at it seriously last year for on prem. I chickend put bcz I didn't want to be the only person on my team that understood it. We still don't have a solution, but nomad will be there for when we are ready to progress, regardless of the license.

> I chickend put bcz I didn't want to be the only person on my team that understood it.

There are online courses for free and paid courses (online and in person) so if they have the desire to learn, you won't be the only person.

Re: Mitchell reflects as he departs HashiCorp

#158
post #157
post #147

Mitchell feels like the exception that proves the rule, the rule being that there are very few engineers turned entrepreneurs that are successful & balanced.

Is he successful if the company is doing so bad?

https://ir.hashicorp.com/news-releases/news-release-details/...

Hashicorp seems to be doing alright to me. Don't look at the stock price.

Re: Mitchell reflects as he departs HashiCorp

#160
post #59

Earlier quoted context omitted.

KMS? Secrets manager? Are those offered by a particular vendor or what

Yes but if you want to be multi-cloud and not have to integrate with each cloud's secret storage API, you would do it once for Vault and bring it with you to each cloud.

Even when going multi-cloud you can employ different strategies. Vault is definitely one of them, but you can also use federation to exchange one cloud's credentials for another's, giving you the ability to centralize secrets in one of them. You can use a layer of abstraction like GoCloud [0]. You can also build for each cloud separately and decide either not to centralize secrets at all, or build some trivial bespoke tooling to synchronize some of them. I'm not endorsing any of the options, nor am I trying to argue that Vault is never the right choice, I'm just pointing out that Vault isn't the only viable alternative.

https://github.com/google/go-cloud

Post reply on HN