Podcasts about Oxide

Extra-Vitamine selten notwendig, Kräuter nicht als DauergabeZehn verschiedene Töpfe im Stall sind gar nicht notwendig, manche Futtermittelzusätze im schlimmsten Fall schädlich. HBD-Futtermittelcoach @AnjaBeifuss warn etwa vor einer Überdosierung von Selen oder Kupfer. In dieser Podcastfolge AUF TRAB beschreibt sie, wie artgerechte und gesunde Fütterung bei Pferden aussehen kann. Die Basis jeder Pferdernährung ist das Heu, soll heißen mindestens  zwei Kilo Heu pro 100 kg Körpergewicht pro Tagund das möglichst über 24 Stunden verteilt.  Fresspausen von über zwei Stunden sind ungesund, so wie allgemein zu wenig Heu den Magen und die Mikrobiome schädigt. Das sei auch die Crux an den automatisierten Raufen, die Pferden meist nur 2,5 Stunden Heu zur Verfügung stellen. Der Heumangel lässt sich hier leicht ausrechnen: Pferde fressen rund zwei Kilo Heu pro Stunde – für ein Großpferd sind 2,5 Stunden  Heu fressen somit zu wenig. Das Mikrobiom von gesunden Pferden könne mit ausreichend Heu  sowohl Vitamin-B-Komplex, als auch Vitamin C undBiotin selbst produzieren, so Anja Beifuss. Zufüttern macht nur Sinn bei Hochleistungssport, kranken Pferden oder Stoffwechselproblemen und da täte es oftmals auch ein günstiges Öl  aus dem Supermarkt.Mineralstoffe zufüttern sei hingegen unerlässlich, da durchden Klimawandel das Heu nicht mehr die Qualität von früher hat. Bei Mineralstoffen sollte man nicht sparen, sondern zu einem hochwertigen Komplett-Mineralfutter greifen. Wichtig sind 100 Prozent organisch gebundene Mineralstoffe (Chelate), keine anorganischen Sulfate und Oxide, selbstverständlich keine Zuckerzusätze und keine Getreideanteile. Was ich persönlich sehr spannend finde ist, dass die Futtermittel-Expertin vor regelmäßige Kräuterfütterung abrät. Zum einen helfen die Kräuter dann im Krankheitsfall nicht mehr. Zum anderen enthalten Kräuter Ätherische Öle, die die Darmschleimhaut reizen und damit die Allergiebereitschaft des Körpers erhöhen. Gesundheit geht jedenfalls durch den Magen. In diesem Sinne eine AUF TRAB-Podcast-Folge, die ihr nicht verpassen solltet. Viel Hörvergnügen wünschen Julia Kistner und ihre Welshies. Musik- und Soundrechte: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://auftrab.eu/index.php/musik-und-soundrechte/#pferdegrecht #füttern #Mineralstoffe #Vitamine #Mikrobiom #Darm #Kräuter #Allergien #Bewegung #podcast Foto: #AnjaBeifuss/Bearbeitung AUF TRAB

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

Oxide raised a truckload of capital a few weeks ago to fund the business for the foreseeable future. Bryan and Steve describe the raise, and Adam poses the best the best (and worst) questions scraped from Hacker News.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide CEO, Steve Tuck.Previously on Oxide and Friends:OxF s01e25 - Tales from the Bringup LabOxF s04e30 - Intel after GelsingerOxF s05e24 - Oxide's $100M Series BOxF s02e18 - Silicon Valley Bank with Eric VishriaOxF s05e28 - Systems Software in the LargeMentioned during the show:Oxide Blog: Our $200M Series COxide is hiring!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Bryan Cantrill, the co-founder and CTO of Oxide Computer company, speaks with host Jeremy Jung about challenges in deploying hardware on-premises at scale. They discuss the difficulty of building up Samsung data centers with off-the-shelf hardware, how vendors silently replace components that cause performance problems, and why AWS and Google build their own hardware. Bryan describes the security vulnerabilities and poor practices built into many baseboard management controllers, the purpose of a control plane, and his experiences building one in NodeJS while struggling with the runtime's future during his time at Joyent. He explains why Oxide chose to use Rust for its control plane and the OpenSolaris-based Illumos as the operating system for their vertically integrated rack-scale hardware, which is designed to help address a number of these key challenges. Brought to you by IEEE Computer Society and IEEE Software magazine.

Trevor discusses the latest updates from Ridgeline Minerals with CEO Chad Peters. The conversation covers recent drill results from the Swift project and the company's plans for 2026 drilling with Nevada Gold Mines. Additionally, they delve into the exploration target at the Selena project and its Oxide mineralization. Chad also discusses the progress on the Chinchilla sulfide area with partners South32.

This is a recap of the top 10 posts on Hacker News on February 10, 2026. This podcast was generated by wondercraft.ai (00:30): The Singularity will occur on a TuesdayOriginal post: https://news.ycombinator.com/item?id=46962996&utm_source=wondercraft_ai(01:57): Europe's $24T Breakup with Visa and Mastercard Has BegunOriginal post: https://news.ycombinator.com/item?id=46958399&utm_source=wondercraft_ai(03:25): Google Fulfilled ICE Subpoena Demanding Student Journalist Credit Card NumberOriginal post: https://news.ycombinator.com/item?id=46963804&utm_source=wondercraft_ai(04:52): I started programming when I was 7. I'm 50 now and the thing I loved has changedOriginal post: https://news.ycombinator.com/item?id=46960675&utm_source=wondercraft_ai(06:20): Oxide raises $200M Series COriginal post: https://news.ycombinator.com/item?id=46960036&utm_source=wondercraft_ai(07:47): Frontier AI agents violate ethical constraints 30–50% of time, pressured by KPIsOriginal post: https://news.ycombinator.com/item?id=46954920&utm_source=wondercraft_ai(09:15): Jury told that Meta, Google 'engineered addiction' at landmark US trialOriginal post: https://news.ycombinator.com/item?id=46959832&utm_source=wondercraft_ai(10:42): Ex-GitHub CEO launches a new developer platform for AI agentsOriginal post: https://news.ycombinator.com/item?id=46961345&utm_source=wondercraft_ai(12:10): Qwen-Image-2.0: Professional infographics, exquisite photorealismOriginal post: https://news.ycombinator.com/item?id=46957198&utm_source=wondercraft_ai(13:37): Rust implementation of Mistral's Voxtral Mini 4B Realtime runs in your browserOriginal post: https://news.ycombinator.com/item?id=46954136&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

Send us a textDr. Nathan Bryan was the first to describe nitrite and nitrate as indispensable nutrients required for optimal cardiovascular health. He was the first to demonstrate and discover an endocrine function of nitric oxide via the formation of S-nitrosoglutathione and inorganic nitrite.This technology is now validated in six published clinical trials. He is also a successful entrepreneur who has commercialized his nitric oxide technology through the formation of N1o1 (formerly Pneuma Nitric Oxide), whose products can be found on N1o1.com, and Amazon.Dr. Nathan Bryan has been involved in nitric oxide research for the past 18 years and has made many seminal discoveries in the field. These discoveries and findings have transformed the development of safe and effective functional bioactive natural products in the treatment and prevention of human disease and may provide the basis for new preventive or therapeutic strategies in many chronic diseases.Dr. Bryan has published a number of highly cited papers and books, including his latest book The Secret of Nitric Oxide—Bringing The Science To LifeFind Dr. Bryan at-https://n1o1.com/Amazon- The Secret of Nitric Oxide—Bringing The Science To LifeYT- Dr Nathan Bryan Nitric OxideFB- N1o1 by Pneuma Nitric OxideIG- N1o1 LifeFind Boundless Body at- myboundlessbody.com Book a session with us here!

