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

IBM completes acquisition of HashiCorp

newsroom.ibm.com

Post reply on HN
Print view View original

201–210 of 407 posts

Re: IBM completes acquisition of HashiCorp

#201

Post by zifpanachr23 »

nayuki wrote: post #196
thisisnotauser wrote: post #137

Earlier quoted context omitted.

I've had the incredible displeasure of having to maintain multiple massive legacy COTS systems that were once designed by promising startups and ultimately got bought by IBM. IBM turned every last one into the shittiest enterprise software trash you can imagine. Every IBM product I've ever used is universally reviled by every person I've met who also had to use it, without exaggeration in the slightest. If anything,…

> Every IBM product I've ever used is universally reviled by every person I've met who also had to use it During my time at IBM and at other companies a decade ago, I can name examples of this: * Lotus Notes instead of Microsoft Office. * Lotus Sametime Connect instead of... well Microsoft's instant messengers suck (MSN, Lync, Skype, Teams)... maybe Slack is one of the few tolerable ones? * Rational Team Concert inst…

The green screens tend to be much quicker and more responsive than the web frontends that are developed to replace them.

I've seen a lot of failed projects for data entry apps because the experienced workers tend to prefer the terminals over the web apps. Usually the requirement for the new frontend is driven by management rather than the workers.

Which is understandable to me as a programmer. If it's a task that I'm familiar with, I can often work much more quickly in a terminal than I can with a GUI. The assumption that this is different for non-programmers or that they are all scared of TUIs is often a mistaken assumption. The green screens also tend to have fantastic tab navigation and other keyboard navigation functionality that I almost never see in web apps (I'm not sure why as I'm not a front end developer, but maybe somebody else could explain that).

I'll defend green screens all day long. Lots of people like them and I like them.

Everything else you listed I would agree with you about being terrible and mostly hated though.

Re: IBM completes acquisition of HashiCorp

#202

Post by glenngillen »

jtimdwyer wrote: post #173
jmholla wrote: post #144

Earlier quoted context omitted.

I'm pretty sure you are. I've had it protect me from `terraform destroy`.

I think the previous post is saying a resource removed from a configuration file rather than an invocation explicitly deleting the resource in a command line. Of course if it’s removed from the config file, presumably the lifecycle configuration was as well!

Yeah, that's a legit challenge that it would be great if there was a better built-in solution for (I'm fairly sure you can protect against it with policy as code via Sentinel or OPA, but now you're having to maintain a list of protected resources too).

That said the failure mode is also a bit more than "a badly reviewed PR". It's:

* reviewing and approving a PR that is removing a resource * approving a run that explicitly states how many resources are going to be destroyed, and lists them * (or having your runs auto approve)

I've long theorised the actual problem here is that in 99% of cases everything is fine, and so people develop a form of review fatigue and muscle memory for approving things without actually reviewing them critically.

Re: IBM completes acquisition of HashiCorp

#203

Post by tensor »

thisisnotauser wrote: post #137
schmichael wrote: post #110

I joined HashiCorp in 2016 to work on Nomad and have been on the product ever since. Definitely a lot of feelings today. When I joined HashiCorp was maybe 50 people. Armon Dadgar personally onboarded us one at a time, and showed me how to use the coffee maker (remember to wash your own dishes!). There have been a lot of ups (IPO) and downs (BUSL), but the Nomad team and users have been the best I've ever gotten to wo…

I've had the incredible displeasure of having to maintain multiple massive legacy COTS systems that were once designed by promising startups and ultimately got bought by IBM. IBM turned every last one into the shittiest enterprise software trash you can imagine. Every IBM product I've ever used is universally reviled by every person I've met who also had to use it, without exaggeration in the slightest. If anything,…

Why leave terraform? You don’t feel OpenTofu will carry the torch well enough?

Re: IBM completes acquisition of HashiCorp

#204

Post by grepfru_it »

burnte wrote: post #15
toomuchtodo wrote: post #7

Earlier quoted context omitted.

Broadcom VMware play. If you’re invested as an enterprise in the ecosystem, is going to be a while before you can extricate yourself. In the meantime, you must pay up.

I'm pretty good at engineering fast moves. I took a company off of Salesforce in 45 days. VMware servers are even easier to changeout. Never done Terraform though.

This cowboy attitude doesn’t fly in regulated industries. Where VMware and co reign supreme

Re: IBM completes acquisition of HashiCorp

#205

Post by bonzini »

adastra22 wrote: post #170
throwaway2037 wrote: post #139

Earlier quoted context omitted.

How is Red Hat going after the acquisition by IBM? From my view, it is going well. The enterprise product (RHEL) is still excellent.

Dropping CentOS was a terrible decision. I’m not sure if that happened before or after the acquisition though.

It mostly happened afterwards but it was not driven by IBM.

Re: IBM completes acquisition of HashiCorp

#206

Post by bobloblaw22 »

throwaway2037 wrote: post #145
hashicorporal wrote: post #46

Earlier quoted context omitted.

We experienced arbitrary layoffs in 2023, followed by an ominous feeling that more layoffs were imminent. However, the announcement of a deal changed the situation. Now, we are actively hiring for numerous positions. Personally, I am not planning to stay much longer. I had hoped that our corp structure would be similar to RedHat, but it seems that they intend to fully integrate us into the IBM mothership.

Was HashiCorp ever profitable since its IPO? From here, it says no: https://stockanalysis.com/stocks/hcp/financials/ If never profitable (or terrible return on equity), why would you call the layoffs "arbitrary"? It seems pretty reasonable to me.

Why hire people in the first place if you aren't profitable? Seems pretty irresponsible to me. Or have the rules changed?

Re: IBM completes acquisition of HashiCorp

#209

Post by glenngillen »

sepositus wrote: post #86
hiatus wrote: post #79

Earlier quoted context omitted.

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

What happens when you run `terraform apply`? Arguably, a lot of things, but at its core it: - Computes a list of resources and their expected state (where computation is generally proportional to the number of resources). - Synchronizes the remote state by looking up each of these resources (where network ingress/egress is proportional to the number of resources). - Compares the expected state to the remote state (ag…

you can probably get a sense of it based on your own usage of terraform and the log output (or the time various resources take to get managed in the Terraform Cloud/Enterprise UI). I think in the majority of cases you'll see that the bulk of the compute time is actually network bound, not because of the number of resources, just because the server at the other end (AWS, Azure, GCP, etc.) is doing a lot of work. I know in some cases things like SQL Server Clusters on Azure can take literally hours to provision. Terraform will spend that "compute" time sitting there waiting, it's not actually doing much resource intensive though.

And then at the end as you said "stores the new state". Which is basically a big JSON file. 10 resources? 1M resources? I'll leave you to work out how much it probably costs to save a JSON file of that size somewhere like S3 ;)

Re: IBM completes acquisition of HashiCorp

#210

Post by febyewary »

transitivebs wrote: post #80

"HashiCorp's capabilities drive significant synergies across multiple strategic growth areas for IBM, including Red Hat, watsonx, data security, IT automation and Consulting" this sounds like corporate AI slop

Worst part is that a lot of that slop is actually still human-generated.
Post reply on HN