Earlier quoted context omitted.
> terraform changed to business source license pretty recently Now we know why!
I suspect you have the causality on this backwards: https://news.ycombinator.com/item?id=38579175
IBM to buy HashiCorp in $6.4B deal
231–240 of 391 posts
Re: IBM to buy HashiCorp in $6.4B deal
#232Earlier quoted context omitted.
Yes. And many of the Heroku employees you speak of would have got RSUs that owed taxes on an $80 basis, been trading far below that for most of that time, and now have a maximum expected value of $35. This is not a pay day for many people. Anybody who got a pay day were those that could liquidate in the IPO.
Yeah okay, if you had 0.15% stock you're still out with $ 10M. Smaller and bigger percentages will be different but that's retirement money for hundreds and hundreds unless you pretend to live in very high CoL area. Also, most of them will likely have to keep working thereyears before cashing out some other millions likely.
Re: IBM to buy HashiCorp in $6.4B deal
#233Earlier quoted context omitted.
Yeah okay, if you had 0.15% stock you're still out with $ 10M. Smaller and bigger percentages will be different but that's retirement money for hundreds and hundreds unless you pretend to live in very high CoL area. Also, most of them will likely have to keep working thereyears before cashing out some other millions likely.
What? What's their strike price? If they are above the sale price their return is 0.
Re: IBM to buy HashiCorp in $6.4B deal
#234Question: Is the tldr of companies like these that they sell enterprise server software? And often own the hardware too (data centers)? And then sell a bunch of consulting services on top of that to Fortune 500s and governments? It's tempting to think "How are these guys even relevant anymore?" but IBM's making $60B+ a year with over $10B cash on hand, apparently from mostly "consulting services". For a lot of develo…
Terraform does help with managing medium-large fleets, and a lot of special sauce is the structured types corresponding to cloud platforms (dubbed "providers") and the different services they offer. You could write your own configuration language and launcher but Terraform has been tested against many setups and can manage rolling restarts and other deployment methods. It's modular so you can define the configuration…
My favorite DevOps setup is my Raspberry Pi home server running Raspbian, love this thing - WiFi, touch screen so I can hold it like a mobile device or just set it down somewhere while it's serving several APIs, websites, etc. all the time including a local business in SF. Haven't stopped or restarted it in months.
I look at some of these big, old behemoths, and just don't get it. Take Oracle - when you really get into what they "do" it's like... oh... so, a database? Right now they offer clone services of the other cloud providers too, and some other things, but it's mostly just those huge consulting contracts. I just wonder how they get them (and at those rates) if not for relationships, it doesn't seem like their technology is particularly good.
Personally I run stuff like React sites on Vercel, backends on a mix of my Raspberry Pi and Heroku, and 1 thing still in GCP that I can't wait to port out of there. Still looking for a home for my LLMs. As an individual developer, I will probably embrace PaaS and convenience more and more with regards to DevOps, but yeah interesting to see where open-source Terraform goes - would be cool to see companies doing more customized infra internally instead of everyone using AWS.
Re: IBM to buy HashiCorp in $6.4B deal
#235Earlier quoted context omitted.
What in particular did you find difficult building a maintainable codebase in Golang? Not quite understanding the boilerplate reference. Code generation in Golang is something I've found removed a lot of boilerplate.
I am not used to writing code where 2/3 of it is "if err" statements. Also, refactoring my logging statements so I could see the chain of events seemed like work I rarely had to do in other languages. It's a language the designers of which - with ALL due respect - clearly have not built a modern large application in decades.
Re: IBM to buy HashiCorp in $6.4B deal
#236Earlier quoted context omitted.
True but no company has a vested interest in the democratization of investment. IPOs are purely about getting paydays for founders.
*and early investors. Mostly early investors in many cases.
Re: IBM to buy HashiCorp in $6.4B deal
#237Earlier quoted context omitted.
I am not used to writing code where 2/3 of it is "if err" statements. Also, refactoring my logging statements so I could see the chain of events seemed like work I rarely had to do in other languages. It's a language the designers of which - with ALL due respect - clearly have not built a modern large application in decades.
I understand were you are coming from but I actually like the explicit error handling in Golang. Things being explicit reduces complexity for me a lot and I find it easier to spot and resolve potential issues. It's definitely something that I can understand not working for everyone. I agree on the logging point but my experience was the explicit error handling and with good test coverage meant we rarely got into situ…
This sound a lot of like Apple user arguments about iPhone 1 missing copy & paste over a decade ago.
I am very pedantic about checking responses for errors, but from my experience when working with a team and existing project I see that people notoriously forget to check the result. TBH it is a pain to essentially repeating the boilerplate `if err !=nil ...`.
What's worse is that even documentation skips checks. For example `Close()` method. It's almost always returning error, but I almost never seen anyone check it.
The reason for it, is if you want to use `defer` (which most people do) you would end up with very ugly code.
The other alternative would be to then making sure you place (and properly handle error) close in multiple places (but then you risk of missing a place).
And other solution would be using `goto` in similar way as it is used in Linux Kernel, but there are people who have big problem with it. I had a boss who religiously was against goto (who did not seem to understand Dijkstra's argument), and asked me to remove it even though it made the code more readable.
Re: IBM to buy HashiCorp in $6.4B deal
#238I didn't know IBM still had money to throw around like that. What do they even do these days? Who are their customers?
If you're a shipyard, an oil company, a bank, an automaker, etc. you still need software to manage things like inventory, employees, logistics, and similar, and you have zero expertise to do it in-house. They also have zero expertise to find a qualified vendor.
IBM is a safe bet.
That's a huge market.
Re: IBM to buy HashiCorp in $6.4B deal
#239Community fork https://opentofu.org/
Indeed. Owned by The Linux Foundation, so this will remain OSS forever/no rug pulls are possible.
"Linux Foundation joins IBM to accelerate the mission of multi-cloud automation and bring the products to a broader audience of users and customers." ;)
Re: IBM to buy HashiCorp in $6.4B deal
#240Earlier quoted context omitted.
Yes. And many of the Heroku employees you speak of would have got RSUs that owed taxes on an $80 basis, been trading far below that for most of that time, and now have a maximum expected value of $35. This is not a pay day for many people. Anybody who got a pay day were those that could liquidate in the IPO.
Yeah okay, if you had 0.15% stock you're still out with $ 10M. Smaller and bigger percentages will be different but that's retirement money for hundreds and hundreds unless you pretend to live in very high CoL area. Also, most of them will likely have to keep working thereyears before cashing out some other millions likely.
There are many many people who made a loss on this, even before the acquisition announcement.
Also I think your ownership % is way off. There's a pretty small group of people, most of them the earliest employees + execs, who would have got out with $10M. HashiCorp currently has thousands of employees and would have churned through thousands more over the years.