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

101–110 of 407 posts

Re: IBM completes acquisition of HashiCorp

#101

Post by goodoldneon »

JohnMakin wrote: post #77
ants_everywhere wrote: post #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 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.

IIRC, the lifecycle hook only prevents destruction of the resource if it needs to be replaced (e.g. change an immutable field). If you outright delete the resource declaration in code then it’s destroyed. I may be misremembering though

Re: IBM completes acquisition of HashiCorp

#102

Post by JohnMakin »

defrost wrote: post #100
JohnMakin wrote: post #91

Earlier quoted context omitted.

The same as in any other language when what you wrote was not what you intended? Sorry, I’m really confused what your complaint here is or how you’d prefer it to work. If you make a sensitive resource managed by any kind of IAC, of course the IAC can destroy it in a manner that would result in irretrievable data loss. The language has for forever put semantics in place to prevent that, and I’m not sure as a power use…

> what happens if you forget to free a pointer in c? Assuming you mean 'forget' to free malloc'd space referenced by at least one pointer, that's an easy one .. it's reclaimed by the OS when the process ends. Whether that's a bad thing or not really depends on context - there are entire suites of interlocked processing pipelines built about the notion of allocating required resources, throughputing data, and terminat…

surely my salient point is recognized regardless of semantics, but thanks for the correction. To use another example in another post - what happens if you DROP TABLE in sql?

Re: IBM completes acquisition of HashiCorp

#103

Post by subpixel »

ghaff wrote: post #68
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.

Red Hat has been a very atypical approach. There has been some swapping of teams back and forth but, as far as I can tell (been out of it for a while), Red Hat is still quasi-independent. Still lots of changes (probably most notably because of a lot of growth) but strategic Red Hat areas still seem to be pretty independent.

Broadly independent but filled to the gills with folks who spent a decade or more at IBM before landing at Red Hat. While this has been true of rank and file for years, recently it’s true on the c-suite.

Re: IBM completes acquisition of HashiCorp

#104

Post by scrapcode »

NetOpWibby wrote: post #67
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.

I really wanted to work at HashiCorp in 2017/2018 and did five interviews in one day only to get ghosted[1]. That experience soured me on HC and its tools but I still admired them from afar. End of an era. --- [1]: https://blog.webb.page/2018-01-11-why-the-job-search-sucks.t...

What do you expect is the reason this happens? I would suspect your skill assessment after a handful of interviews is sound and most people liked you. Do you think you just run into a person eventually that doesn't vibe?

Re: IBM completes acquisition of HashiCorp

#105

Post by brudgers »

tiniestcabbage wrote: post #73
brudgers wrote: post #48

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.

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…

+ There’s an argument against every rule of thumb.

+ For what it is worth, the just-one-percent-of-all-Chinese is historically a poor business strategy.

+ As you point out, targeting price sensitive customers puts you in competition with Walmart and Amazon. Not only that but you are competing for their worst customers.

you're not fighting every startup on the planet for the same handful of clients

Not having access to good clients/customers suggests the business idea might not be viable. Chasing money from people without the wherewithal or will to pay, does not make your business idea viable.

But again it is a rule of thumb.

Re: IBM completes acquisition of HashiCorp

#106

Post by SOLAR_FIELDS »

ants_everywhere wrote: post #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 undiff…

An easy way to get someone to admit that terraform is a hacky child’s language is to ask how to simply print out the values of variables and resources you are using in terraform easily. This basic programming language 101 functionality is not present in the language

Re: IBM completes acquisition of HashiCorp

#109

Post by Xelynega »

SOLAR_FIELDS wrote: post #106
ants_everywhere wrote: post #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 undiff…

An easy way to get someone to admit that terraform is a hacky child’s language is to ask how to simply print out the values of variables and resources you are using in terraform easily. This basic programming language 101 functionality is not present in the language

I agree that terraform is hacky, but is "terraform output {variable name}" not how you would do that?

Re: IBM completes acquisition of HashiCorp

#110

Post by schmichael »

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

I've only ever worked at startups before, but HashiCorp itself left that category when it IPO'd. Each phase is definitely different, but then again I don't want go back to roadmapping on a ridiculously small whiteboard in a terrible sub-leased office and building release binaries on my laptop. That was fun once, but I'm ready for a new phase in my own life. I've heard the horror stories of being acquired by IBM, but I've also heard from people who have reveled in the resources and opportunities. I'm hoping for the best for Nomad, our users, and our team. I'd like to think there's room in the world for multiple schedulers, and if not, it won't be for lack of trying.

Post reply on HN