667: The Enterprise Endgame

Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.

My name is Wes.

And my name is Brent.

Hello, gentlemen. Well, coming up on the show today, the three major themes from Red Hat Summit that we think you'll care about the most. Then we'll round the show out with some great boos, some picks, and a lot more. So before we get to all of that, and it is a dense episode, let's say time-appropriate greetings to our virtual lug. Hello, mumble room. Hello. And hello up there in quiet listening. Hello, everybody in the live matrix room and on the stream.

The prs.

Are out in the open.

And it's kind of stupid easy to try especially i mean it's just written in go you can just download a binary that basically runs anywhere all the way to like you know using containers or nix os or whatever you want to orchestrate it or a managed product.

Make a site car.

Do it yeah.

And if you want to try it out define.net slash unplug it just started with managed nebula you can try for free 100 hosts no credit card required it's a great way to support the show and i think one of the things you'll really appreciate is that you can run your own Lighthouse nodes. You're going to really notice a difference on CPU and network overhead compared to other mesh networks. And I think you'll be hearing more about just how freaking fast Nebula really is. It's amazing.

Well, based on last week's adventures with a new distro, let's call it, where I didn't quite do as well, I dove into Red Hat Summit, which is happening this week. Red Hat Summit 2026 is happening in Hotlanta, Georgia. And, well, we grabbed a whole bunch of clips, especially on day one, which was rather high level. But useful to understand where Red Hats, well, where their head is at. And before they started talking about AI, as everyone does, they wanted to make it clear they see you.

Welcome to Red Hat Summit 2026. Please welcome Red Hat President and Chief Executive Officer, Matt Hicks. Good morning. Look at this crowd. Every one of you is responsible for something that cannot break, cannot go down, cannot be wrong.

I think Red Hat has been reading the room. And they realize the importance of getting out in front of this and saying, it's really about you. Everything we're going to do today, it's AI, but it's about you.

Yeah, this is targeted at humans, at the folks that are actually coming here, or at least that are continuing to motivate their bosses to pay our bills.

But Brent, you get the sense, like, if this is how they're starting, because that was like the start. If this is how they're starting, they're going in hard, I would imagine.

Yeah, on the scene, I've been basically just hearing them talking about how this transition to AI is one of the major defining moments in the tech industry.

What is the foundation that lets me compete at the speed that my business needs while not breaking what absolutely cannot be broken? My business. And I've seen this before, twice actually, both times in ways that fundamentally reshaped the industry. The first time was in the shift from proprietary hardware and proprietary operating systems to open infrastructure. To that question, the what do I build on question, the answer turned out to be Linux.

And as you can imagine, he mentioned the future of work being agentic there, which means the kind of work we're going to be doing is going to change.

Here is what we learned about the process, the actual work. And I want to be direct on this. To these software developers in the room, You are not getting replaced by AI, but where you spend your time and energy will drastically change. Figuring out how to build and shape evaluations for these AI-created systems. Figuring out how to build the next generation of continuous integration systems in a world where anyone can contribute.

The overall message was pretty clear in the room that even if it makes you anxious, as it does many of us, or gets you excited, Red Hat says AI is not optional.

AI isn't optional at this point. Whether it brings you energy or whether it creates real uncertainty. And I think for many of us, it is a combination, a mixture of both. it can't be ignored. But there also isn't a single path. Some of you might be ready to run AI or are in production. Some of you might be just trying to figure out what is hype and what is reality at this point. And some of you might be just trying to get your infrastructure in order to even make this a reality.

All right, so that I'd say is theme one. And I noticed that Red Hat was leaning pretty hard on stuff that they've implemented. They talked a lot about how 85% of their internal knowledge workload bases on self-hosted models.

Yeah, that was an interesting step.

Yeah, so that's nice to see. And they've been really working to optimize smaller models to make them practical.

And we know they've been heavily involved with VLLM, which is like the major way that a lot of these models are served both commercially and if you're going to go about doing it with like real powerful GPUs for your own internal use.

Yeah, they definitely are.

And LLMD on top of that.

They're very proud of being, you know, the core, one of the top contributors, the top contributor to VLM and the partnership there. Okay, so that's theme one. Theme two, we've got to talk about, Brent. RHEL forever.

RHEL forever. On day two, we got the news that Red Hat Enterprise Linux was turning into forever distro with RHEL forever.