What do LLMs mean for the future of software engineering? Will vibe-coded AI slop be the norm? Will software engineers simply be less in-demand? Rain and David join Bryan and Adam to discuss how rigorous use of LLMs can make for much more robust systems.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Rain Paharia, and David Crespo.Previously, on Oxide and Friends:OxF s03e08 – Does a GPT future need software engineersOxF s04e04 – HeliosOxF s05e28 – Systems Software in the LargeOxF s04e20 – Pragmatic LLM Usage with Nicholas CarliniSome of the topics we hit on, in the order that we hit them:The issue Bryan was fixingiddqd: the crate Rain builtGhosttyDavid's bugs: 1 2 3Rain's nextest bug: SIGTTOU when test spawns interactive shellOxide RFD 619: Managing types across Dropshot API versionsdrift: the crate Adam builtIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Time for the annual predictions episode! Bryan and Adam were joined by frequent future-ologists Simon Willison, Steve Klabnik, and Ian Grunert to review past predictions and peer into the future. If any of these predictions come to fruition, it's going to be an interest 1, 3, or 6 years!In addition to Bryan Cantrill and Adam Leventhal, speakers included Simon Willison, Steve Klabnik, and Ian Grunert.Previously on Oxide and Friends:OxF s04e02 – Open Source LLMs with Simon WillisonOxF s02e23 – Predictions 2022OxF s03e20 – Predictions 2023!OxF s04e01 – Predictions 2024!OxF s05e01 – Predictions 2025Predictions during the show:Adam1 year: AI companies go on an acquisition binge (especially for anything that smells like data)3 year: Crisis of AI slop open source (both projects and contributions)6 year: Jensen hands over the reins at Nvidia6 year: Tesla is out of the consumer car business6 year: With the iPhone market shrinking, Apple has several new attempts at the next potential flagship productBryan1 year: "Vibe coding" is out of the lexicon -- or used strictly pejoratively it becomes a named condition (for which Adam -- in an act of nomenclature genius rivaling The Leventhal Conundrum -- suggested "Deep Blue")1 year: A frontier model company has a prominent whitepaper making the case that AI will lead to broad-based prosperity rather than job loss1 year: Harvey.ai becomes the pets.com of the AI boom -- and a harbinger of the coming bust (which becomes known as a Correction-like euphemism)1 year: A prominent S1 has revalations of economic behavior that has an effect beyond the company's IPO3 year: Frontier models treat AGI as "already done" -- and ASI as a non-goal3 year: Custom-written software thrives in lieu of SaaS6 year: DSM adds LLMs as a substance that can induce psychosis6 year: $NVDA not beyond its November 2025 peakSimon1 year: The AI for programming holdouts are going to have a nasty shock1 year: We're going to solve sandboxing1 year: Our own challenger disaster with respect to coding agent security - see the Normalization of Deviance in AI by Johann Rehberger3 year: Something that seems impossible for a coding agent to build today - like a full working web browser - won't just be built by coding agents, it will be unsurprising3 year: We will find out if the Jevons paradox saves our careers as software engineers or not6 year: The number of people employed to type code into computers will drop to almost nothing - it will be like punch card operators. Those of us who write code today will have very different jobs that still build software and take advantage of our previous coding experience.Steve1 year: Agent Orchestration will still be a hot topic. It'll be partially, but not entirely, solved. Updated with some more rigour: We won't have a "kubernetes for agents" just yet.3 year: Using AI tools when writing software professionally will be considered something closer to using autocomplete or syntax highlighting than something controversial or exceptional.6 year: AI will not have caused the total collapse of our economic and governmental systems.If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers

Bryan and Adam reflect on Oxide and Friends in 2025--favorite moments, episodes, and images. Happy new year and see you in 2026!Your hosts are Bryan Cantrill and Adam Leventhal.Some of the topics we hit on, in the order that we hit them:RFD 576: Using LLMs at Oxide (hacker news comments)OxF: Oxide and Friends 6/2/2025 -- AI Discourse with Steve Klabnik (around 1:08:00)Shell Game podcastOxF s05e12 – Hell is other networks — April 4, 2025"No Egress" was a ChatGPT joke!OxF s05e33 – A Grown-up ZFS Data Corruption Bug — November 26, 2025Simpsons scene deleted in syndicationOxF s05e29 – AI in Higher Education with Michael Littman — October 17, 2025OxF s05e28 – Systems Software in the LargeOxF s05e18 – AI, Materials, and Fraud with Ben ShindelOxF s04e21 – Adventures in Data Corruption"Duck season, Fire!"MLG Airhorn aka "the jj airhorn"OxF s05e31 – FuturelockLaura's blog post: A disappearing Service ProcessorOxF s05e34 – Death by Uptime"Painfully concrete" - ChatGPTOxF s05e03 – Holistic Engineering with Robert MustacchiOxF s05e30 – RIP USENIX ATCTeam DTrace meets Dennis Richie, redux"Fart Boy"OxF s05e?? – Books in the Box V — The latest annual book recommendation episode.Oxide Bingo by John HollowayOxF s05e16 – Scaling ManufacturingOxF s05e22 – Founder vs. InvestorOxF s05e27 – Character LimitStretch goal for 2026: finally a C&DOxF s05e24 – Diving InBryan's blog: College Baseball, Venture Capital, and the Long MaybeOxF s03e31 – Hiring Processes with Gergely OroszOxF s04e06 – Crucible: The Oxide Storage Service"Don't worry, Alan, no one will listen" -> one of our most popular episodesOxF s04e23 – RFDs: The Backbone of OxideOffice Space: Michael Bolton as AI em-dash"This isn't nostalgia, it's epistemology" - ChatGPT"Weaponized weariness" - ChatGPT"Dry Fatalism" - ChatGPT"Cougar turned in his wings..."OxF s05e16 – Solutions Software Engineering with Matthew SanabriaAlexander Hamilton: amazing. Also the world's pre-eminent subtweeter and blogger?If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Programa especial Halloween. -Entrevistamos a Jorge Hidalgo donde nos desvela como ha ido el lanzamiento de Oxide Room 208 y muchos detalles más. -El Buhonero, Felipe nos trae mucho material al que poner el precio justo. -Grapas del pasado, José Ángel nos repasa la revista Nintendo Acción Nº10. -Now Playing, enseñamos nuestros juegos favoritos de terror.

