Live data from Hacker News

IBM completes acquisition of HashiCorp

newsroom.ibm.com

71–80 of 407 posts

Re: IBM completes acquisition of HashiCorp

#71
post #64
post #43

Earlier quoted context omitted.

Yup that's me. Happy user of terraform at that time so bought their stock on the day of IPO.

Where you paying Terraform for anything at the time? My doubt in the value of the company was that I've been using Terraform for years in Enterprise settings and never needed to pay the company for anything.

Totally worthless.

Running a few products. Quoted $1MM or so over 3 years for support. I was able to say no and saved six figures each month.

Re: IBM completes acquisition of HashiCorp

#72
Hashicorp's stuff always struck me as pretty hacky with awkward design decisions. For Terraform (at least a few years ago) a badly reviewed PR could cause catastrophic data loss because resources are deleted without requiring an explicit tombstone.

Then they did the license change, which didn't reflect well on them.

Now it's being sold to IBM, which is essentially a consulting company trying to pivot to mostly undifferentiated software offerings. So I guess Hashicorp is basically over.

I suspect the various forks will be used for a while.

Re: IBM completes acquisition of HashiCorp

#73

Earlier quoted context omitted.

Who's the target audience for this pricing that can afford this? The RUM pricing is indeed quite ridiculous. It feels quite ridiculous, especially if you are managing "soft" resources like IAM roles via Terraform / Pulumi. At least with real resources (say, RDS instances), one can argue that Terraform / Pulumi pricing is a small percentage of the cloud bill. But IAM roles are not charged for in cloud, and there are s…

Who's the target audience for this pricing that can afford this? The kind of customers it is good to have. Because filtering out price sensitive customers is a sound business strategy. As a rule of thumb, solve any problem your customer might have. Except not having money.

There is an argument to be made that price-sensitive customers are a neglected market. Granted, marketing to them is very different - they're prone to being scooped if someone comes by willing to sell your same product to them at a loss (hi, Amazon and Walmart) - but there are a lot more of them and you're not fighting every startup on the planet for the same handful of clients.

Business have made a killing in China and India for a reason, after all.

Re: IBM completes acquisition of HashiCorp

#74

Earlier quoted context omitted.

Who's the target audience for this pricing that can afford this? The kind of customers it is good to have. Because filtering out price sensitive customers is a sound business strategy. As a rule of thumb, solve any problem your customer might have. Except not having money.

Good for who? Good for people getting bonuses? Good for executives? It doesn't seem to be good for the customers or the people using the software or the people contributing to the open source code. It also doesn't seem to have been good for the investors, looking at the other comments.

Good for people who got in pre-IPO. Bad for people who got in post-IPO.

Re: IBM completes acquisition of HashiCorp

#75

Sad to see this, but I will again shill for HashiCorp's Nomad as a better alternative to Kubernetes.

Definitely not better than Kubernetes, but I don't regret working on it and I like it as a simpler alternative to Kubernetes. I remember trying to hire people for it and not a single person ever even heard of it.

Re: IBM completes acquisition of HashiCorp

#77

Hashicorp's stuff always struck me as pretty hacky with awkward design decisions. For Terraform (at least a few years ago) a badly reviewed PR could cause catastrophic data loss because resources are deleted without requiring an explicit tombstone. Then they did the license change, which didn't reflect well on them. Now it's being sold to IBM, which is essentially a consulting company trying to pivot to mostly undiff…

> For Terraform (at least a few years ago) a badly reviewed PR could cause catastrophic data loss because resources are deleted without requiring an explicit tombstone.

There have been lifecycle rules in place for as long as I can remember to prevent stuff like this. I'm not sure this is a "problem" unique to terraform.

Re: IBM completes acquisition of HashiCorp

#78
post #31
post #14

Earlier quoted context omitted.

Pulumi’s RUM pricing is why I was very hesitant to even evaluate it as an alternative to just using terraform.

I’m finding that the basic backend functionality of Pulumi and Terraform managed cloud is fairly easy to build (especially Terraform, I can’t quite believe how absurdly simple their cloud is…)

Plus there are open source projects like Atlantis that fit the bill for many teams with regards to terraform automation.

Re: IBM completes acquisition of HashiCorp

#79
post #5

Earlier quoted context omitted.

Yeap we did. I wrote it off around the time of the licence change, just after they decided to ditch the TF Team plan in favour of the utterly ridiculous “Resources Under Management” billing model. I knew the company had lost the plot at that point.

This is probably inaccurate, but it seemed like they wrote it off as a safe move, with their main competitor, Pulumi, getting away with it. However, to play devil's advocate, the number of Terraform resources is a (slightly weak) predictor for resource consumption. Every resource necessitates API calls that consume compute resources. So, if you're offering a "cloud" service that executes Terraform, it's probably a de…

> However, to play devil's advocate, the number of Terraform resources is a (slightly weak) predictor for resource consumption. Every resource necessitates API calls that consume compute resources. So, if you're offering a "cloud" service that executes Terraform, it's probably a decent way to scale costs appropriately.

That would make sense if you paid per API call to any of the cloud providers.

Post reply on HN