I need to run that version of RHEL forever without a hint of sarcasm. And for that, we're announcing Red Hat Enterprise Linux long-life add-on. A yearly subscription with indefinite support once you reach the end of extended support. Critical security fixes, bug resolutions, and more for as long as you need them. When you have a system that cannot change, you need support that will not end.

To me, this is kind of a remarkable announcement.

Yeah.

The engineering task.

There's something to be said for LTS, which is, you know, I've been around for a while, long-term support, but this is literally indefinite. That word really stuck out to me. How in the world do you do that?

I do think it's important to recognize that they do have some internal guardrails. It's at Red Hat's discretion. They include that a lot.

Yes.

Smart.

Yeah. And so I do think there's an aspect of some long-term bets on maybe how they're able to keep accomplishing this. But I also wonder if there isn't a connection to what we're going to talk about next in terms of new offerings they'll be able to push to a lot of their current clients.

Yeah. Yeah, I can see that. So you touched on something there. Do you think, so let's look at the alternative. So Canonical offers 15 years contractually on Ubuntu Pro Legacy. SUSE does 16 years for core components. Red Hat, indefinite, is a lot longer than any of those. Although I'd say Canonical's scope is a lot broader because under Canonical's 15 years, it's all 36,000 packages in the main archive.

Right, this is continued access to critical software security and bug fixes. Yeah.

Where the Red Hat version, like you implied there, is going to be a lot narrower to which we don't even know the degree of that scope yet. Or the pricing.

You do have to wonder, though, like you're saying, there has been some developments with other folks in the space bumping up timelines. So maybe this is a like, you don't, you know, if you're worried about that, we are going to let you keep paying and we will let you keep running this.

They even said at one point 30 years.

Wow. But even just Canonical's offering at 15 years was just a huge jump from what they were doing a couple of years ago. what were you know what was the state of linux 15 years ago chris when uh oh my gosh right if you picture it that way it's like wow well 15 years.

I wonder if there's a bet there too in terms of like because i think some of this starts with six ah i wonder if there's like a baseline they think they've achieved in terms of like how much will change maybe you have enough of the primitives enough se linux enough maybe basic container tech in there but.

Even on a say Let's just say it's not 30 years. Let's say it's a 20-year. First, it's a bet the Red Hat will be there that long, but they plan to be here indefinitely apparently. But at 20 years, it just becomes exponentially harder to take a modern-day security fix and apply it to something like the 6-series kernel when we could be on a 10-series kernel by then or something like that.

I think that comes into play, I think especially maybe in sort of countering perhaps an expected increase in things that you need to address, right? We've seen – we don't know if it will continue, but we've seen – it's been a very busy month in Linux security vulnerability.

Pause there for a second, buddy. That's a huge point. They are making this commitment as the CVE are exponentially going up, and they're like zero-daying them just to get attention. And they're like, yep, indefinite support at the beginning of this curve.

So that's where I think it also maybe reflects. So I think maybe they think, you know, we will also have tools to help make this process more sustainable and be more highly automatable to address that and, you know, tamp down some of the growth on that curve. And then maybe also some confidence in their existing execution and team and sort of security profile.

It's true.

So I think they have a lot of the bones in place. And then maybe because as we've seen, they are kind of whole hog going forward to use AI tooling. Maybe they've already seen some gains in that regard.

Right. And the plan here is you go through all the standard lifecycle, then the extended lifecycle, then the premium extended lifecycle, and then indefinite. And so you have to also imagine the pricing escalates with each one of those tiers.

Right. And so that's, I think, where the discretion and the like how much you extract sort of comes in in terms of they retain the option to make this worth their while if they need to.

I just want to take a moment and thank our members. We would normally have an ad right here. We should have had an ad right here since the beginning of the year. And since then, our members have been keeping us on the road. LinuxUnplugged.com slash membership for this here program or Jupiter.party for all the shows.

Also, during day two's keynote, we got the Hummingbird announcement. They start by saying, from the same factory that creates RHEL-hardened images, is how they will create Hummingbird.

Of a new builder-focused Linux distribution, Fedora Hummingbird Linux, a rolling release OS that pushes updates and fixes as quickly as the upstream Linux community produces them. So it's built on the same automated infrastructure as Red Hat Hard Images, And because of that, Fedora Hummingbird Linux will provide languages, runtimes, databases, and tools, also free of non-CVEs. This allows AI agents to choose Fedora Hummingbird Linux as the OS to experiment with.