George Ogilvie, President and CEO of Arizona Sonoran Copper (TSX:ASCU – OTCQX:ASCUF), joins us to outline the key metrics from the Pre-Feasibility Study (PFS) on the Cactus Project in Arizona and the envisioned mine plan.  We also get an exploration update, more clarity around the permitting process, discuss the recent capital raise, and review the pathway to production.   PFS Highlights include: Simple open pit / SXEW operation producing approximately 103,000 tonnes (226 million lbs) of estimated average annual copper cathodes over the first 10 years of mining, which would make Cactus the third largest cathode producer in the USA  Industry-leading capital intensity of $10,894 per tonne of copper cathodes produced $574 million of average annual EBITDA1  Strong economics to support the continued development of Cactus with a focus on simplicity and executability of the open pit copper cathode project, on private land in Arizona Cactus Project is well positioned over the 22-year Project Life of Mine (“LoM”) to generate value at a variety of copper prices: Conventional, Cost-effective Mining and Processing: Open-pit, Heap Leach and SXEW Operation with Oxide and Enriched Materials from Cactus and Parks/Salyer open pits over 22 years of processing Cash costs (C1) of $1.34/lb, All in Sustaining Costs (“AISC”) of $1.62/lb and All in Costs (“AIC”)1 of $2.01/lb Initial mineral reserves of 513 million tons at a grade of 0.52% Total Copper in the Proven and Probable category for 5.3 billion pounds of contained copper 65% conversion of leachable M&I mineral resources to mineral reserves, with increased grades reporting to the heap leach pads Significant benefits to the local community and economy of Arizona, including projected creation of an estimated 600+ direct jobs Future mine expansion opportunities outside of the current mineable copper reserves, including late mine life primary sulphides, Cactus East and other exploration targets Final investment decision as early as Q4 2026 with targeted first cathodes in 2029   George reviews how the incorporation of the newer MainSpring area into the larger Parks-Salyer deposit, over the last 2 years has allowed for a shift in strategy from underground mining over to an open-pit mining method.  They are reviewing moving the center of the open pit more towards the high-grade portion of the  Park-Salyer deposit, the infill drilling showed it expanding towards that direction, which presented better economics and a faster payback period, as outlined in the PFS.   George also provides some updates on permitting for the project, and the importance of it being on private land to help expedite the process, and that they should be submitting their applications later this year for administrative acceptance by early 2026, and then approval 6 months later.  This permitting process will time out well with the release of their Bankable Feasibility Study.     Next we discussed the news on December 2nd, which announced that the Company closed its previously announced private placement of common shares of the Company pursuant to which the Company issued, on a “bought deal” basis, 25,746,300 Common Shares, including 3,358,200 Common Shares granted to the underwriters, at a price of $3.35 per Common Share, for aggregate gross proceeds of C$86,250,105.  This gives the company the runway to execute on all coming workstreams heading into the Bankable Feasibility Study and the capital stack coming together for a construction decision late next year.         If you have any follow up questions for George about Arizona Sonoran, then please email us at Fleck@kereport.com  or Shad@kereport.com.   In full disclosure, Shad has a position in Arizona Sonoran Copper at the time of this recording and may chose to buy or sell shares at any time.   Click here to visit the Arizona Sonoran website to read over all the recent news.   For more market commentary & interview summaries, subscribe to our Substacks:   The KE Report: https://kereport.substack.com/ Shad's resource market commentary: https://excelsiorprosperity.substack.com/     Investment disclaimer: This content is for informational and educational purposes only and does not constitute investment advice, an offer, or a solicitation to buy or sell any security. Investing in equities and commodities involves risk, including the possible loss of principal. Do your own research and consult a licensed financial advisor before making any investment decisions. Guests and hosts may own shares in companies mentioned.    

This is a recap of the top 10 posts on Hacker News on December 07, 2025. This podcast was generated by wondercraft.ai (00:30): Using LLMs at OxideOriginal post: https://news.ycombinator.com/item?id=46178347&utm_source=wondercraft_ai(01:53): The state of Schleswig-Holstein is consistently relying on open sourceOriginal post: https://news.ycombinator.com/item?id=46181491&utm_source=wondercraft_ai(03:17): Over fifty new hallucinations in ICLR 2026 submissionsOriginal post: https://news.ycombinator.com/item?id=46181466&utm_source=wondercraft_ai(04:40): Google Titans architecture, helping AI have long-term memoryOriginal post: https://news.ycombinator.com/item?id=46181231&utm_source=wondercraft_ai(06:04): I failed to recreate the 1996 Space Jam website with ClaudeOriginal post: https://news.ycombinator.com/item?id=46183294&utm_source=wondercraft_ai(07:27): Z2 – Lithographically fabricated IC in a garage fabOriginal post: https://news.ycombinator.com/item?id=46178789&utm_source=wondercraft_ai(08:51): Dollar-stores overcharge customers while promising low pricesOriginal post: https://news.ycombinator.com/item?id=46181962&utm_source=wondercraft_ai(10:14): Trains cancelled over fake bridge collapse imageOriginal post: https://news.ycombinator.com/item?id=46178108&utm_source=wondercraft_ai(11:38): The C++ standard for the F-35 Fighter Jet [video]Original post: https://news.ycombinator.com/item?id=46183657&utm_source=wondercraft_ai(13:01): Discovering the indieweb with calm techOriginal post: https://news.ycombinator.com/item?id=46178892&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

We hit a new (and disturbing!) failure mode recently when a production rack that had been up for several months saw every (!) compute sled's service processor become simultaneously unresponsive. Bryan and Adam were joined by the members of the Oxide team who debugged the vexing issue -- and reached its surprising root cause.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues, Cliff Biffle, Matt Keeter, and Will Chandler.Previously, on Oxide and Friends:OxF s05e03 – Holistic Engineering with Robert MustacchiOxF s04e14 – Rebooting a datacenter: A decade laterOxF s01e26 – The Pragmatism of HubrisOxF s05e20 – Debugger-Driven Development (omdb)OxF s05e07 – Transparency in Hardware/Software InterfacesOxF s05e31 – FuturelockOxF s05e33 – A Grown-up ZFS Data Corruption BugSome of the topics we hit on, in the order that we hit them:hubris #2304: STM32H7 Ethernet driver stops yielding CPU after many packetsgist — Summarizing the Hubris side of investigationsMatt's blog: Hunting a spooky ethernet driver bugIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Hey hey! We recently tripped over a ZFS data corruption bug–introduced over 18 years ago! Bryan and Adam discuss with members of the Oxide team as well as Matt Ahrens, the co-inventor of ZFS.In addition to Bryan Cantrill and Adam Leventhal, speakers included Alan Hanson, Matt Keeter, Andy Fiddaman, James MacMahon, and special guest, Matt Ahrens.Previously, on Oxide and Friends:OxF s4e6 - Crucible: the Oxide Storage ServiceOxF s5e28 - Systems Software in the LargeSome of the topics we hit on, in the order that we hit them:ZFS fsync can trigger ZIL transaction reordering and data corruptionRFD 177: Implementation of Data Storagethe "fix" that introduced data corruptionPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Oxide founders, Bryan and Steve, as well as Oxide investor, Seth Winterroth, were joined by Liz Zalman and Jerry Neumann, authors of the book Founder vs. Investor, discussing the collaboration and conflict in company formation. Adam was also present.In addition to Bryan Cantrill and Adam Leventhal, our guests included Liz Zalman, Jerry Neumann, Seth Winterroth (Oxide investor), and Steve Tuck (Oxide founder / CEO).Some of the topics we hit on, in the order that we hit them:Founder vs. InvestorTopic[@M:SS](link into recording) Leventhal's ConundrumPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

We're big users of async Rust at Oxide, and recently we found (another) very odd and hard to debug pathology related to async Rust that we dubbed "Futurelock". Oxide engineers who diagnosed the problem join Bryan and Adam to describe Futurelock and discuss methods to identify and avoid it.In addition to Bryan Cantrill and Adam Leventhal, speakers included our Oxide colleagues Dave Pacheco, John Gallagher, Rain Paharia. Sean Klein, and Eliza Weisman.Previously, on Oxide and Friends:OxF s05e22 - When Async Attacks!OxF s05e26 - Technological Revolutions with Jerry NeumannSome of the topics we hit on, in the order that we hit them:Oxide RFD 609: FuturelockPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Revisiting an annual tradition--Books in the Box! Bryan, Adam, and the Oxide Friends share book recommendations (and--sometimes--anti-recommendations). Take a listen if you're looking for your next read.In addition to Bryan Cantrill and Adam Leventhal, we were joined by some guests noted below:Previously, on Oxide and Friends:OxF s05e06 - A Half‑Century of Silicon Valley with Randy ShoupOxF s05e26 - Technological Revolutions with Jerry NeumannOxF s04e03 - Fork in the Road for TerraformOxF s01e16 - The Books in the BoxOxF s02e18 - Books in the Box ReduxOxF s03e22 - Books in the Box IIIOxF s04e28 - Books in the Box IVOther Notes:Princeton Review: Happiest StudentsUMass Dining Named Best Campus Food by The Princeton ReviewCHM Oral HistoriesNight Rider (and K.I.T.T.)From Bryan and Adam (and others)The Mouse Driver ChroniclesFumbling the FutureSlingshotChip WarTechnological Revolutions and Financial Capital @bcantrill (economics book recommendation)Snow Crash (another Neal Stephenson book)The Big ShortReinventing The WheelEccentric Orbits (recommended by listener)Language Machines Cultural AI and the End of Remainder Humanism (recommended by listener)Molly White's **review ** of Read Write OwnCareless PeopleNOT A RECOMMENDATION If Anyone Builds It, Everyone Dies (If you are Molly White, please destroy this for us!)Surreal Numbers by Knuth (recommended by listeners)From Oliver HermanOpen CircuitsSystems PerformanceWhy We're Getting PoorerTermination ShockFrom Tom LyonFrom Airline Reservations to Sonic the HedgehogSee also Systems We Love: Life of an Airline FlightThe War of Don Emmanuel's Nether PartsThe NVIDIA WayFrom Dan McDonaldInventing the RenaissanceCharles Sumner: Conscience of a NationIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

