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

391–400 of 407 posts

Re: IBM completes acquisition of HashiCorp

#391

Post by weiliddat »

jsk2600 wrote: post #299
lenkite wrote: post #245

Earlier quoted context omitted.

Things have changed back though - the CLI is hot again at-least amongst developers.

I find it ironic that we developers prefer to use CLI because it's quick, efficient, stable, etc., but what we then deliver to people as web apps is quite the opposite experience.

Easier to sell the initial impression for "modern" web apps (shiny, easy-to-learn, low-skill-ceiling) vs the actual performance of TUI/"desktop" apps (mundane, effortful-to-learn, higher skill ceiling).

Maybe someone has examples of web apps made for also a high skill ceiling?

I've heard Linear, Superhuman does something like that while maintaining a nice interface, but I've never used those

Re: IBM completes acquisition of HashiCorp

#392

Post by worthless-trash »

linuxftw wrote: post #301
worthless-trash wrote: post #184

Earlier quoted context omitted.

I have found the experience very different than what the OP's experience is. As you know the layoffs that happened were around the same time as the rest of the industry layoffs were happening (fashion firing), I don't feel like it had a significant effect on the culture. I am fully remote though, and have been for 15 years.

What part of my experience did you find different than your own? I said the day to day was mostly the same, minus the decrease in comp. I mostly was trying to articulate that the idea that IBM is going to 'super power' Hashicorp is not real, despite what IBM says. A lot of what was communicated during the acquisition process was how IBM was going to super power Red Hat and help Red Hat grow into an even larger entity…

> There are no resources and opportunities after being acquired by IBM.

Got promoted twice, once between teams. Went to multiple countries and I was in product security (cost center ) at the time.

> No matter what they tell you, your day to day will not improve.

I am down to a 40 hour work week, down from 50-60.

> Not long after I left, they laid off a bunch of staff.

I don't see any difference, corporate has laid off many different groups, I guess the only different to the mothership laid off people in the US so it hits closer to your home. I've seen layoffs in Support in phillipines, Documentation in Brisbane, Most of Singapore GLS/GPS.

The USA has always been insulated from the layoffs because execs find it harder to lay off people you meet in the corridors.

> A lot of what was communicated during the

> acquisition process was how IBM was going to super

> power Red Hat and help Red Hat grow into an even

> larger entity, and how Red Hat actually need IBM to

> survive.

Maybe this was in the US, most of the IBM briefing/cheerleading meetings were not held during the APAC timezone so I skipped them and prioritized high value work. I have always assumed that if I needed to know something my manager would tell me.

If i was getting let go, nothing I could do about it if I was already doing the work I was supposed to be doing.

Re: IBM completes acquisition of HashiCorp

#393

Post by JohnMakin »

nunez wrote: post #380
linuxftw wrote: post #303

Earlier quoted context omitted.

I find this statement to be technically correct, but practically untrue. Having worked in large terraform deployments using TFE, it's very easy for a resource to get deleted by mistake. Terraform's provider model is fundamentally broken. You cannot spin up a k8s server and then subsequently use the k8s modules to configure the server in the same workspace. You need a different workspace to import the outputs. The net…

I agree with you (this is something that OpenTofu is trying to fix), but the way I do k8s provisioning in Terraform is to have one module that brings up a cluster, another to print the cluster's Kubeconfig, then, finally, another to use the Kubeconfig to provision Kubernetes resources. It's not perfect but it gets the job done most of the time.

this is best practice. I couldnt imagine doing it any other way and would flatly refuse.

There are shortcomings in the kubernetes provider as well that make wanting to maintain that in one state file a nonstarter for me.

Re: IBM completes acquisition of HashiCorp

#394

Post by happymellon »

carlwgeorge wrote: post #374
happymellon wrote: post #251

Earlier quoted context omitted.

But CentOS Stream is not CentOS. They are completely different products just reusing branding to confuse what people are asking for. RHEL Developer is closer, as a no-support, no-cost version of RHEL, but you still have the deal with the licence song and dance. CentOS gave folks a free version that let you run some dev environments that mostly mirrors prod, without worrying about licences or support. CentOS stream do…

To call it "completely different" is false. They are built differently, but the end result is still 90-95% the same software versions (because it has to be as the major version of RHEL). In fact, the way it is built differently is a massive improvement over the old process. The old CentOS was put together by 2-4 people at a time, with long delays after the corresponding RHEL releases, with no ability to actually fix…

It is different, otherwise why would then explain at length at how it is better?

Re: IBM completes acquisition of HashiCorp

#395

Post by iwontberude »

esseph wrote: post #191
iwontberude wrote: post #178

Earlier quoted context omitted.

RHEL has had no significant investment to keep it from becoming irrelevant in the next five years. The datacenter and deployments of linux have changed so rapidly (mostly due to the new centralization and homogeneity of infrastructure investment) that RHELs niche is rapidly shrinking.