I guess I'm struck by a couple of things with Hummingbird, and I want to start with this. How do you have a zero CVE Linux distribution?

Yeah, so it's less of a claim forever, but the point is really about process, which is it's very much an automation sort of CI, CD first thing. In this case, it's built on Conflux and Tecton and some of the existing infrastructure that Red Hat has been working on. But the idea is, you know, you have a minimal package set or total software set inside the image and you build it frequently often. And as part of that, you use tools like SIFT and Gripe to actually get reports,

And you can do it quickly.

Yes.

You can do it frequently. I see.

Yeah. And then you can even tie it into upstream vulnerability reports, right? So, like, if a vulnerability is patched upstream, you can, the pipeline will be looking for that, rebuild, test it, and then push an updated image.

This, to me, sort of smells like they're going after chain guards territory.

Yeah, very similar.

Hmm. That's interesting. Now ChainGuard is a direct competitor with Red Hat.

And we've seen as sort of there has been more pressure in terms of like compliance and audits on like what is the software that you're running. That's put more pressure on. I mean, once you start producing that information, you see that like, oh, we are running a bunch of stuff in these images that maybe never even needs to be there at runtime, but just sort of ends up because it has you, you know, if you just use standard sort of base images, you kind of have to strip that stuff out.

Vendor-required RHEL standard images. And I think that's the key competing differentiator that Red Hat has going for them versus Chain Guard is Chain Guard is using their own custom distro, kind of Alpine style APK formats and all of that, where this is going to be a Fedora, you know, Red Hat base.

What is kind of neat about that from this perspective is it is kind of classically more of an enterprise offering, right? And like Red Hat does have Red Hat hardened images and that kind of stuff that they offer at that. But this is more on the open side. This is something that can be given to anyone who's happy to run stuff built from Fedora Rawhide, which that's us, right?

Yeah, and you could even boot it with a base image, right? Like, I don't believe Chain Guard actually has a bootable Linux distro.

Right, so this also gets to take advantage of all the very cool work happening with Bootsy.

Yeah.

That's neat.

However, there has been some community backlash. In fact, the discourse thread that we'll link to in the show notes is still rolling. And there's a certain pattern to it. It seems people are feeling like this is sent off stream all over again. There was a Red Hat business decision that was pre-announced as a Fedora deliverable with kind of a fig leaf community consultation. That's a quote from one of their members.

Yeah, there's feelings kind of like there was some engagement around. Maybe we want to explore bringing this into Fedora.

Hey, we're thinking about this.

And then sort of it gets announced on stage, and it's like a done deal, and it's happening.

Two weeks later, Fedora's doing this new thing. And they're like, wait, Fedora's doing what? We had no idea. And some of the deliverables require some maybe different staffing. They require some discussion here. And, you know, Red Hat wanted a big, splashy announcement for Summit. And Fedora wants to do things the most open way, following their community guidelines and all of that. And the two are sometimes... not compatible. And I thought some of the key quotes put it pretty well.

Wow. Frankly, that article sounds hostile to me. It's basically claiming to be Fedora Linux. Then again, that it is not, but that it is as secure as opposed to everything else with curated kernel config and elaborate engineering framework, a whole blank load of sales pitch. So what is it? Fedora or not Fedora? There might even be some good ideas in there, but given how this started and how it is communicated, I can put zero trust in this.

Yeah. Matthew Miller, former project leader, chimed in, quote, as a former project leader, I know that there's always a tension between transparency and Red Hat's business and marketing desire to have a splashy, exciting announcement at Summit. Once that's settled down, the real work can start.

It is a good perspective in that this is not the first time there's been some version of this in terms of a clash between a strong community distro that is very much a part and often funded by a proprietary business that has its own needs and timelines.

Yeah. And then there's this adjacent announcement. It's a separate announcement, but it's kind of feeling in the same groove, is a Fedora AI developer desktop. And Fedora is considering an initiative that they might call the Fedora AI developer desktop that would be a spin of the Atomic desktop with some AI tooling built in. The goal here, they say, is to make an AI development on Fedora less painful

Boy, has it. As it should, I would imagine. This is a large topic.