LLMs have had a dramatic impact on education. There are obvious reasons for concern, but what about the less obvious opportunities afforded by LLMs? Bryan and Adam were joined by Michael Littman, professor at Brown University and Associate Provost for AI, to talk about his role advising the university on productive, innovative, creative uses for AI in higher education.In addition to Bryan Cantrill and Adam Leventhal, our special guest was Michael Littman.Previous, on Oxide and Friends:OxF s01e18 - Dijkstra's TweetstormOxF s04e02 - Open Source LLMs with Simon WillisonOxF s05e18 - AI, Materials, and Fraud with Ben ShindelSome of the topics we hit on, in the order that we hit them:Michael's home pageLeslie KaelblingComputing Up: Rich SuttonPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Bryan Cantrill and Steve Tuck, the co-founders of Oxide, are on the pod live (to tape) from the stage at OxCon. Jerod and I were invited to Oxide's annual internal conference to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. The best part was this on-stage discussion with Bryan and Steve. Enjoy!

Voices of Oxide on the pod! Cliff Biffle (engineer), Dave Pacheco (engineer), and Ben Leonard (designer) are on the show today. Jerod and I were invited to Oxide's annual internal conference called OxCon to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. Cliff Biffle is working on all Hubris and firmware. Cliff says "There's a lot that happens before the 'main CPU' can even power on." Dave Pacheco is leading the efforts on Oxide's "Update" system. And Ben Leonard in charge of all things brand and design at Oxide.

Voices of Oxide on the pod! Cliff Biffle (engineer), Dave Pacheco (engineer), and Ben Leonard (designer) are on the show today. Jerod and I were invited to Oxide's annual internal conference called OxCon to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. Cliff Biffle is working on all Hubris and firmware. Cliff says "There's a lot that happens before the 'main CPU' can even power on." Dave Pacheco is leading the efforts on Oxide's "Update" system. And Ben Leonard in charge of all things brand and design at Oxide.

Bryan Cantrill and Steve Tuck, the co-founders of Oxide, are on the pod live (to tape) from the stage at OxCon. Jerod and I were invited to Oxide's annual internal conference to meet the people and to hear the stories of what makes Oxide a truly special place to work right now. The best part was this on-stage discussion with Bryan and Steve. Enjoy!

Dave Pacheco is leading Oxide's multi-year effort around full-system update. He recently gave a talk about his experience leading that project, the complexities of designing the system and organizing the team. Dave, Bryan, and Adam discuss the project, the many sources of leadership, and the often underestimated peril of "organizational procrastination".In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleague, Dave Pacheco.Previously on OxF:OxF s05e21 - Rebooting a Datacenter: A Decade LaterOxF s01e09 - Agile + 20OxF s04e11 - A Baseball Startup with Paul Freedman and Bryan CarmelSome of the topics we hit on, in the order that we hit them:Dave's talk: Path to self-service update (slides)Fire trucks dousing the champion BallersBryan's talk: Debugging Under FireRoger Faulkner: "I'm not here to make it perfect; I'm here to make it better"Mid-recording earthquakeIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Bryan and Adam were joined by members of the Oxide manufacturing team to talk about all that goes into ramping up production, from people and processes to expanding the team and refining inefficiencies. It's a great problem to have!In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues, CJ Mendes, Kirstin Neira, Erik Anderson, Aaron Hartwig, and Doug Wibben.Previously on Oxide and Friends...OxF s03e20 - Tales from Manufacturing: Shipping Rack 1Some of the topics we hit on, in the order that we hit them:Topic[@M:SS](link into recording) Leventhal's ConundrumPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Jerry Neumann joined Bryan and Adam to discuss his blog post from 2015, examining the work of Carlota Perez on technological revolutions. These waves have similarities, in particular: frenzy, bust, and deployment. Is AI a new wave or the culmination of the IT wave of the last 50 years?In addition to Bryan Cantrill and Adam Leventhal, we were joined by special guest, Jerry Neumann.Some of the topics we hit on, in the order that we hit them:Jerry's 2015 blog post: The Deployment AgePRs needed!Previous episodes mentioned:OxF s05e24 - Oxide's $100M Series BOxF s05e04 - AI Disruption: DeepSeek and CerebrasIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Energy Fuels has successfully completed production of its first kilogram of dysprosium oxide at pilot scale at the Company's White Mesa Mill in Utah. White Gold has updated its mineral resource estimate. NexMetals and Dryden Gold have new assay results out. Marimaca to acquire a sulfuric acid plant in Chile. This episode of Mining Stock Daily is brought to you by... Revival Gold is one of the largest pure gold mine developer operating in the United States. The Company is advancing the Mercur Gold Project in Utah and mine permitting preparations and ongoing exploration at the Beartrack-Arnett Gold Project located in Idaho. Revival Gold is listed on the TSX Venture Exchange under the ticker symbol “RVG” and trades on the OTCQX Market under the ticker symbol “RVLGF”. Learn more about the company at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠revival-dash-gold.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Vizsla Silver is focused on becoming one of the world's largest single-asset silver producers through the exploration and development of the 100% owned Panuco-Copala silver-gold district in Sinaloa, Mexico. The company consolidated this historic district in 2019 and has now completed over 325,000 meters of drilling. The company has the world's largest, undeveloped high-grade silver resource. Learn more at⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠https://vizslasilvercorp.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Equinox has recently completed the business combination with Calibre Mining to create an Americas-focused diversified gold producer with a portfolio of mines in five countries, anchored by two high-profile, long-life Canadian gold mines, Greenstone and Valentine. Learn more about the business and its operations at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠equinoxgold.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Integra is a growing precious metals producer in the Great Basin of the Western United States. Integra is focused on demonstrating profitability and operational excellence at its principal operating asset, the Florida Canyon Mine, located in Nevada. In addition, Integra is committed to advancing its flagship development-stage heap leach projects: the past producing DeLamar Project located in southwestern Idaho, and the Nevada North Project located in western Nevada. Learn more about the business and their high industry standards over at integraresources.com

