Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mitchell reflects as he departs HashiCorp

hashicorp.com

Post reply on HN
Print view View original

181–190 of 192 posts

Re: Mitchell reflects as he departs HashiCorp

#181

Post by jen20 »

kkapelon wrote: post #177
jen20 wrote: post #155

Earlier quoted context omitted.

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

The definition of multi-cloud does not matter when talking about what syntax is.

Re: Mitchell reflects as he departs HashiCorp

#182

Post by nuker »

kkapelon wrote: post #143
nuker wrote: 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…

> The marketing on the website just informs you what you can use any cloud you want.

Disagree. The message says “fault tolerance”, meaning you deploy same things in different clouds. Which brings back to my original post - TF does not help with this, as jen20 said - very different resource models.

Re: Mitchell reflects as he departs HashiCorp

#183

Post by ryanlitalien »

mitchellh wrote: post #15

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.

Congratulations! I was an early Vagrant user, it helped immensely, thank you!

Re: Mitchell reflects as he departs HashiCorp

#184

Post by ak217 »

kkapelon wrote: post #179
pas wrote: post #154

Earlier quoted context omitted.

> 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.

Thanks for noting these. From my experience, neither can replace terraform (though Pulumi might be on the right track). Neither come anywhere close to the Terraform AWS provider, and tightly coupling my IaC to Kubernetes is a non-starter for me (and I'm sure for many others as well).

Re: Mitchell reflects as he departs HashiCorp

#187

Post by nijave »

pas wrote: post #154
kkapelon wrote: post #142

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…

Imo main benefit is you can use 1 tool/deploy pipeline for app and infrastructure.

Yes, technically you can do that with Terraform but in my experience it doesn't work great for code deploys (which tend to have procedural steps)

Re: Mitchell reflects as he departs HashiCorp

#188

Post by beoberha »

faeyanpiraat wrote: post #149
beoberha wrote: post #67

Vagrant is such an awesome tool. It’s been about a decade since I’ve used it in any capacity, but remember being wowed in my first internship when I could just spin up a VM like nothing. Best of luck, Mitchell!

What are you using instead of Vagrant for the same use case?

I work at Microsoft now, so Hyper-V

Re: Mitchell reflects as he departs HashiCorp

#190

Post by earthling8118 »

SOLAR_FIELDS wrote: post #72
andrelaszlo wrote: post #68

Earlier quoted context omitted.

Integrated Circuit. Insatiable Craving. Irrevocable Crust. Indifferent Creator. Ignatios of Constantinople. Instigating Crime. Irritating C**. Individual Contributor. Your guess is as good as mine!

It’s standard big corp parlance for a role that has no direct reports. Obvious terminology for anyone who has worked in an org with a moderate size HR or higher, but anyone else has probably never heard of it. I knew immediately that it meant Individual Contributor but I can easily see someone not knowing it if have never worked in BigCorp

Having worked in a few extremely large organizations myself, I've never had this term used. Only on this site.
Post reply on HN