Yeah. Where do we even start with this? Because the reaction to this is quite bad. The Fedora community is concerned with what has been promised as a deliverable. Things like an LTS kernel. The current Fedora kernel maintainer doesn't really even have the time to maintain the kernel Fedora, let alone take on an LTS project, which is sort of antithetical to Fedora in the first part.

Yeah i think the like it there is some interest in it and there's some discussion of maybe could this be like a like a spin or a remake like could there be a different form of like how it fits yeah uh-huh um but it does come in kind of clash with both uh policies and philosophies perhaps in terms of like do we even allow shipping you know these out-of-tree kernel modules um but then also just with existing constraints in terms of like you know fedora's kind

I think there's also an issue here where now they have this ability to ship some of the invidious stuff but that would technically taint the kernel which fedor classically i mean this is one of the reasons linus likes to use it as a clean kernel.

Buddy of the show neil gampa has been involved in the discussion kind of brings up that there's value to the reputation in the kernel and fedora often works with stuff like they work with the upstream butterfs developers and the upstream kernel developers really like knowing that fedora ships this really clean kernel and so when they get reports from those systems they can trust them and use them for debugging so.

There's also a couple of uncomfortable tensions here and brent i don't know i don't if you have any thoughts feel free to to, does Fedora need to respond to this moment? One of the arguments that I've seen made is that there's really no evidence that people are passing over Fedora because they don't have an AI spin right now. And I wonder, is that a valid argument?

Hmm. Well, I mean, in our episode about Ubuntu recently, we heard that they're making strides to make this easier. So one could argue that any distribution that wants to stay relevant will at least have to look at this as a possibility for the future of how computers will be used. I mean, that's one of the arguments we've heard.

I would say anyone who's ever argued that you should use Discord to reach the youngs should also be in favor of this. Because this would be one of the arguments. If you want to reach the youngs, you need to be where the youngs are at.

100%.

And that's the argument for people to throw away their open source hard line when it comes to chat platforms and use Discord. So it would be interesting to see some of those Discord stands try to argue against this.

But I think the bigger question that the community is bringing up here is whether Fedora is the right place to do this.

Yeah.

And I think overwhelmingly we're seeing that maybe that answer is no. So is Red Hat pushing this in the wrong place, perhaps?

I don't know, because I think if you look at some of the comments by Jeff Spolita, that there's... I think he's quite eloquently sort of expressed this, what Chris was saying, in terms of like... He worries a lot about how do you attract the people who he was when he joined Fedora. And that those folks are just using, to some degree, lesser and more, these tools, because these tools are kind of just normal as they learn how to interface.

They're not on IRC chat rooms anymore. Right.

And so... And then it kind of comes also to an issue we've discussed on the show before, which is if the folks involved in the discussion do value the philosophies and attitudes and ethics of Fedora and its community, if they're not in the discussion with these tools, then those values really don't get representation.

Like what's the Fedora implementation of these ideas? I like that.

And when the Fedora implements something, does that philosophy sometimes carry through to some of the users and how they use the technology and the choices they make? And if it does, then Fedora probably does want to be there. So my thoughts on this are complicated because a couple of things jumped out at me. reading through this thread. And I do think maybe a Fedora LTS kernel would be kind of a cool idea. I may actually end up, you know, reconcerting Fedora for a few other tasks.

But I think the Bluefin folks, you blue folks have a LTS kernel.

But I think if you step back and we're just going to try to steel man this and you put a business hat on and pretend like you're a CEO or some executive at Red Hat and you try to look at the macro picture, I wonder if these types of discussions won't bring in the beginning of the end of a traditional distribution model like this free software project attached to a large corporate sponsor. Because think about it this way.

You can imagine it being seen as a cost, right?

Yeah, it's slowing things down, and there's no time to spare.

It's an externality we have to manage that we don't fully control.

And they're going to be thinking, right or wrong, they're going to be thinking, well, we're in the age of AI. Somebody could just vibe code a replacement for something that we offer. A competitor can come along and start building and shipping at light speed. We have got to move. And maybe somebody like a chain guard or somebody is out there eating market share and you're still negotiating with the factory workers on a discussion forum.

I think it's a stress test for that relationship and for their long-term values and if those are something that they're willing to accept this tradeoff for or not.

It just feels like that's really what's at play here and the stakes couldn't be higher with this one particular example. There's just so much.

It's showing up in these couple of ways, but there's more cooking underneath, yeah.

