341–350 of 391 posts
Earlier quoted context omitted.
Considering IBM sided with the fork, I suspect it'll be reverted for most or all of Hashicorp's projects.
That is the kind of thing that could have been a kind of negotiation tactic for purchasing Hashicorp, not necessarily done in good faith.
Earlier quoted context omitted.
Huh, they won't get pay day if no one use their products. And there are plenty of examples of failed products. If people have idea and execution capability for sustainable progression they can very well try outside the valley. It is not like companies don't start outside valley.
which is why the majority of the startups fail and then a lucky unicorn comes and funds the next cycle. look at how many poor ideas got massive investment on the bet of payout; so many blockchain companies and none solved a real world problem. lots of potential investment in things that could have greatly helped many more people in the world, but instead invested into a technology looking for a problem.
Earlier quoted context omitted.
I assume you're talking about languages with exceptions when saying "other language just hide errors from the user." I think that's a gross over-simplification of exception-based error handling. I generally do prefer explicit, but there are plenty of cases where exceptions are clearly elegant and more understandable. My preference is a language like Elixir where most methods have an error-code returning version and a…
I've never gotten the explicit argument. Java checked exceptions are also part of the function signature/interface and nothing prevents one from making a language where all exceptions are checked then just doing try { maybeError := FunctionThrowingValueError() } catch (ValueError e) { // do stuff } I get at the end of the day it's all semantics, but personally I kinda like the error-specific syntax. If you want to do…
Earlier 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.
disagree. k8s is written in it just fine. plus, tons of other modern large applications in enterprise settings
Which kind of proves my point. Even Google struggled to write clean, idiomatic Go.
Earlier quoted context omitted.
> Something like the JSON version of Terraform that can be generated by different tools, but an open standard instead. God, please no. The worst thing about all these tools is the terrible formats they keep choosing. Given the directions we’ve (“cutting edge” programmers and server ops folks) chosen to go instead, leaving XML behind was a big mistake. I’d prefer something better, but yaml and json are so terrible tha…
You'd write in a language designed for humans, and that would get translated into a language for computers. In other words, JSON. What are your reasons for disliking JSON?
Hardly - it's a hack as a data-only subset of JavaScript, as a sibling comment mentions.
It has no support for comments (even though JavaScript does). No support for optimal trailing commas. No integers. No enums.
Earlier quoted context omitted.
It is more than IBM used to be a big name in areas where hackers would be expected to be. They have left all those behind though. there are lots of other companies that none of us would recognize that are big, but IBM is a name that we all know as once somewhat important who now are not.
Uhm, the term “hacker” in this context, is, itself, just a coded way of saying “cool developer in the same circles as me”. Again, HN users are in a bubble, and HN users think that they’re very trendy.
HN users are trendy. If you didn't grow up in the 1990s or before though you may not remember just how picked on this type of crowd was. Now while we are never exactly the "in" crowd, we are respected, being a "nerd" or "geek" is now an acceptable thing. We have come a long way and that is enough trendy enough for us.
Earlier quoted context omitted.
Hashicorp had a $14 billion IPO in Dec 2021 and was trading at ~$4.7 billion right before the acquisition announcement. At that point it doesn't matter what the company or its founders want or what their long term vision is. Shareholders are in charge and heads are going to roll if the price doesn't get back up quick by any means necessary.
Yet another example of why I think it's a mistake to take your company public. If I put in the work to build up a successful business, no way would I ever let it be turned into a machine that ignores long term health for the sake of making the stock price go up.
It's a mistake if you care about the long term health of a company. But... why should you?
Hashicorp had a great run, and contributed a lot of great open source products over the years. Today, their products have large user bases and healthy forks seem likely. The founders and early employees cash out, and it's a win for everybody involved.
Nothing lasts forever.
Earlier quoted context omitted.
Is the implication that we won’t be able to freely use ansible-playbook anymore, and/or development will end on the “freely” available one?
No, the implication is that Terraform will become prohibitively expensive to use. AAP has been around for a while, as Red Hat’s downstream of (iirc) AWX. It’s also quite pricey, like Terraform may become.
Official: https://newsroom.ibm.com/2024-04-24-IBM-to-Acquire-HashiCorp... Confirming what everybody knows, IBM views HashiCorp's products as Terraform, Vault, and some other shit.
But what about the dozens of us using Nomad and Vagrant?
Earlier 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.