This is clearly someone that is not paying attention to what Red Hat is doing. RHEL is the enterprise gold standard. Fedora is a lot of the pipeline for it, which itself has become an incredible server and desktop platform. All the work with Open shift, backstage, podman / qubelet, etc. They're going to be fine, from my graybeard position.

Yes also a gray beard and been around long enough to tell you RHEL is and will continue to be legacy and will continue to dwindle into obsolescence. You mentioned the cool stuff Fedora is doing, that is not RHEL. CoreOS is the future.

Re: IBM completes acquisition of HashiCorp

#396

Post by regularfry »

anonfordays wrote: post #332
regularfry wrote: post #331

Earlier quoted context omitted.

Defaults matter. I don't know how else to express that a system which fails safe in the face of fallible humans is strictly better , all else being equal, than the alternative.

That is the default. Terraform fails safe by not deleting your databases on a whim, it asks for manual confirmation by default.

Unless the resource disappears unexpectedly from the config, in which case it gets deleted. That's the issue.

Re: IBM completes acquisition of HashiCorp

#397

Post by esseph »

iwontberude wrote: post #395
esseph wrote: post #191

Earlier quoted context omitted.

This is clearly someone that is not paying attention to what Red Hat is doing. RHEL is the enterprise gold standard. Fedora is a lot of the pipeline for it, which itself has become an incredible server and desktop platform. All the work with Open shift, backstage, podman / qubelet, etc. They're going to be fine, from my graybeard position.

Yes also a gray beard and been around long enough to tell you RHEL is and will continue to be legacy and will continue to dwindle into obsolescence. You mentioned the cool stuff Fedora is doing, that is not RHEL. CoreOS is the future.

RedHat developers are the ones making Fedora.

Fedora is the upstream for RHEL.

You are going to see RHEL transition to bootc: https://docs.fedoraproject.org/en-US/bootc/

Get with the times, fellow gray beard: https://github.com/redhat-cop/redhat-image-mode-demo

---

* What is RHEL Image Mode?

RHEL Image mode is a new approach for operating system deployment that enables users to create, deploy and manage Red Hat Enterprise Linux as a bootc container image.

This approach simplifies operations across the enterprise, allowing developers, operations teams and solution providers to use the same container-native tools and techniques to manage everything from applications to the underlying OS.

* How is RHEL Image Mode different?

Due to the container-oriented nature, RHEL Image mode opens up to a unification and standardization of OS management and deployment, allowing the integration with existing CI/CD workflows and/or GitOps, reducing complexity.

RHEL Image mode also helps increasing security as the content, updates and patches are predictable and atomic, preventing manual modification of core services, packages and applications for a guaranteed consistency at scale. ---

Re: IBM completes acquisition of HashiCorp

#398

Post by adastra22 »

ghaff wrote: post #370
adastra22 wrote: post #369

Earlier quoted context omitted.

There are many large organizations that pay for RHEL support. Supercomputers, for example. These organizations also benefited from being able to spin up analog installs of CentOS on local machines for testing. Not anymore. I expect RHEL's market dominance in these areas to diminish over time.

HPC was always a tough sales area for Red Hat and RHEL. In general, while RHEL is obviously still an important revenue source, there's also a lot of focus on OpenShift going forward which has done of pretty good job of covering (and more) inevitable RHEL declines moving forward.

All the HPC I've used in the past was always RHEL... I wouldn't have imagined it was a tough sales area for RedHat, at least in the past.

Re: IBM completes acquisition of HashiCorp

#399

Post by adastra22 »

carlwgeorge wrote: post #373
adastra22 wrote: post #369

Earlier quoted context omitted.

There are many large organizations that pay for RHEL support. Supercomputers, for example. These organizations also benefited from being able to spin up analog installs of CentOS on local machines for testing. Not anymore. I expect RHEL's market dominance in these areas to diminish over time.

For testing environments Red Hat will literally give them free RHEL. Problem solved.

No, they won't. I'm talking about the users of HPC centers, not the maintainers. The supercomputer cluster is at NASA or DoE and running RHEL, but the user is some grad student in Caltech or whatever. The grad student needs the analog environment to run their code before their scheduled time on the big iron.

Re: IBM completes acquisition of HashiCorp

#400

Post by iwontberude »

esseph wrote: post #397
iwontberude wrote: post #395

Earlier quoted context omitted.

Yes also a gray beard and been around long enough to tell you RHEL is and will continue to be legacy and will continue to dwindle into obsolescence. You mentioned the cool stuff Fedora is doing, that is not RHEL. CoreOS is the future.

RedHat developers are the ones making Fedora. Fedora is the upstream for RHEL. You are going to see RHEL transition to bootc: https://docs.fedoraproject.org/en-US/bootc/ Get with the times, fellow gray beard: https://github.com/redhat-cop/redhat-image-mode-demo --- * What is RHEL Image Mode? RHEL Image mode is a new approach for operating system deployment that enables users to create, deploy and manage Red Hat Enter…

I know all of this already and honestly I’m just amused at how long it has taken. Forget I said anything. Enjoy working on rhel for the rest of your life.
Post reply on HN