Well, thank you to everybody who supports the show with a boost. That direct contribution goes to all of us, plus Editor Drew and the creator of your podcast app. And if you boost above 2,000 sats, you get your message read on the air. So it's a way to get a message in, send us some feedback, and support the show at the same time. All of it sent over a peer-to-peer free software network. The entire stack is

Well, Rich was thinking about us this week, writing in twice. Rich is asking how Chris plans to update his Hypervibe configs for Hyperland 0.55's new Lua-based configuration system. He's uncertain how the architectural shift will affect the Hypervibe setups already packaged inside RichArch. He notes that RichArch has already released an updated Hypervibe spin featuring Noctalia shell on Hyperland. But the Lua config migration may require further work to fully align with the

It is a big change for old Hyperland. It came out on May 9th, Hyperland 0.5. And the big, big thing in there, like Rich mentioned, is the config is now done in Lua. But you don't actually have your configs broken right away. There is a transition, and it's pretty easy to have both existing at the same time right now. But I'm actually surprised Rich asked this. You know, I wonder, how old is the old Hypervibe repo now?

Good question.

Do you have a guess?

A year? Yeah, no. Is it not that long? Maybe your project's been that long, but the repo's kind of...

What's the fastest way to tell? Just look at the commits or what? What's my...

Yeah, go see the oldest commit.

All right. Do I have to scroll down for that? Oh, gosh. It's going to be pages.

Oh, yeah. You've probably made a lot of commits.

It's going to be pages.

You might be able to go into the project analytics.

So what I was thinking...

Do I have it locally?

Oh, God. I'm only on February right now. I don't know how to tell.

Yeah, I got...

But what I was thinking about this is...

Initial commit, Sunday, August 10th, 2025. So not quite a year, but coming up.

Wow.

Do I win by Price is Right rules there?

It's a little bit blowing my noodle at this moment how much the tooling has changed and improved since I started this. Because what I created Hypervibe with feels archaic compared to what we can do now.

Totally.

If you were doing it today, would you even call it vibing, really?

No, I don't think so. No, because...

Because you're an agentic developer.

It'd be agentic, hyper agent... I don't know, agentic.

Hygentic?

There you go. Hygentic is good. But I'm surprised Rich is asking this because, of course, I'm just tasking the machine to just...

We'll convert it.

Convert to the new... And it worked well.

I will say, this has me a little more interested in Hyperland.

Oh, yeah?

Uh-huh.

Oh.

How come?

I like Lua, and it's a nice way to do it, I think, and, um... I'd like to try it.

So good decision?

It was the only gotcha I had is I had a custom script that set my monitor refresh rate once and then paused and then set it again because it was working around an old problem, which is no longer in Hyperland. And so I had to undo that. But otherwise, completely smooth transition.

You mean in your NixOS you had some initialization script?

No activation scripts at all.

No, not me. We also got another email from you.

You've turned that. Activation script concept into an entire operating system.

Yeah, one day I'm just going to bake it all into one Go binary.

Well, Rich also wrote in the next day saying that they caught the Red Hat Summit. Well, they actually caught the Red Hat Summit, unlike your dear Brent, and dropped a quick field report. The vendor expo floor was dominated by AI and OpenShift demos. Red Hat's two biggest pushes right now, they say. And notably, Microsoft maintained a large booth presence, underscoring the still strong Microsoft and Red Hat partnership. Rich did keep the report brief, but the picture was quite clear.

Yeah, we knew it was going to be AI heavy. We weren't sure how hard they were going to lean into agents. And then they ended up calling agents the future of work. So they leaned in pretty hard. Appreciate the report. Anybody that ever goes to an event like this that wants to send us a report, even if it's an event that we're also monitoring or going to, we still like your report. And if you're going to be there, we always hope to be able to say hi, too.

More like Greg the Baller.

Boosting in memory of the van. You guys are killing it. I use OpenSense Firewall, and it does fail over perfectly. Oh. Well, that's very nice. Thank you, Greg. Have we ever heard from Greg before? Is he our first-time booster here? What's going on, boys?

I feel like we must have.

I believe we have.

I do believe Greg is in our Element chat, our Matrix chat, too.