Listen now to 126 Future Now Show - Starfish Mystery We made it back home from Canada by the skin of our teeth, just ahead of the massive Air Canada Flight Attendant’s strike, as were on one of the last flights out of Quebec province! While in Canada we created some interviews for our show (see last two weeks shows), and now that we are back we’ll catch up on some significant Dr. Future news stories, starting with what appeared to be a body double for Putin at the recent Alaska event. Really? We look at the evidence..  Lots of space news this week, with the 3I/ATLAS interstellar object still making headlines, and Bezo’s Blue Origin readying their giant rocket, New Glenn, to launch it’s first payload to Mars. Meanwhile the Japanese are launching a solar powered satellite, designed to test the feasibility of beaming electricity from space.  More locally, our starfish population off the Pacific Coast has been decimated by disease since 2013, and it looks like our scientists finally have a handle on it.  Now how can we save these creatures from further suffering? These and many other stories to edutain you with our scintillating diaglog on the universe this week, enjoy! Getting a handle on their pandemic

Bryan Cantrill returns in the wake of Oxide Computer Company's $100M Series B. Bryan tells us how he's avoiding an appearance on Silicon Valley (ding), why their uniform compensation is working, where Oxide fits in the AI datacenter, what scaling to 50+ rack orders looks like, and more. (GitHub has no CEO and saving Intel)++