Greg, thank you for being our baller booster. Just put this episode over the top this week, so I really do appreciate it. And, yeah, did he boost that memory, that van part from this morning? because the bootleg, let's just say the California repair has gone wrong in a way that I don't think anybody could have ever predicted or expected. And whatever you're assuming it could have been is not it. And it's worth the bootleg right there. Thank you, Greg. I really do appreciate that.

Landlocked Boosin with 25,000 cents.

All right.

Listening for a long time and finally set up Albie Hub with my own Bitcoin node.

Nice.

Keep up the truly great work.

Well done Thank you so much for taking the time to do that But also I hope you had a lot of fun It is a very good learning experience Well done, Landlocked Thank you very much.

Nyquist sent in a 5,000 set test boost for us And we will say success.

Received Thank you very much, Nyquist Always welcome to test with us.

Tomato and or tomato also boosted in with a total of 6,660 satoshis. Here's a little BSD challenge report. Couldn't find the time for the BSD challenge last week, so I did this week. It is not hammer time. I tried Dragonfly BSD, and I now see why disliking it is a meme among BSD users. I did get open BSD running, however. Daily driver level didn't try the sound, though. Everything in power user category of the challenge, too. So 23 points for me.

Nice.

Well done.

As for the question in the episode of why BSD, I think Wes was on the right track with that one. I'm a regular NetBSD user, and I've been since the 90s. Wow. It's well-designed, it's simple, and I understand all the parts of the system. I can read the source, find what I need, and change it easily. It rebuilds, even cross-compiled, easily and quickly.

I mean it's the same argument the anti-SystemD crowd uses and I still think SystemD is worth having, but I do like that there is an alternative, something that for people that don't want things to change.

To exist I think that was very well very well said.

Tomato it was, Tomato, I'm being a little cantankerous on purpose about it just to sort of poke the BSD folks. But it is the same argument the anti-SystemD crowd would make for going with DavWan or something like that.

Somebody got a horn in their back.

But, no. I think it's a good point, and I'm, you know, in that context, because we do have Linux and SystemD, and we do have those changes and that evolution, it is nice to have something that remains sort of, you learned it 10 years ago, and gosh darn it, if you want to type IP configure, whatever it is, you're going to get it. And you know what? but it's still going to be called ETH Zero, and it's going to stay that way. And that's how it's going to be, and I like that about it.

Nice to hear from Distro Stew.

It is. It is. Distro Stew's a good guy. I ran OpenBSD on a ThinkPad 20 years ago with Wi-Fi working. Back then, Linux and BSD were about as painful to use as each other. Yeah, I understand that. But I'm still using OpenSense on some of my routers.

Nice.

I revisited FreeBSD, and I do that from time to time, but I'm a developer and the experience has gotten worse over time for me.

Oh, no.

Most IDEs barely work and I need Docker for a bunch of my workflows. I think BSD has always been good for appliances or data centers, but it's only been backed more into a corner over the years. It continues to surprise me how little BSD has, and you're probably going to say evolve or change. I feel like it's a little bit of the Fedora thing. Like nobody's really using Fedora for AI workloads outside of core Red Hat customers.

Olmec comes in with 15,453 sats. first time booster hey yes nice well done double points because using my own albi hub.

Very impressed.

What is your view on Linux's MDADM or MDAdmin?

Got to ask a good question.

At work, we use hardware RAID in most of our servers. And in my experience, the RAID controllers often die faster than the disks themselves.

That has been, ironically, my observation as well. And I will state, I started life in IT as a RAID controller stand. Very big fan, battery-powered, had additional RAM on there, very precarious and particular about which one. And over the years, I have personally gone to completely trusting software RAID. I find it more flexible. I find it to be perfectly stable and reliable. I'm curious, your thought.

Yeah, he does continue here. However, the sysadmins are quite skeptical of software RAID.

A lot of traditional folks are.

Why do you think this is? P.S., defining a RAID setup via NixOS Disco works incredibly well.

Yeah, I have to say, especially, too, if you're going to deploy, like, a large ZFS pool in a RAID, you really just don't want hardware RAID in the mix. You want to let ZFS manage that whole stack, and it's going to probably do a better job than a RAID controller will. So I just think it's an older way of looking at things, and it shows you how these things change over time, but people get entrenched in a particular workflow.

I do think maybe you do have to watch out for things like if you needed RAID 5 and there's still the right hole problem. and there may be particular performance profiles or certain workloads or whatever that maybe there makes a case for. But I do think in this day and age, it behooves one to actually look because Linux has made great strides in that subsystem.

Yeah, it's not 100% black and white because there is different considerations and constraints when you're doing software RAID, just like there's a lot of different constraints and considerations when you're doing a hardware RAID. And you may not want to map them one-to-one. And so if you're a shop that only knows hardware RAID, it's probably going to be safer.

Or you have a particular need and a relationship with a vendor and you're well-supported, then that's a different situation than like, I'm not going to be able to afford to replace this hardware controller on demand and I'm worried about these disks maintaining this array long-term. That's a very different position.

Or you're trying to pitch like some large ZFS pool for your shop to have a huge storage of data on a ZFS array. and you you know you got the you know the folks that are trying to suggest you go hardware rate that's when you go hold on a second here hold on a second here well.

A dude is trying stuff by boosting six thousand seven hundred and sixty seven cents, Gen Z boost.

All right.

Do we have something for that? Do we have a Gen Z?

We have to work on that.

What would be a Gen Z boost? I'm not sure. You let me know.

Question. If we eventually get to the point where we have a legitimate local AI model that is broadly and privately helping people day to day to be able to infer, well, do inference with their computer, Do you see personal computers being equipped with GPUs for local inference in the long term? Or will there finally be a use for all those AI-ready processors?

I suspect.

Yeah, it seems like it'll probably be stuff like NPUs and, you know, various sorts of pieces of hardware. It may not be a full classical GPU necessarily.

We forget just 10, 15 years ago how many things on our computers were not hardware accelerated and all ran on the CPU.

No kidding.

And we have spent 10, 15 years building dedicated chips and co-processors or offloading things to the GPU. And now when you get your, you know, your internet phone or a standard laptop or PC, they've got stuff dedicated for H.264 processing and decoding and encoding. Like they've got stuff on there for all kinds of dedicated subjobs that just get dispatched to them. And I imagine that trend would just continue because it's the most probably cost effective and power efficient way. Maybe.

Yeah, I might need fuel, too, at this point. Again, see the bootleg, it is said.

It's bad. It's bad.

Magnolia Mayhem comes in with 6,300 sats.

Oh! Oh!

I don't have any fries to get back to, so here's a boost.

Thank you, sir. Thank you, sir. Another bootleg reference. Bootleg is coming in thick today. Thanks for the live boost, guys. Really, between the baller boost and the live boost, really putting it over from kind of a standard affair episode, maybe even not doing so well, to a really strong episode. It just takes a few people, and it makes really all the difference.

I do want to pull forward Moon and I boosted in 520 stats just because they're kind of having fun. You can tell timestamps on boosts after I made a comment that we added that picking up on the metadata when it's included. well, guess I have to boost 420 sats at minute 69.

That would be a whole new level of combo and a way to maybe do a discount combo is your boost amount combined with the time code. But you'd have to give us a hint. We're not going to just notice it automatically. But that could be a neat combination of numbers and tricks.

Well, I mean, it was 420 sats, so maybe it is at minute 69. I love this.

You know, maybe you double it or something. Okay, so there you go. Thank you, everybody who support us. Of course, folks also just turned on the SAT streaming and their podcasting 2.0 app that support it, and they streamed SATs as they listened. 18 people did that stacking us 29,186 SATs this week. When you combine that with our boosters, we had a grand total of 342,015 Satoshis. Not too bad at all. Thank you, everybody who supported the show with a boost.

Yeah, it's nice just because I think this is the kind of thing, if you are getting started or maybe using the Linux desktop a little more.

You just want to have. Get your AMA-RG on your framework.

Yeah, exactly.

Coming from your MacBook.

It feels well supported. It makes us feel like we know what we're doing. We're not stuck in, you know, 1995.

I go back to, as well, it's a good trend that we keep seeing these boutique, well-built, very purpose-focused apps because that was something that the Mac got 10, 20 years ago, and it started to slow down as the platform gets worse. And now isn't it interesting as those folks have come over to Linux and other people are now here to use these applications. We're starting to see that type of stuff show up.

Yeah, okay. So under the hood, there's the excellent VHS tool, which is, as they say, your CLI home video recorder. But essentially, write terminal GIFs as code. So you want a GIF of, like, something happened. Sorry, animated Jeff of something happening in your terminal, right? Maybe to demo changes to your product or some new feature you're adding or a workflow you're doing or the cool AI thing you built, whatever.