This week, we discuss GPT 5.0, the emerging AI ecosystem, and why TAM is basically a bedtime story for investors. Plus, Coté serves up a masterclass on kolaches. Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/nco_KB19FRc?si=H74g05kXMYyshCMT) 533 (https://www.youtube.com/live/nco_KB19FRc?si=H74g05kXMYyshCMT) Runner-up Titles Yeehaw Buns Bush Turkey Pigs in Blanket The Czech Stop "The Central Texas Kolache Corridor" “I'm over here in Gemini-land.” What if this is as good as it gets? How smart are humans? You're Tony Randall! Is this the dystopian future we signed up for? Extreme in Hungary (Tilberg, actually) I don't think there's a honey-badger outcome. All the porridge A bedtime story for investors Rundown OpenAI OpenAI Finally Launched GPT-5. Here's Everything You Need to Know (https://www.wired.com/story/openais-gpt-5-is-here/) OpenAI launches new GPT-5 model for all ChatGPT users (https://www.cnbc.com/2025/08/07/openai-launches-gpt-5-model-for-all-chatgpt-users.html) GPT-5 is alive (https://www.platformer.news/gpt-5-launch-release-reviews-impressions/) OpenAI is raising money at a $300 billion valuation (https://www.axios.com/newsletters/axios-pro-rata-e77a108b-d766-47b3-8052-9cf8a8b46021.html?chunk=1&utm_term=emshare#story1) Sam Altman says Gen Z are the ‘luckiest' kids in history thanks to AI, despite mounting job displacement dread (https://www.yahoo.com/news/articles/sam-altman-says-gen-z-143000256.html) Three big lessons from the GPT-5 backlash (https://www.platformer.news/gpt-5-backlash-openai-lessons/?ref=platformer-newsletter) Mr. Short-Term Memory (https://www.youtube.com/watch?v=C6ufImch00g) The AI Ecosystem Apps are growing Your AI workloads still need a service mesh (https://blog.howardjohn.info/posts/ai-mesh/) AI Security Company | Manage GenAI Risks & Secure LLM Apps (https://www.prompt.security/) Requesty - Unified LLM Platform (https://www.requesty.ai/) The latest AI news we announced in July (https://blog.google/technology/ai/google-ai-updates-july-2025/) Oxide and Friends | Oxide's $100M Series B (https://oxide-and-friends.transistor.fm/episodes/oxides-100m-series-b) Relevant to Your Interests Google Pixel 10 | Soon (https://youtu.be/ZR_6Z1IDD8s) The Man Who Beat IBM (https://every.to/feeds/b0e329f3048258e8eeb7/the-man-who-beat-ibm) Linus Torvalds Rejects RISC-V Changes For Linux 6.17: "Garbage" (https://www.phoronix.com/news/Linux-6.17-RISC-V-Rejected) Zuckerberg's Compound Had Something That Violated City Code: A Private School (https://www.nytimes.com/2025/08/10/us/zuckerberg-compound-palo-alto-school.html?smid=nytcore-ios-share&referringSource=articleShare) The 20-Year David Ellison Plan (https://www.hollywoodreporter.com/business/business-news/david-ellison-ai-questions-paramount-media-1236340756/?link_source=ta_thread_link&taid=68974982ac8daf00015b2343&utm_campaign=trueanthem&utm_medium=social&utm_source=threads.net) AOL Will End Its Dial-Up Internet Service (Yes, It's Still Operating) (https://www.nytimes.com/2025/08/11/business/aol-dial-up-internet.html) Ford's cheaper, simpler $30K electric vehicles are how 'we can make money on EVs,' CEO says (https://finance.yahoo.com/news/fords-cheaper-simpler-30k-electric-vehicles-are-how-we-can-make-money-on-evs-ceo-says-143040475.html) Goodbye API Keys: Gemini CLI GitHub Actions with Workload Identity Federation (https://medium.com/google-cloud/goodbye-api-keys-gemini-cli-github-actions-with-workload-identity-federation-6d4fae9e936b) I Tried Every Todo App and Ended Up With a .txt File (https://www.al3rez.com/todo-txt-journey) Intel shares drop after Trump calls for CEO to resign immediately (https://www.cnbc.com/2025/08/07/intel-ceo-trump-lip-bu-tan.html) Auf Wiedersehen, GitHub (https://github.blog/news-insights/company-news/goodbye-github/) GitHub will join Microsoft's CoreAI division with departure of CEO Thomas Dohmke (https://www.geekwire.com/2025/github-will-join-microsofts-coreai-group-with-departure-of-ceo-thomas-dohmke/) Nonsense The FDA Wants to Change the Definition of Orange Juice for the First Time in 60 Years (https://www.foodandwine.com/orange-juice-fda-standard-of-identity-11786737) Conferences SpringOne (https://www.vmware.com/explore/us/springone?utm_source=organic&utm_medium=social&utm_campaign=cote), Las Vegas, August 25th to 28th, 2025. See Coté's pitch (https://www.youtube.com/watch?v=f_xOudsmUmk). Explore 2025 US (https://www.vmware.com/explore/us?utm_source=organic&utm_medium=social&utm_campaign=cote), Las Vegas, August 25th to 28th, 2025. See Coté's pitch (https://www.youtube.com/shorts/-COoeIJcFN4). Wiz Capture the Flag (https://www.wiz.io/events/capture-the-flag-brisbane-august-2025), Brisbane, August 26. Matt will be there. SREDay London (https://sreday.com/2025-london-q3/), Coté speaking, September 18th and 19th. Civo Navigate London (https://www.civo.com/navigate/london/2025), Coté speaking, September 30th. Texas Linux Fest (https://2025.texaslinuxfest.org), Austin, October 3rd to 4th. CF Day EU (https://events.linuxfoundation.org/cloud-foundry-day-europe/), Frankfurt, October 7th, 2025. AI for the Rest of Us (https://aifortherestofus.live/london-2025), Coté speaking, October 15th to 16th, London. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: AirPods Max (https://www.apple.com/airpods-max/) Matt: Devolutionary Times (https://www.youtube.com/watch?v=aSzkOsADr74) Coté: “Connaissais de Face,” (https://www.youtube.com/watch?v=-1Aq10LTVsQ) “Evan Finds The Third Room.” (https://www.youtube.com/watch?v=QcD_YXCxxZM) L (https://www.youtube.com/watch?v=gxCJToKyc-0)ive performance of the song “People Everywhere” (https://www.youtube.com/watch?v=gxCJToKyc-0) Photo Credits Header (https://dynamic-media-cdn.tripadvisor.com/media/photo-o/0d/9a/77/60/so-many-kolaches-to-choose.jpg?w=900&h=500&s=1)

Bryan Cantrill returns in the wake of Oxide Computer Company's $100M Series B. Bryan tells us how he's avoiding an appearance on Silicon Valley (ding), why their uniform compensation is working, where Oxide fits in the AI datacenter, what scaling to 50+ rack orders looks like, and more. (GitHub has no CEO and saving Intel)++

In the second installment of our Emerging Contaminants series, we turn our attention to ethylene oxide, a chemical critical to the sterilization of medical and protective equipment yet increasingly scrutinized for its potential carcinogenic effects due to widespread use and long industrial history. In this episode, we're joined by Rebecca Pritchett (Maynard Nexsen), Heather Lynch (Integral Consulting), and David Fusco (K&L Gates) to examine the latest developments in ethylene oxide science, regulation, and litigation. Our guests discuss recent findings and interpretations suggesting that human health risks from ethylene oxide exposure may be lower than previously thought—a perspective that continues to generate scientific, legal, and policy debate.

Scott Hanselman gave a terrific talk about the promises of tech: connection, convenience and creativity. Did it deliver? Scott joins Bryan and Adam to discuss... and also wander around as one expects from an Oxide and Friends episode.In addition to Bryan Cantrill and Adam Leventhal, our special guest was Scott Hanselman.Past episodes mentioned:OxF s01e12 - A Brief History of Talking ComputersOxF s02e18 - Books in the Box ReduxOxF s05e10 - Lip‑Bu Tan's IntelSome of the topics we hit on, in the order that we hit them:Scott's talk: Tech Promised Everything. Did it deliver?If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Oxide raised its $100M Series B round of venture capital. Oxide's founders, Bryan and Steve, answer questions selected by Adam from social media about the round, the company, and the future.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide CEO, the man, the myth, the legend, Steve Tuck.Previous episodes mentioned:OxF s05e10 - Lip‑Bu Tan's IntelOxF s03e04 - Oxide and the Chamber of MysteriesOxF s04e27 - Unshrouding Turin (or Benvenuto a Torino)OxF s05e14 - Bringing up CosmoSome of the topics we hit on, in the order that we hit them:blog: Oxide's $100M Series BHacker News threadPRs needed!If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Two years ago, the Oxide team encountered data corruption during a fairly simple network data transfer. The ensuing debugging sessions uncovered a truly bizarre bug involving CPU speculation! Bryan and Adam were joined by colleagues John and Rain to discuss the discovery and circuitous hunt to track down the bug.In addition to Bryan Cantrill and Adam Leventhal, speakers included John Gallagher, and Rain Paharia.Previous episodes mentioned:OxF s03e09 - Get You a State Machine for Great GoodOxF s03e20 - Shipping the first Oxide rack: Tales from ManufacturingOxF s04e25 - RTO or GTFOOxF s02e38 - A Debugging OdysseySome of the topics we hit on, in the order that we hit them:The Update FrameworkOmicron Issue #3441 (Oxide Computer GitHub)Omicron Pull Request #3455 (Oxide Computer GitHub)stlouis Issue #454 (Oxide Computer GitHub)Changing psrset.out.txt (Oxide Computer)Commit 5ec2885322423c0cca0d006611b5c9ac94b0f588 (Oxide Computer)Omicron Pull Request #3560 (Oxide Computer GitHub)If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

On this episode of Vitality Radio, Jared shares three powerhouse supplements that may not be “new,” but are being used in some of the most impactful ways yet. First up is a clinically studied lutein and zeaxanthin complex that supports eye health, blue light protection, and even cognitive performance—delivered in a delicious gummy called Screen Eyes. Next, Jared breaks down monolaurin, a coconut-derived compound that supports immune resilience by targeting lipid-coated viruses like herpes, Epstein-Barr, and influenza—especially when paired with L-lysine and vitamin C. And finally, he explores two innovative magnesium-based powders from Kal - Clean Out Magnesium and Gut Magnesium, each designed to promote healthy regularity and support cleansing protocols. If you've struggled with constipation or want to fine-tune your immune and visual wellness, this is an episode you don't want to miss.Products:Zhou Screen Eyes Blue Light FormulaMonolaurin & LysineVital-C ImmunityNano-SilverKAL Clean Out Magnesium PowderKAL Gut Magnesium PowderVital 5 Magnesium BisglycinateAdditional Information:#209 VR Short: Centrum SucksVisit the podcast website here: VitalityRadio.comYou can follow @vitalitynutritionbountiful and @vitalityradio on Instagram, or Vitality Radio and Vitality Nutrition on Facebook. Join us also in the Vitality Radio Podcast Listener Community on Facebook. Shop the products that Jared mentions at vitalitynutrition.com. Let us know your thoughts about this episode using the hashtag #vitalityradio and please rate and review us on Apple Podcasts. Thank you!Just a reminder that this podcast is for educational purposes only. The FDA has not evaluated the podcast. The information is not intended to diagnose, treat, cure, or prevent any disease. The advice given is not intended to replace the advice of your medical professional.

What happens when the Oxide API is slow? A podcast episode! More specifically, one about how the team employed all manner of debugging techniques to track it down to one obscure and configurable async runtime feature! Bryan and Adam were joined by members of the team to talk about that journey and the tools we used (and made!) along the way.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues, Dave Pacheco, Eliza Weisman, and Augustus Mayo.Previous episodes mentioned:Oxide and the Chamber of MysteriesThe Saga of SagasDTrace at 20Cultural IdiosyncrasiesMr. Nagle's Wild RideA Debugging OdysseyRTO or GTFOSome of the topics we hit on, in the order that we hit them:Falling in Love with RustTokio Runtime Builder – disable_lifo_slotmagic‑trace (GitHub)Magic Trace podcast episode from Jane Streetdiesel‑dtrace (GitHub)omicron issue commentqorbstatemaptokio‑dtracetokio issue #7411Visualizing Systems with StatemapsPostgreSQL WAL INIT ZEROStatemaps: Visualizing System Behavior (YouTube)If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Nicki Killeen, HSE Emerging Drug Trends Project Manager and Mark Ward, Sinn Féin TD Dublin Mid-West

Building systems software can be quite opaque, leading to the need for great debugging tools. At Oxide, we've found that debuggers can be even more valuable leading rather than following system development. Bryan and Adam talk with Oxide colleagues about how domain specific debugging tools help us build systems not only more robustly, but faster as well.In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues, Dave Pacheco. John Gallagher, Alan Hanson, and Eliza Weisman.Previous episodes mentioned:OxF: AI Discourse with Steve KlabnikOxF: The Saga of SagasOxF: A Crate is BornOxF: The Network Behind the NetworkOxF: Bringing up CosmoOxF: RIP USENIX ATCOxF: Dijkstra's TweetstormSome of the topics we hit on, in the order that we hit them:omdb ground rulesIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

Last week, our colleague (and frequent Oxide and Friends guest) Steve Klabnik made some new friends on the Internet with a blog entry on AI discourse. Bryan and Adam were joined by Steve to try to de-polarize the discussion a little.In addition to Bryan Cantrill and Adam Leventhal, we were joined by special guest, Steve Klabnik, and valued listener, Julian Giamblanco (aka "Oatmealdealer").Some of the topics we hit on, in the order that we hit them:Steve's blog post: I am disappointed in the AI discourseOxF: A Baseball Startup with Paul Freedman and Bryan Carmel (The Ballers)OxF: Adversarial Machine Learning with Nicholas CarliniOxF: Hiring Processes with Gergely Orosz ("the RFD 3 podcast episode")OxF: AI Disruption: DeepSeek and CerebrasOxF: Reflecting on Founder Mode ("ego con")If we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

This week, we unpack what Uber's CEO said, why the CNCF exists, and how companies chase the money. Plus, Coté stands alone in his love for rice cakes. Watch the YouTube Live Recording of Episode 518 (https://www.youtube.com/live/h0RVI_IOZvo?si=tbRl4R8iwhDsLzu7) Runner-up Titles Go feral You've ruined eating for me Cultural tombstone The next step is “I told you so” Culture is what happens when you're not talking about culture. You know, it's terrible to run over someone The robots are just fine Center of Attention Rundown Uber CEO says changing employee benefits 'is a risk we decided to take' (https://www.cnbc.com/2025/05/06/uber-ceo-says-changing-employee-benefits-is-a-risk-we-decided-to-take.html) Waymo is reducing serious crashes and making streets safer for those most at risk (https://waymo.com/blog/2025/05/waymo-making-streets-safer-for-vru) CNCF and Synadia Align on Securing the Future of the NATS.io Project (https://www.cncf.io/announcements/2025/05/01/cncf-and-synadia-align-on-securing-the-future-of-the-nats-io-project/) Oxide and Friends | Shootout at the CNCF Corral (https://oxide-and-friends.transistor.fm/episodes/shootout-at-the-cncf-corral) New D&D core rules are now CC-BY (https://www.dndbeyond.com/srd?srsltid=AfmBOorzpL2Y57RWJ966OdFDTICTiWTAAQL6Dn8FFvcB09HJClZkbWli). ‘Cook chose poorly': how Apple blew up its control over the App Store (https://www.theverge.com/apple/659296/apple-failed-compliance-court-ruling-breakdown) Relevant to your Interests I use Zip Bombs to Protect my Server (https://idiallo.com/blog/zipbomb-protection) "AI-first" is the new Return To Office - Anil Dash (https://www.anildash.com/2025/04/19/ai-first-is-the-new-return-to-office/) Find and Buy with AI: Visa Unveils New Era of Commerce (https://www.businesswire.com/news/home/20250430580204/en/Find-and-Buy-with-AI-Visa-Unveils-New-Era-of-Commerce?utm_source=www.therundown.ai&utm_medium=newsletter&utm_campaign=visa-mastercard-give-ai-credit-cards&_bhlid=3ec615c11c0429835c326dbeaabe5bca0dddaf66) Google dusts off Google Voice and adds three-way calling (https://www.theverge.com/news/659719/google-voice-app-update-call-ui-merge-three-way) Anthropic to Buy Back Employee Shares at $61.5 Billion Valuation (https://www.theinformation.com/articles/anthropic-buy-back-employee-shares-61-5-billion-valuation) IBM unveils capabilities meant to accelerate AI agent adoption (https://siliconangle.com/2025/05/06/ibm-unveils-capabilities-meant-accelerate-ai-agent-adoption/) Getting things "done" in large tech companies (https://www.seangoedecke.com/getting-things-done/) A.I. Is Getting More Powerful, but Its Hallucinations Are Getting Worse (https://www.nytimes.com/2025/05/05/technology/ai-hallucinations-chatgpt-google.html?campaign_id=9&emc=edit_nn_20250505&instance_id=153899&nl=the-morning®i_id=55370892&segment_id=197320&user_id=861fd8fcc0091c6690e3b338636d5995) This NAS brand just called out the competition and says you should own your hardware (https://www.techradar.com/pro/asustor-makes-veiled-dig-at-synologys-proprietary-hard-drive-philosophy-with-open-and-unlocked-stance) Microsoft Earnings, Microsoft's Core Capability, Amazon Earnings (https://stratechery.com/2025/microsoft-earnings-microsofts-core-capability-amazon-earnings/) Amazon beats on top and bottom line but issues light second quarter guidance (https://www.cnbc.com/2025/05/01/amazon-amzn-q1-earnings-report-2025.html) Amazon Takes Aim at Cursor With New AI Coding Service (https://www.theinformation.com/articles/amazon-takes-aim-cursor-new-ai-coding-service) OpenAI caves to pressure, keeps nonprofit in charge (https://www.theregister.com/2025/05/05/openai_keep_nonprofit_in_charge/) OpenAI Reaches Agreement to Buy Startup Windsurf for $3 Billion (https://www.bloomberg.com/news/articles/2025-05-06/openai-reaches-agreement-to-buy-startup-windsurf-for-3-billion) Anysphere, which makes Cursor, has reportedly raised $900M at $9B valuation (https://techcrunch.com/2025/05/04/cursor-is-reportedly-raising-funds-at-9-billion-valuation-from-thrive-a16z-and-accel/) Clouded Judgement 5.2.25 - Cloud Giants Report Q1 '25 (https://open.substack.com/pub/cloudedjudgement/p/clouded-judgement-5225-cloud-giants?r=2l9&utm_medium=ios) Nine Emerging Developer Patterns for the AI Era | Andreessen Horowitz (https://a16z.com/nine-emerging-developer-patterns-for-the-ai-era/?trk=feed_main-feed-card_feed-article-content) Nonsense AI Brings Play-by-Play Commentary To Pong (https://hackaday.com/2025/05/06/ai-brings-play-by-play-commentary-to-pong/) Conferences Fr (https://vmwarereg.fig-street.com/051325-tanzu-workshop/)ee AI workshop (https://vmwarereg.fig-street.com/051325-tanzu-workshop/), May 13th. day before C (https://events.linuxfoundation.org/cloud-foundry-day-north-america/)loud (https://events.linuxfoundation.org/cloud-foundry-day-north-america/) (https://events.linuxfoundation.org/cloud-foundry-day-north-america/)Foundry (https://events.linuxfoundation.org/cloud-foundry-day-north-america/) Day (https://events.linuxfoundation.org/cloud-foundry-day-north-america/). Melbourne Wiz Meet-Up (https://www.wiz.io/events/melbourne-wizdom-meet-up-may-2025), May 13. Matt will be there. Cloud Foundry Day US (https://events.linuxfoundation.org/cloud-foundry-day-north-america/), May 14th, Palo Alto, CA, Coté speaking. KCD Texas Austin 2025 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-austin-2025/), May 15th, Whitney Lee speaking NDC Oslo (https://ndcoslo.com/), May 21st-23th, Coté speaking. POST/CON 25 (https://fnf.dev/43irTu1), June 3-4, Los Angeles, CA, Brandon representing SDT. Use Code: BRANDON, first 20 people get a free pass SREDay Cologne, June 12th, 2025 (https://sreday.com/2025-cologne-q2/#tickets) - Coté speaking, discount: CLG10, 10% off. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: UniFi Express (https://store.ui.com/us/en/products/ux) , FlexHD (https://store.ui.com/us/en/products/uap-flexhd), U6+ (https://store.ui.com/us/en/products/u6-plus) and US 8 60W (https://store.ui.com/us/en/products/us-8-60w) Matt: Andor (https://www.google.com/aclk?sa=L&ai=DChcSEwi_k_SJq5KNAxVtbn8AHTM9LiAYABAAGgJvYQ&co=1&gclid=CjwKCAjwiezABhBZEiwAEbTPGJm543I3_qXVgfjHny9-ZLEw01E6SYCKzXEqXnLCpru-2Wjkg92ybRoCF8EQAvD_BwE&cce=1&sig=AOD64_1ZVJAYtB5pJD_f0aUN-mZqKPFYXQ&q&adurl&ved=2ahUKEwigq--Jq5KNAxV248kDHbzcLIoQ0Qx6BAgHEAQ) Season 2 (https://www.google.com/aclk?sa=L&ai=DChcSEwi_k_SJq5KNAxVtbn8AHTM9LiAYABAAGgJvYQ&co=1&gclid=CjwKCAjwiezABhBZEiwAEbTPGJm543I3_qXVgfjHny9-ZLEw01E6SYCKzXEqXnLCpru-2Wjkg92ybRoCF8EQAvD_BwE&cce=1&sig=AOD64_1ZVJAYtB5pJD_f0aUN-mZqKPFYXQ&q&adurl&ved=2ahUKEwigq--Jq5KNAxV248kDHbzcLIoQ0Qx6BAgHEAQ) Coté: Batman (https://www.rottentomatoes.com/m/1001781-batman) and Batman Returns (https://www.imdb.com/title/tt0103776/). Photo Credits Header (https://unsplash.com/photos/text-QUQwhUa_B7E)

Matthew Sanabria joins Bryan and Adam to talk about his role at Oxide--Solutions Software Engineer--and how it fits in with engineering, sales, support and marketing. It takes everyone in Busytown! Sound good? Apply!In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleague, Matthew Sanabria.Some of the topics we hit on, in the order that we hit them:Solutiuons Software Engineer applicationOxF: the "squeezefish" episodeThe Fallthrough podcastBusytownIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

The Daily Quiz - Science and Nature Today's Questions: Question 1: What is deuterium oxide commonly known as? Question 2: What is cereology the study of? Question 3: What is Histology the study of? Question 4: What is the medical name for the collarbone? Question 5: What is the term for the cleaning process that birds engage in? Question 6: What Did Alfred Nobel Invent Before Initiating His Nobel Peace Prize Award Scheme? Question 7: What is a baby weasel known as? Question 8: What is the word for a group of swans? Question 9: What is the word for a group of boars? This podcast is produced by Klassic Studios Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, we sit down with Filip Smeets, Chief Commercial Officer at Ceres Power, to explore the company's solid oxide technology and its role in the green H2 revolution. Filip shares his journey from NEL Hydrogen and Hydrogenics to Ceres, diving into the dual capability of their solid oxide platform for both electrolysis and fuel cells. He highlights how this flexibility, combined with high efficiency and modular scalability, positions Ceres to transform hard-to-abate industries such as steel, ammonia and data centers. We discuss strategic partnerships with Shell and Denso, the importance of leveraging industrial waste heat, and how licensing accelerates global deployment. Filip also addresses the critical role policymakers play in driving infrastructure change and enabling clean energy adoption.

Oxide is bringing up its next generation server. To discuss the (amazingly smooth) bringup process, Bryan and Adam were joined by members of the oxide team. Tales of adversity, re-work, un-re-work, and triumph!In addition to Bryan Cantrill and Adam Leventhal, we were joined by Oxide colleagues Nathanael Huffman, Ian Sobering, Matt Keeter, and Aaron Hartwig.We mentioned quite a few terms! Here's a helpful guide:Cosmo - Oxide's next-generation sled (currently in development) with an AMD Turin CPUGimlet - Oxide's current-generation sled with an AMD Milan CPUTurin - AMD Epyc 9005 SeriesMilan - AMD Epyc 7003 SeriesGenoa - AMD Epyc 9004 Series (Oxide chose to skip this generation)Sequencing - the precise control of when power rails are energized throughout a PCBSled - One of the (max 32) computers in an Oxide rack; a custom form-factor optimized for power and cooling efficiencyIBC - Intermediate Bus Converter (Our 54VDC -> 12VDC converter)RoT - Root of TrustSP - Service Processor, the small computer (running Hubris) that allows for low-level controlIgnition - An even lower-level control network for power management (including power of the SP)Ruby - The AMD reference platform (Oxide has used this to prepare Cosmo software in advance of bringup)DC-SCM - https://www.opencompute.org/documents/ocp-dc-scm-spec-rev-1-0-pdf and OpenCompute standard form factor.Grapefruit - OCP DC-SCM form-factor board with our SP, RoT, and FPGA on it, used to replace the OCP DC-SCM baseboard management controller in the Ruby platform.Cadence - Software Oxide previously used for PCB designAltium - Software Oxide now uses for PCB designHubris - Oxide's embedded operating system, run on the SP and RoTHumility - The Hubris debuggerPLM - Product Lifecycle Management – a class of software used for managing hardware BOMsBOM - Bill of Materials – the components required to build a hardware productRFK - Our colleague, Robert Keith (to distinguish him from our other colleague, Robert, and our former colleague, Keith)FPGA - Field Programmable Gate Array – Also referred to as “soft logic” – effectively programmable hardwareILA - Integrated Logic AnalyzerJTAG - A debugging interface for various processorsUART - A serial port or connectionFor previous tales from the bringup lab:Tales from the bringup labMore tales from the bringup labBringup Lab Chronicles: A Measurement Two Years in the MakingRaiding the MinibarIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

The Astronomy, Space and Science News PodcastEarth's Climate Shaped by Orion, New Insights into Mars' Red Color, and NASA's Europa Clipper Mission UpdateIn this episode of SpaceTime, we explore a groundbreaking study suggesting that Earth's climate may have undergone significant changes around 14 million years ago due to our solar system's journey through the Orion star-forming region. Researchers propose that this passage may have compressed the heliosphere, increasing interstellar dust influx and potentially impacting Earth's climate and geological records.Revisiting Mars' Iconic HueWe also discuss new findings that challenge previous assumptions about why Mars is red. Recent research indicates that the planet's rusted appearance may be linked to a wetter history, with liquid water playing a crucial role in the formation of iron oxides. This revelation reshapes our understanding of Mars' habitability and environmental conditions in its ancient past.NASA's Europa Clipper MissionAdditionally, we provide an exciting update on NASA's Europa Clipper mission, which has successfully completed a close gravity assist flyby of Mars. This maneuver not only altered the spacecraft's trajectory towards Jupiter but also allowed mission managers to test its radar instrument and thermal imager, setting the stage for its upcoming encounters with the icy moon Europa.00:00 Space Time Series 28 Episode 28 for broadcast on 5 March 202500:49 Impact of the solar system's journey through Orion on Earth's climate06:30 Details on the Radcliffe Wave and its significance12:15 New insights into Mars' red color and history of water18:00 Analysis of iron oxides and implications for Martian habitability22:45 Overview of NASA's Europa Clipper mission and its flyby of Mars27:00 The importance of gravity assists in space missions30:15 Health implications of screen time on children's visionwww.spacetimewithstuartgary.comwww.bitesz.com

Chad Peters, CEO of Ridgeline Minerals, discusses the company's recent acquisition of the Atlas Gold Project in Nevada, highlighting its potential as a high-grade oxide gold exploration prospect. He elaborates on the historical context of the project, the exploration strategy, and how it complements their ongoing work at the Big Blue project. Peters shares insights into the upcoming drill programs and the excitement surrounding both projects, emphasizing the promising geological features and the company's strategic approach to exploration.

A round-up of the main headlines in Sweden on December 3rd 2024. You can hear more reports on our homepage www.radiosweden.se, or in the app Sveriges Radio Play. Presenter: Babak ParhamProducer: Michael Walsh

Send us a textIn this episode of Tatter-a-Fact, I tackle one of the most heated debates in the PMU industry: carbon black vs. iron oxide pigments. Drawing from over 24 years of experience, I break down the differences between these two pigment types, the misconceptions surrounding them, and how to strategically choose which one to use based on your client's skin type. I also dive into the importance of considering factors like saturation levels, needle choices, and skin variables. Whether you're a seasoned artist or new to the industry, this episode will help you make informed decisions when it comes to pigments.  

Alan Carter, CEO of Cabral Gold, provides an update on the Cuiú Cuiú Gold Project in Brazil. He discusses the project's historical context, geological significance, and the recent pre-feasibility study results of the gold-in-oxide starter pit. Alan highlights the challenges of funding exploration and development while emphasizing the potential for significant gold resources. The conversation also covers the processing techniques being employed and the strategic shift towards generating cash flow through an oxide starter operation. Alan concludes with insights on the future of the project and investment considerations.