Oh, yeah. Definitely got to show that off. Everybody cares.

Well, I send you guys. I send you guys a fair amount of MP4s and GIFs.

I send it to you because you guys are the only people that care. Brent only barely cares.

Yeah, true, true. Okay, so great tool. So you kind of write it out, but they have this custom tape format, they call it, which is cute, and it's part of the name, right? But it's just like this custom sort of ad hoc format for them. Maybe you want to be able to use something more standard. So this is just sort of a YAML wrapper that's able to make...

It takes that .tape.

Well, no, it lets you write YAML, and then it turns it into the .tape and then uses VHS to render it. So you can just go straight from YAML to...

No, I'm following you totally.

This is not niche at all, guys. Not niche at all.

And so it's VHS that produces the Jeff.

That's correct.

Oh, my God. Okay, great. Thank you, Wes. What a great find.

And it sort of starts making sense if you go look at a .tape file, and then you look at... I mean, we know what a YAML file looks, but if you look at the example .yaml here in the repo, So you've got to see, like, if you just want to be able to list, it looks a lot more like something you'd see in CI, which is like a list of bash commands or whatever you're running in YAML that you're kind of used to reading rather than having to maybe adapt to an arbitrary format.

I'm looking forward to seeing a screencast from you soon. You know, I'm looking forward to it. So this next pick is pretty interesting. A entrepreneuring developer has managed to combine Wine staging with a series of patches and DLL files that have been modified to get a reproducible recipe for running Adobe Lightroom Creative Cloud on Linux. You get the full Creative Cloud desktop app working under Wine. You can sign into Creative Cloud. You can get cloud-synced photo library photos.

This is so wild.

The state of wine these days is just something else.

The Adobe tools coming, I mean, the next unlock is going to be Photoshop and then Premiere and then eventually After Effects. And once we get to After Effects...

What are the main things we hear about people not being able to move to Linux? One was gaming, solved, right? For the most part. Second was Adobe tools. Well, today, that sounds like that's solved. So we're running out of reasons. People can't just use Linux right now.

Unlock my mom has been using photoshop since 1.0 she got access to the beta i mean she was she was involved in a seattle graphics arts program when they called using photoshop and things like that they called it graphic arts yeah yeah and um our seattle institute of art had a program and they had a partnership with adobe and all of that that she was involved with so to say that she's been using photoshop for a little while is

Those tools yeah.

So she doesn't she continues year after year to have she has to buy a new mac and she eventually gets forced because of the deprecation of the os and the updates and so for her this would be such a massive massive unlock if i could move her to linux then all she has to maintain is a creative cloud subscription.

Yes i guess apple doesn't really offer anything like well forever do they no.

And the thing that strikes me is if if an individual with cloud code can do this then what's stopping adobe from doing this directly and just kind of going the valve route creating an adobe proton style compatibility layer, that then they just design their applications to run on top of yeah, We'll get on at Adobe. Like, let's start spending some money on this.

It's also kind of wild, just another reminder of how much at this point Linux is really becoming a Windows runtime.

Yeah. Yeah, really. Which is, I think, the ultimate future of Windows, inevitably.

If only Microsoft would realize it.

Yeah, they will one day, but it's going to take them a while. And, you know, I'm never going to use this. We're not going to use this. But it just seemed like a milestone to get a current Creative Cloud product, something like Lightroom, running on Linux.

Go see what you can port to Linux today. Well, not important, but, you know, hack together in mind today.

Yeah, tell us. We want to know. All right, that is everything.

See you next week. Same bad time, same bad station.

Wes Payne, you want to tell them about some pro tips? Metadata, things like that, transcripts.

Oh, yeah. Well, we've stuffed a whole bunch of extra features into our RSS feed. So maybe just go look at it because it's nice to look at on its own.

Can I tell you, if we were like corporate owned, we'd be saying it's the agentic ready podcast.

That's right. It sure is.

Because our chapters are in JSON. Our transcripts are plain text that any agent can ingest.

Point your MCPs our way.

Our podcast is more agentic ready than your buddy's podcast. That's for sure.

Cloud JSON chapters. That's cloud native chapters.

We'll never do that again. All right. Thank you so much for tuning in this week's episode.

Hybrid Cloud Transcripts.

Oh, yeah, thank you. We'll see you right back here next Tuesday. As in Sunday.