Podcasts about Supermicro

Why are investors turning away from gold? And why weren't Micron Technology's blowout earnings good enough? Plus, why is Super Micro's co-founder in hot water with U.S. prosecutors? Host Hannah Erin Lang discusses the biggest stock moves of the week and the news that drove them. Sign up for the WSJ's free Markets A.M. newsletter Learn more about your ad choices. Visit megaphone.fm/adchoices

Why are investors turning away from gold? And why weren't Micron Technology's blowout earnings good enough? Plus, why is Super Micro's co-founder in hot water with U.S. prosecutors? Host Hannah Erin Lang discusses the biggest stock moves of the week and the news that drove them.Sign up for the WSJ's free Markets A.M. newsletter. Learn more about your ad choices. Visit megaphone.fm/adchoices

Market update for Friday March 20, 2026Check out the Public app for incredible investing tools and to support the show (LINK)Follow us on Instagram (@TheRundownDaily) for bonus content and instant reactions.In today's episode:FedEx earnings signal economy still holding upAmazon working on AI-powered smartphone comebackSuper Micro stock plunges after smuggling chargesFirefly Aerospace surges on strong growthTesla Semi wins over truckers

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

Why are Gartner investors so spooked by AI? And how is the AI infrastructure buildout supercharging Super Micro shares? Plus, what's behind the selloff of Coinbase shares? Host Jack Pitcher discusses the biggest stock moves of the week and the news that drove them. Sign up for the WSJ's free Markets A.M. newsletter. Learn more about your ad choices. Visit megaphone.fm/adchoices

Why are Gartner investors so spooked by AI? And how is the AI infrastructure buildout supercharging Super Micro shares? Plus, what's behind the selloff of Coinbase shares? Host Jack Pitcher discusses the biggest stock moves of the week and the news that drove them. Sign up for the WSJ's free Markets A.M. newsletter. Learn more about your ad choices. Visit megaphone.fm/adchoices

Supermicro's (SMCI) self-described "near-term margin pressure" didn't stop investors from buying shares of the company. Marley Kayden turns to the earnings drawing Wall Street back to the beaten-down tech stock. However, as Marley explains, analysts remain mixed on Supermicro's outlook. Prosper Trading Academy's Scott Bauer offers an example options trade for the stock. ======== Schwab Network ========Empowering every investor and trader, every market day.Options involve risks and are not suitable for all investors. Before trading, read the Options Disclosure Document. http://bit.ly/2v9tH6DSubscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribeDownload the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watchWatch on Vizio - https://www.vizio.com/en/watchfreeplus-exploreWatch on DistroTV - https://www.distro.tv/live/schwab-network/Follow us on X – https://twitter.com/schwabnetworkFollow us on Facebook – https://www.facebook.com/schwabnetworkFollow us on LinkedIn - https://www.linkedin.com/company/schwab-network/About Schwab Network - https://schwabnetwork.com/about

4/2 Ws futures misti. Prosegue la rotazione fuori dal Tech a favore di ciclici, value vince su growth. Debacle del settore software (Etf -5%) su timori disruption AI. La scintilla: il nuovo plugin di Anthropic cowork agent per diversi settori: legal, finance, marketing etc. London Stock Exchange –13%, Reuters –15%, Gartner –21%, S&P Global 11% Moody's 9% Factset 11%. Walmart entra nel club da 1000 mld di capitalizzazione, è la dodicesima società al mondo dopo Berkshire. Oro recupera 5.000$ sale anche l'argento. AMD scivola sui conti, guidance debole. SuperMicro +7% in pre-market. Nvidia pronta a investire 20mld dollari in OpenAI. Huang: nessun dramma con Altman. Stasera Alphabet. Petrolio risale su tensioni Iran. Gli Usa abbattono drone iraniano. Witkoff vede Nethanyau, colloqui possibili in Oman e non Turchia. La Russia intercetta le comunicazioni chiave di almeno una dozzina di satelliti europei. Asia Mista, Kospi record. Nikkei in rosso, yen in calo. Nintendo -10% su timori memory chip. Europa, Milano riparte dai massimi dal 2000. Domani Bce, oggi inflazione preliminare gennaio. Assemblea straordinaria di MPS, Lovaglio accelera sul Piano. Bff verso delisting? Ubs batte le attese: 1,2 mld euro profitti nel 4Q, buyback da 3mld euro.  Learn more about your ad choices. Visit megaphone.fm/adchoices

Markets digest a flood of major earnings while tech volatility takes center stage. Jim Cramer interviewed NVIDIA CEO Jensen Huang and talks the AI trade scrutiny. Huang weighs in on OpenAI's massive fundraising round. Ke reports from AMD, Amgen, Chipotle, Mondelez and Super Micro. Christopher Rolland, Senior Analyst at Susquehanna, analyzes what the AMD results mean for the broader semiconductor trade.Jackson Ader, Senior Research Analyst at KeyBanc, joins to discuss the ongoing software selloff, while Venu Krishna, Head of U.S. Equity Strategy at Barclays, offers insight on market positioning and earnings momentum. A look ahead to Alphabet's earnings with Gil Luria, Managing Director and Senior Software Analyst at D.A. Davidson. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

European bourses opened stronger, but sentiment has dipped off best levels; US equity futures are modestly firmer, with mild outperformance is seen in the NQ.DXY is flat, Antipodeans benefit from a rebound in metals prices with outperformance in the Aussie after the RBA hiked rates by 25bps (as expected), whilst the SoMP noted that underlying inflation is higher than expected.Fixed income on the backfoot with supply in focus in a shutdown-thinned US docket.Crude prices initially lower but now flat; India to stop importing Russian oil as part of the trade deal with the US. Metals rebound with spot gold returning above USD 4900/oz.Looking ahead, highlights include US RCM/TIPP (Feb), New Zealand Unemployment (Q4), Australian S&P PMIs Final (Jan), Speakers including Fed's Bowman, Barkin & ECB's Lagarde.December JOLTS has been postponed, on account of the US government shutdown. Earnings from AMD, Supermicro, Amgen, Amcor, PayPal, PepsiCo, Pfizer, Merck.Read the full report covering Equities, Forex, Fixed Income, Commodites and more on Newsquawk

APAC stocks were mostly higher with several bourses firmly recovering from the prior day's sell-off, as the region took impetus from the positive handover from Wall Street.US President Trump announced that India will stop buying Russian oil, while the US will be lowering tariffs on India to 18% from 25%.RBA hiked the Cash Rate by 25bps as expected in a unanimous decision, marking the first hike in over two years; RBA's SoMP noted that underlying inflation is higher than expected and GDP growth has continued to pick up.US BLS will not release the January jobs report on Friday due to the partial US Government shutdown, while December JOLTS (due 3rd Feb) has also been postponed.European equity futures indicate a positive cash market open with Euro Stoxx 50 futures up 0.4% after the cash market closed with gains of 1.0% on Monday.Looking ahead, highlights include Turkish Inflation (Jan), French Prelim. CPI (Jan), RCM/TIPP (Feb), New Zealand Unemployment (Q4), Australian S&P PMIs Final (Jan), Speakers including Fed's Bowman, Barkin & ECB's Lagarde, Supply from UK & Germany, Earnings from AMD, Supermicro, Amgen, Amcor, PayPal, PepsiCo, Pfizer, Merck & Publicis.Read the full report covering Equities, Forex, Fixed Income, Commodites and more on Newsquawk

Singapore shares rose today as Asian markets rebounded from the previous day’s losses. The Straits Times Index was up 1.04% at 4,943.04 points at 2.30pm Singapore time, with a value turnover of S$1.06B seen in the broader market. In terms of counters to watch, we have the Singapore Exchange given how the bourse operator and the Monetary Authority of Singapore (MAS) are working on paving the way for forward-looking disclosures by listed companies. Elsewhere, from how Australia’s central bank raised its benchmark policy rate for the first time in two years today, to how US President Donald Trump said tariffs on Indian goods would be cut from 50% to 18% in return for New Delhi halting Russian oil purchases and lowering trade barriers, more international headlines remained in focus. On Market View, Money Matters’ finance presenter Chua Tian Tian unpacked the developments with Kelvin Wong, Senior Analyst, OANDA.See omnystudio.com/listener for privacy information.

Zahlen in dieser Woche: Palantier, Supermicro, PayPal, Uber, Alphabet, Amazon ARM und Qualcomm

In der heutigen Folge sprechen die Finanzjournalisten Anja Ettel und Holger Zschäpitz über Fantasie bei Ölservicefirmen, neue Lebenszeichen beim Bitcoin und die Vermögenspräferenzen der Deutschen. Außerdem geht es um AST Space Mobile, Robinhood, Archer Aviation, Riot Platforms, Coinbase, Jaguar Land Rover, Siemens, Palantir, CoreWeave, Supermicro, Magna, Nebius, Microsoft, Schlumberger, Halliburton, Chevron, Exxon, Conocophilips, Valero und Phillips66, DWS Invest Latin American Equities (WKN: DWS0VM), Nordea Latin American Equity Fund (WKN: A1T8Q4), Amundi Funds Latin America (WKN: A0DNS3), JPMorgan Funds - Latin America (WKN: 972079), Amundi MSCI EM Latin America ETF (WKN: A2H58P). Wir freuen uns an Feedback über aaa@welt.de. Noch mehr "Alles auf Aktien" findet Ihr bei WELTplus und Apple Podcasts – inklusive aller Artikel der Hosts und AAA-Newsletter. Hier bei WELT: https://www.welt.de/podcasts/alles-auf-aktien/plus247399208/Boersen-Podcast-AAA-Bonus-Folgen-Jede-Woche-noch-mehr-Antworten-auf-Eure-Boersen-Fragen.html. Der Börsen-Podcast Disclaimer: Die im Podcast besprochenen Aktien und Fonds stellen keine spezifischen Kauf- oder Anlage-Empfehlungen dar. Die Moderatoren und der Verlag haften nicht für etwaige Verluste, die aufgrund der Umsetzung der Gedanken oder Ideen entstehen. Hörtipps: Für alle, die noch mehr wissen wollen: Holger Zschäpitz können Sie jede Woche im Finanz- und Wirtschaftspodcast "Deffner&Zschäpitz" hören. +++ Werbung +++ Du möchtest mehr über unsere Werbepartner erfahren? Hier findest du alle Infos & Rabatte! https://linktr.ee/alles_auf_aktien Impressum: https://www.welt.de/services/article7893735/Impressum.html Datenschutz: https://www.welt.de/services/article157550705/Datenschutzerklaerung-WELT-DIGITAL.html

We look back to look forward and predict whether three of 2025's biggest disappointments can turn it around in 2026. Can Super Micro Computer (NASDAQ: SMCI), Lululemon (NASDAQ: LULU), and Nike (NYSE: NKE) get back to beating the market? Tom King, Travis Hoium, and Tim Beyers discuss: - How losing faith with auditors cost Supermicro. - Whether fashion trends favor Lululemon. - The 2026 challenges facing Nike CEO Elliott Hill. Companies discussed: SMCI, LULU, NKE Host: Tim Beyers Guests: Tom King, Travis Hoium Producer: Anand Chokkavelu Engineer: Dan Boyd Disclosure: Advertisements are sponsored content and provided for informational purposes only. The Motley Fool and its affiliates (collectively, “TMF”) do not endorse, recommend, or verify the accuracy or completeness of the statements made within advertisements. TMF is not involved in the offer, sale, or solicitation of any securities advertised herein and makes no representations regarding the suitability, or risks associated with any investment opportunity presented. Investors should conduct their own due diligence and consult with legal, tax, and financial advisors before making any investment decisions. TMF assumes no responsibility for any losses or damages arising from this advertisement. We're committed to transparency: All personal opinions in advertisements from Fools are their own. The product advertised in this episode was loaned to TMF and was returned after a test period or the product advertised in this episode was purchased by TMF. Advertiser has paid for the sponsorship of this episode. Learn more about your ad choices. Visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠megaphone.fm/adchoices Learn more about your ad choices. Visit megaphone.fm/adchoices

This week on Market Mondays we're getting tactical and long-term: your futures trading tip of the week, the biggest mistakes younger investors make chasing fast wins, and the most important investing lessons this year reinforced. We also get personal about the mindset shifts that matter—what we used to disagree with early on, then changed our mind about later, and the questions people should be asking if they actually want to build wealth over decades (not just catch a lucky trade).Then we dive into what's moving markets right now: Oracle as a business and investment, whether the AI narrative tied to SoftBank/OpenAI has pushed expectations too far, and what really caused Friday's sell-off—plus whether it quietly changed market structure more than most people realize. We break down the Coinbase vs. MicroStrategy vs. IBIT debate, talk about whether we're headed toward a real correction or just another emotional shakeout, and if the market is broadening beyond tech or setting up a head fake before leadership narrows again.We also hit the high-volatility conversations: Super Micro's relevance in AI infrastructure, how elite traders handle ES and NQ moving in sync, and whether leveraged ETFs like NVDL/AMDL are advanced tools—or long-term portfolio destroyers in disguise. Plus: quantum computing (obvious leaders vs. sleeper names), and a real discussion on how to balance fitness, family, investing, travel, and content creation without burning out. And we're joined by Derrick Hayes to talk about his business journey and what it really takes to scale.#MarketMondays #Investing #Stocks #FuturesTrading #DayTrading #LongTermInvesting #FinancialLiteracy #WealthBuilding #AI #Oracle #Crypto #Bitcoin #Coinbase #MicroStrategy #IBIT #ETFs #LeveragedETFs #NVDL #AMDL #TechStocks #MarketNews #TradingPsychology #RiskManagement #QuantumComputing #Entrepreneurship #DerrickHayes #EarnYourLeisureSupport this podcast at — https://redcircle.com/marketmondays/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

I ugens episode af Aktieuniverset får vi besøg af Jens Schjerning til en snak om den økonomiske situation generelt, renterne og forventningerne dertil for næste år - og selvfølgelig aktier. Vi kommer også forbi diverse markedsnyheder for ugen. Et lytterspørgsmål om Super Micro Computer kommer vi igennem, samt en kig på nogle nye aktier på sigtekornet. Der er også regnskaber fra ugens løb, vi kommer igennem. Alt dette og meget mere! Denne episode er sponsoreret af Vippresidences.com. Bliv medejer af unikke boliger rundt omkring i verdenen. Læs mere på Vippresidences.com. Denne episode er sponsoreret af rådgiver Hans Henrik fra Pensionsplanlægning. Få rådgivning og optimering på din pensionsopsparing. Se mere på Pensionsplanlægning.dk.Sig du kommer fra Aktieuniverset - så får man ekstra god behandling. Denne episode er sponsoreret af investeringsfonden NewDeal Invest. Porteføljen NDI-FutureTech på eToro har fødselsdag og fylder 2 år. På de 2 år har portoføljen lavet et afkast på 117%.Læs mere på newdealinvest.dk. Denne episode er sponsoreret af Finobo. Få et gratis økonomitjek hos specialisterne i låneoptimering ved at bruge linket:finobo.dk/gratis-oekonomitjek-aktieuniverset/Prøv den nye omlægningsberegner på Finobo.dk/beregner-omlaegningsberegner/?utm_source=aktieuniverset  Tjek os ud på:FB gruppe: ⁠facebook.com/groups/1023197861808843⁠X: ⁠x.com/aktieuniverset⁠IG: ⁠instagram.com/aktieuniversetpodcast⁠  DISCLAIMER:Aktieuniverset indeholder markedsføring af investeringsforeningen Portfoliomanager NewDeal Invest, kl n (PMINDI), som Mads Christiansen er investeringsrådgiver for. Podcasten kan ligeledes referere til andre fonde.Indholdet i podcasten udtrykker alene værternes og gæsters egne holdninger, refleksioner og analyser, og skal ikke opfattes som en personlig anbefaling af bestemte værdipapirer eller strategier. Podcasten skal ikke anses som investeringsrådgivning, da den enkelte lytters finansielle situation, nuværende aktiver eller passiver, investeringskendskab og -erfaring, investeringsformål, investeringshorisont, risikoprofil eller præferencer ikke kan inddrages. Det afhænger af den enkelte investors personlige forhold og målsætning, om en bestemt investering eller investeringsstrategi er hensigtsmæssig, og vi anbefaler, at man rådfører sig med sin investeringsrådgiver, inden en eventuel beslutning om investering tages.PMINDI kan findes via Nordnet (https://www.nordnet.dk/markedet/investeringsforeninger-liste/18148998-portfolio-manager-new-deal-invest), Saxo Bank (https://www.saxoinvestor.dk/investor/page/product/Fund/38109485) eller ved at søge på ”DK0062499810” i din egen netbank.PMINDI er kun egnet for investorer med høj risikovillighed og en investeringshorisont på mindst 5 år. Alt investering medfører risiko, herunder potentielt tab af kapital. Historisk afkast er ikke en indikator for fremtidigt afkast, der kan afvige meget eller være negativt.Læs PRIIP KID for PMINDI for fulde risikoscenarier: https://fundmarket.dk/newdeal-invest-kl-n/. Overvej risici og fordele nøje før investering.Læs mere om risici her: https://newdealinvest.dk/risici/ og generelt om investeringsforeningen på www.newdealinvest.dk.Vil du have en månedlig oversigt over alle positionerne i PMINDI? Så skriv dig op til nyhedsbrevet her:https://newdealinvest.dk/nyhedsbrev/. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Michel Amar, CEO of DigiPower X (DGXX), breaks down the stock's incredible six-month rise… how the company's Supermicro (SMCI) partnership will drive massive growth… and why DGXX's market cap could soar from $250M to over $2B. In this episode: Welcome back Michel Amar, CEO of DigiPower X [2:45] DGXX's incredible six-month rise: What's driving the upside? [3:12] How the Supermicro partnership will spur massive growth [7:13] Why DGXX's market cap could soar from $250M to over $2B [9:53] Investors shouldn't worry about stock dilution [23:22] DGXX is going all in on AI [29:09] 2026 and beyond: Growth forecasts [34:24] Our next Curzio One private placement is coming up [42:29] Did you like this episode? Get more Wall Street Unplugged FREE each week in your inbox. Sign up here: https://curzio.me/syn_wsu Find Wall Street Unplugged podcast… --Curzio Research App: https://curzio.me/syn_app --iTunes: https://curzio.me/syn_wsu_i --Stitcher: https://curzio.me/syn_wsu_s --Website: https://curzio.me/syn_wsu_cat Follow Frank… X: https://curzio.me/syn_twt Facebook: https://curzio.me/syn_fb LinkedIn: https://curzio.me/syn_li

Die US-Börsen starten schwächer in den Dezember. Der S&P 500 fällt um 0,4 Prozent, die Nasdaq um 0,5 Prozent und der Dow gibt rund 180 Punkte nach. Vor allem der Tech-Sektor steht unter Druck: Broadcom verliert mehr als 3 Prozent, Super Micro über 2 Prozent – ein Hinweis auf weiteres Profit-Taking im KI-Bereich. Einzige Ausnahme ist Synopsys, die Aktie springt deutlich an, nachdem Nvidia eine Investition angekündigt hat. Bitcoin rutscht parallel mehr als fünf Prozent ab und handelt wieder unter 87.000 Dollar – die Kryptowährung tut sich seit Wochen schwer, die Marke von 90.000 Dollar nachhaltig zurückzuerobern. Die Wall Street kommt zwar aus einer sehr starken Thanksgiving-Woche, doch zum Start in den Dezember spricht die Saisonalität eigentlich für Rückenwind: Historisch steigt der S&P 500 im Schnitt um gut ein Prozent. Doch das heutige Bild zeigt, dass der Markt eine technische Bereinigung durchläuft und auf neue Impulse wartet – insbesondere auf die Fed-Entscheidung kommende Woche. Der ISM-Industrieindex fällt für November auf 48,2 Punkte und bleibt damit klar in der Schrumpfzone. Schwächere neue Aufträge und sinkende Lieferzeiten belasten das Bild, während Lagerbestände steigen und die Preise leicht anziehen. Abonniere den Podcast, um keine Folge zu verpassen! ____ Folge uns, um auf dem Laufenden zu bleiben: • X: http://fal.cn/SQtwitter • LinkedIn: http://fal.cn/SQlinkedin • Instagram: http://fal.cn/SQInstagram

Ahold Delhaize overtreft de verwachting van analisten. De winst én omzet vallen in het derde kwartaal hoger uit. Het bedrijf gaat daarom (opnieuw) eigen aandelen inkopen. Voor 1 miljard euro. Ook investeert het supermarktbedrijf in AI. Deze aflevering hebben we het over die stap. Gaat het Ahold verder helpen? De marges verbeteren nu al, maar kunnen misschien nóg meer groeien. Hebben we het ook over de Amerikaanse shutdown. Dat is nu officieel de langste uit de Amerikaanse geschiedenis. Al 36 dagen zit de boel daar op slot en een einde is nog lang niet in zicht. Wij proberen te kijken wat dat betekent voor de Amerikaanse economie, voor de beurs en voor jou als belegger.Een shutdown die de beursgang van The Magnum Ice Cream Company in de war schopte. Die werd vertraagd, maar er kwam vandaag toch goed nieuws. Op 8 december gaat de ijsjestak alsnog naar de beurs van New York, Londen én Amsterdam! Kwartaalcijfers zijn er ook van Toyota, Novo Nordisk en Wolters Kluwer. We vertellen je waar je op moet letten. Waarom de cijfers van McDonalds zo goed zijn én over een Nederlands beursbedrijf dat mogelijk het Damrak gaat verlaten.See omnystudio.com/listener for privacy information.

AMD mit leichten Gewinnmitnahmen, Arista Networks, Pinterest und Super Micro unter Druck – vor allem wegen dünner Margen. Astera Labs dagegen überzeugt mit starken Zahlen und optimistischem Ausblick. Auch außerhalb des Tech-Sektors tut sich einiges: Rivian profitiert von robusten Ergebnissen, Amgen glänzt mit beeindruckenden Zahlen. Im Konsumbereich zeigt sich Schwäche: McDonald's verfehlt die Erwartungen, CAVA senkt den Ausblick und Apollo zieht sich offenbar von der geplanten Übernahme von Papa John's zurück. Um so erfreulicher, dass der ISM-Dienstleistungsindex für den Oktober über den Zielen lag. Abonniere den Podcast, um keine Folge zu verpassen! ____ Folge uns, um auf dem Laufenden zu bleiben: • X: http://fal.cn/SQtwitter • LinkedIn: http://fal.cn/SQlinkedin • Instagram: http://fal.cn/SQInstagram

Die Futures erholen sich deutlich von den Tiefs – nach dem starken Abverkauf im Nasdaq 100 sehen wir das klassische Muster: eine Gegenbewegung nach unten überverkauften Tech-Werten. Laut Bespoke Investment geht es historisch am Folgetag oft wieder bergauf. AMD mit leichten Gewinnmitnahmen, Arista Networks, Pinterest und Super Micro unter Druck – vor allem wegen dünner Margen. Astera Labs dagegen überzeugt mit starken Zahlen und optimistischem Ausblick. Auch außerhalb des Tech-Sektors tut sich einiges: Rivian profitiert von robusten Ergebnissen, Amgen glänzt mit beeindruckenden Zahlen. Im Konsumbereich zeigt sich Schwäche: McDonald's verfehlt die Erwartungen, CAVA senkt den Ausblick – und Apollo zieht sich offenbar von der geplanten Übernahme von Papa John's zurück. Heute richtet sich der Blick auf den ISM-Dienstleistungsindex (16 Uhr MEZ). Fällt der schwach aus, könnte der Wall Street erneut Gegenwind drohen. Ein Podcast - featured by Handelsblatt. +++ Alle Rabattcodes und Infos zu unseren Werbepartnern findet ihr hier: https://linktr.ee/wallstreet_podcast +++ +++ Hinweis zur Werbeplatzierung von Meta: https://backend.ad-alliance.de/fileadmin/Transparency_Notice/Meta_DMAJ_TTPA_Transparency_Notice_-_Ad_Alliance_approved.pdf +++ Der Podcast wird vermarktet durch die Ad Alliance. Die allgemeinen Datenschutzrichtlinien der Ad Alliance finden Sie unter https://datenschutz.ad-alliance.de/podcast.html Die Ad Alliance verarbeitet im Zusammenhang mit dem Angebot die Podcasts-Daten. Wenn Sie der automatischen Übermittlung der Daten widersprechen wollen, klicken Sie hier: https://datenschutz.ad-alliance.de/podcast.html Impressum: https://www.360wallstreet.de/impressum

Before Supermicro's (SMCI) earnings after Tuesday's closing bell, Alex Coffey pointed out the recent price performance and its impact on options, where traders braced for a 10% move in the stock. He believes that volatile of a move heavily weighs on Supermicro's guidance.======== Schwab Network ========Empowering every investor and trader, every market day. Subscribe to the Market Minute newsletter - https://schwabnetwork.com/subscribeDownload the iOS app - https://apps.apple.com/us/app/schwab-network/id1460719185Download the Amazon Fire Tv App - https://www.amazon.com/TD-Ameritrade-Network/dp/B07KRD76C7Watch on Sling - https://watch.sling.com/1/asset/191928615bd8d47686f94682aefaa007/watchWatch on Vizio - https://www.vizio.com/en/watchfreeplus-exploreWatch on DistroTV - https://www.distro.tv/live/schwab-network/Follow us on X – https://twitter.com/schwabnetworkFollow us on Facebook – https://www.facebook.com/schwabnetworkFollow us on LinkedIn - https://www.linkedin.com/company/schwab-network/ About Schwab Network - https://schwabnetwork.com/about

RBA kept Cash Rate unchanged at 3.60%, as expected; judged some of the increase in underlying inflation in Q3 was due to temporary factors.European bourses are lower across the board with sentiment downbeat; US equity futures are in the red, NQ -1.3%.DXY briefly returned to a 100 handle, GBP slipped post-Reeves, who failed to reiterate her tax-related pledges, Antipodeans lag.Gilts outperform amid tax rise speculation, USTs await Fed speak.WTI and Brent slip to lows given the risk tone, but XAU fails to benefit and sits sub-4k/oz.Looking ahead, US RCM/TIPP, New Zealand Jobs, RBNZ FSR, BoJ Minutes (Sep), French Assembly PLF Vote, Speakers including ECB's Nagel and Balz, BoE's Breeden & Fed's Bowman. Earnings from Fresenius MC, Ferrari; AMD, Supermicro, Marathon, Pfizer & Uber.Read the full report covering Equities, Forex, Fixed Income, Commodites and more on Newsquawk

APAC stocks were mostly subdued following the mixed lead from Wall St, where the majority of sectors declined but tech outperformed.RBA kept Cash Rate unchanged at 3.60%, as expected; judged some of the increase in underlying inflation in Q3 was due to temporary factors.European equity futures indicate a lower cash market open with Euro Stoxx 50 future down 0.8% after the cash market closed with gains of 0.3% on Monday.DXY is flat, antipodeans lag with AUD softer post-RBA. JPY outperforms, underpinned by a haven bid and more verbal intervention.In a rare pre-budget press conference today, UK Chancellor Reeves will indicate she is prepared to break Labour's manifesto promise not to raise income tax, according to The Telegraph.Looking ahead, highlights include Canadian Trade, US RCM/TIPP, New Zealand Jobs, RBNZ FSR, BoJ Minutes (Sep), French Assembly PLF vote process begins, ECB's Lagarde, Nagel and Balz, BoE's Breeden & Fed's Bowman, Supply from UK & Germany.Earnings from Phillips, Evonik, Fresenius MC, Ferrari, BP; AMD, Supermicro, Marathon, Pfizer & Uber.Read the full report covering Equities, Forex, Fixed Income, Commodites and more on Newsquawk

Die CEOs von Morgan Stanley und Goldman Sachs warnen, während der HSBC-Chef vor überzogenen KI-Investitionen warnt. Michael Burry setzt auf fallende Kurse bei Palantir und NVIDIA. Trotz starker Zahlen stehen Palantir, Shopify und Uber unter Druck – Anleger nehmen Gewinne mit. Auch außerhalb des Tech-Sektors enttäuschen viele Unternehmen: Clorox, Eastman Chemical, Hims & Hers, Norwegian Cruise, Stanley Black & Decker, Harley-Davidson, Molson Coors und Marriott. Lichtblick: Pfizer hebt Prognose an. Nachbörslich folgen noch AMD, Arista Networks und Super Micro.Kurz gesagt: Tech-Aktien wanken, Gewinnmitnahmen nehmen zu – die Wall Street steht unter Druck. Abonniere den Podcast, um keine Folge zu verpassen! ____ Folge uns, um auf dem Laufenden zu bleiben: • X: http://fal.cn/SQtwitter • LinkedIn: http://fal.cn/SQlinkedin • Instagram: http://fal.cn/SQInstagram

Die CEOs von Morgan Stanley und Goldman Sachs warnen, während der HSBC-Chef vor überzogenen KI-Investitionen warnt. Michael Burry setzt auf fallende Kurse bei Palantir und NVIDIA. Trotz starker Zahlen stehen Palantir, Shopify und Uber unter Druck – Anleger nehmen Gewinne mit. Auch außerhalb des Tech-Sektors enttäuschen viele Unternehmen: Clorox, Eastman Chemical, Hims & Hers, Norwegian Cruise, Stanley Black & Decker, Harley-Davidson, Molson Coors und Marriott. Lichtblick: Pfizer hebt Prognose an. Nachbörslich folgen noch AMD, Arista Networks und Super Micro.Kurz gesagt: Tech-Aktien wanken, Gewinnmitnahmen nehmen zu – die Wall Street steht unter Druck. Ein Podcast - featured by Handelsblatt. +++ Alle Rabattcodes und Infos zu unseren Werbepartnern findet ihr hier: https://linktr.ee/wallstreet_podcast +++ +++ Hinweis zur Werbeplatzierung von Meta: https://backend.ad-alliance.de/fileadmin/Transparency_Notice/Meta_DMAJ_TTPA_Transparency_Notice_-_Ad_Alliance_approved.pdf +++ Der Podcast wird vermarktet durch die Ad Alliance. Die allgemeinen Datenschutzrichtlinien der Ad Alliance finden Sie unter https://datenschutz.ad-alliance.de/podcast.html Die Ad Alliance verarbeitet im Zusammenhang mit dem Angebot die Podcasts-Daten. Wenn Sie der automatischen Übermittlung der Daten widersprechen wollen, klicken Sie hier: https://datenschutz.ad-alliance.de/podcast.html Impressum: https://www.360wallstreet.de/impressum

Ein Paukenschlag im Pharmasektor treibt die Börse zum Wochenstart an: Kimberly Clark übernimmt Kenvue für fast 50 Milliarden Dollar! Auch aus China und den USA gibt es versöhnliche Töne – ein weiteres Signal für Entspannung zwischen den Supermächten. Gerüchte um Moderna machen weiter die Runde: Steht auch hier ein Verkauf bevor? Währenddessen zeigt sich die Berichtssaison von ihrer starken Seite – 43% der Unternehmen haben ihre Prognosen angehoben, und laut FactSet liegt das Gewinnwachstum im dritten Quartal bei soliden 10,7%. Berkshire Hathaway glänzt mit besser als erwarteten Zahlen, die Aktie startet freundlich in die Woche. Und es bleibt spannend: Palantir meldet heute Abend, AMD, Arista Networks, Super Micro, Shopify und Spotify folgen am Dienstag. Ein Podcast - featured by Handelsblatt. +++ Alle Rabattcodes und Infos zu unseren Werbepartnern findet ihr hier: https://linktr.ee/wallstreet_podcast +++ +++ Hinweis zur Werbeplatzierung von Meta: https://backend.ad-alliance.de/fileadmin/Transparency_Notice/Meta_DMAJ_TTPA_Transparency_Notice_-_Ad_Alliance_approved.pdf +++ Der Podcast wird vermarktet durch die Ad Alliance. Die allgemeinen Datenschutzrichtlinien der Ad Alliance finden Sie unter https://datenschutz.ad-alliance.de/podcast.html Die Ad Alliance verarbeitet im Zusammenhang mit dem Angebot die Podcasts-Daten. Wenn Sie der automatischen Übermittlung der Daten widersprechen wollen, klicken Sie hier: https://datenschutz.ad-alliance.de/podcast.html Impressum: https://www.360wallstreet.de/impressum

Amazon bekommt einen $38 Mrd. Auftrag von OpenAi, was den Nadsaq anfacht. Ansonsten ist die Tendenz trotz eines Mega-Deal im Pharmabereich und einer weiteren Annäherung zwischen China und den USA uneinheitlich. Kenvue wird für fast $50 Mrd. von Kimberly Clark übernommen. Letzte Woche kursierten Gerüchte, dass sich auch Moderna zum Verkauf aufgestellt hat. Die Aktionäre werden in Cash und Aktien angefunden. Was Quartalszahlen betrifft, hatte wir letzte Woche den Zenit der Meldungen. Es haben nicht nur ungewöhnlich viele Unternehmen die Ertragsziele geschlagen. 43% der Firmen, die sich zu den Aussichten äußerten, haben die Prognosen angehoben. Wir sehen für Q3 nun ein solides Gewinnwachstum von 10,7%, berichtet FactSet. Berkshire Hathaway konnte am Wochenende die Erwartungen ebenfalls übertreffen, mit der Aktie vor dem Opening freundlich. Im weiteren Wochenverlauf stehen erneut einige wichtige Tech-Ergebnisse an. Heute Abend meldet Palantir, gefolgt von AMD, Arista Networks, Super Micro, Shopify und Spotify am Dienstag. Abonniere den Podcast, um keine Folge zu verpassen! ____ Folge uns, um auf dem Laufenden zu bleiben: • X: http://fal.cn/SQtwitter • LinkedIn: http://fal.cn/SQlinkedin • Instagram: http://fal.cn/SQInstagram

In Folge 367 von Binärgewitter Talk gibt's wieder Tech-Geschichten mit ordentlich Würze: Ingo jongliert Konferenz-Chaos, Felix und Sebastian streiten über Kalender-Logik, und Markus verabschiedet heimlich seine Apps ins digitale Jenseits. Dazu gibt's Nostalgie-Laptops, KI-Halluzinationen und Hacktoberfest-Vibes – kurzum: ein bunter Tech-Cocktail mit Insider-Witzen und Nerd-Charme. Blast from the Past neues (altes) thinkpad standby tut -> unendlich batterie Nvidia T14 g1 mit i7 und nvidia Toter der Woche Android auf FireTV Sticks nova launcher for android Untoter der Woche AI der Woche Warum KI-Modelle haluzinieren SABTA: Sicheres Auftreten bei totaler Ahnungslosigkeit KI Gewinnt Programmierwettbewerb IPPC Warum KI im Wettbewerb brilliert aber im alltag scheitert First Malicious MCP in the Wild AI generated Workslop is destroying productivity Gema vs ChatGPT ai hosts in youtube music ai powered stan lee News Anna’s Archive von deutschen Internetanbietern gesperrt Supermicro server motherboards can be infected with unremovable malware FireTV Exploit WhatsApp und Signal: Messenger-Tracking ohne Spuren Verbandsklage gegen die illegale Meta-Überwachung Amazon zahlt 2,5 Milliarden Dollar in Rechtsstreit um Prime-Abos IG-Nobelpreis Nextcloud Community Conference Nextcloud Hub 25 Autumn nächste RadioTux Bald Nextcloud Community Conference 2025 no hybrid or virtual participation this year mehrere Tracks Besucher 340 Ios App rewrite, MacOS Client rewrite - faster drag and drop between 2 open nextcloud apps / ios26 15% less database queries E2E auch im Webinterface möglich - passwort muss eingegeben werden spiele museeum JRuby and JDK 25: Startup Time with AOTCache Themen 39c3 call for participation Alternativen für US Tech Produkte Gruppen im Fediverse Smart Ergonomic Keyboard neo layout 3D-Druck der Woche Gridfinity Mimimi der Woche nvidia compilation time (2 tage für alle dependencies von openai-whisper) Tuxedo Tastatur will nicht immer… Lesefoo Finding the hidden Risks in the Battery Supply Chain Turn Android Phone into batteryless home server Picks Tiptoi Stoppt die #Vorratsdatenspeicherung 2.0 Bundesweiten Aktionstage Netzpolitik & Demokratie hacktoberfest hackergarten ocenaudio SF Parking Hackernews Article Stuttgart Park Control

In this episode, host Paige West speaks with Matthias Huber, Sr. Director, Solutions Manager, IoT/Embedded & Edge Computing, Supermicro, all about accelerating Edge AI infrastructure for predictive and Generative AI.

British authorities arrest a man in connection with the Collins Aerospace ransomware attack. CISA says attackers breached a U.S. federal civilian executive branch agency last year. Researchers uncover two high-severity vulnerabilities in Supermicro server motherboards. A Las Vegas casino operator confirms a cyber attack. Analysts track multiple large-scale, automated email phishing campaigns. Libraesva issues an emergency patch for its Email Security Gateway. Our guest is Jason Clark, Chief Strategy Officer (CSO) at Cyera, tackling the security threat of Agentic AI. Robocars get misdirected by mirrors.  Remember to leave us a 5-star rating and review in your favorite podcast app. Miss an episode? Sign-up for our daily intelligence roundup, Daily Briefing, and you'll never miss a beat. And be sure to follow CyberWire Daily on LinkedIn. CyberWire Guest On our Industry Voices segment, we are joined by Jason Clark, Chief Strategy Officer (CSO) at Cyera, discussing tackling the security industry's biggest threat: Agent AI. If you want to hear the full conversation from Jason, you can check it out here. Selected Reading UK police arrest man over hack that affected European airports (Reuters) AI tool helped recover £500m lost to fraud, government says (BBC) CISA says hackers breached federal agency using GeoServer exploit (Bleeping Computer) Supermicro server motherboards can be infected with unremovable malware (Ars Technica) Boyd Gaming Suffers Cyberattack, Data Breach (Casino.org) Email Threat Radar – September 2025 (Barracuda) Revamped Phishing Techniques: How Telegram and Front-End Hosting Platforms Scale Campaigns (Forescout) GitHub notifications abused to impersonate Y Combinator for crypto theft (Bleeping Computer) Libraesva ESG issues emergency fix for bug exploited by state hackers (Bleeping Computer) Fooling a self-driving car with mirrors on traffic cones (The Register) Share your feedback. What do you think about CyberWire Daily? Please take a few minutes to share your thoughts with us by completing our brief listener survey. Thank you for helping us continue to improve our show. Want to hear your company in the show? You too can reach the most influential leaders and operators in the industry. Here's our media kit. Contact us at cyberwire@n2k.com to request more info. The CyberWire is a production of N2K Networks, your source for strategic workforce intelligence. © N2K Networks, Inc. Learn more about your ad choices. Visit megaphone.fm/adchoices

Distracting the Analyst for Fun and Profit Our undergraduate intern, Tyler House analyzed what may have been a small DoS attack that was likely more meant to distract than to actually cause a denial of service https://isc.sans.edu/diary/%5BGuest%20Diary%5D%20Distracting%20the%20Analyst%20for%20Fun%20and%20Profit/32308 GitHub s plan for a more secure npm supply chain GitHub outlined its plan to harden the supply chain, in particular in light of the recent attack against npm packages https://github.blog/security/supply-chain-security/our-plan-for-a-more-secure-npm-supply-chain/ SolarWinds Web Help Desk AjaxProxy Deserialization of Untrusted Data Remote Code Execution Vulnerability (CVE-2025-26399) SolarWinds Web Help Desk was found to be susceptible to an unauthenticated AjaxProxy deserialization remote code execution vulnerability that, if exploited, would allow an attacker to run commands on the host machine. This vulnerability is a patch bypass of CVE-2024-28988, which in turn is a patch bypass of CVE-2024-28986. https://www.solarwinds.com/trust-center/security-advisories/cve-2025-26399 Vulnerabilities in Supermicro BMC Firmware CVE-2025-7937 CVE-2025-6198 Supermicro fixed two vulnerabilities that could allow an attacker to compromise the BMC with rogue firmware. https://www.supermicro.com/en/support/security_BMC_IPMI_Sept_2025

The 5 things you need to know before the stock market opens today: Lawyers for President Trump are asking an appeals court to let his bid to fire Federal Reserve Governor Lisa Cook continue before next week's Open Market Committee meeting, Treasury Secretary Scott Bessent continues interviewing candidates for next Fed chair, Adobe shares are heading up, RH is under pressure, and AI tech firm Super Micro has begun to ship Nvidia Blackwell chips worldwide. Squawk Box is hosted by Joe Kernen, Becky Quick and Andrew Ross Sorkin.  Follow Squawk Pod for the best moments, interviews and analysis from our TV show in an audio-first format. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The 5 things you need to know before the stock market opens today: Lawyers for President Trump are asking an appeals court to let his bid to fire Federal Reserve Governor Lisa Cook continue before next week's Open Market Committee meeting, Treasury Secretary Scott Bessent continues interviewing candidates for next Fed chair, Adobe shares are heading up, RH is under pressure, and AI tech firm Super Micro has begun to ship Nvidia Blackwell chips worldwide. Squawk Box is hosted by Joe Kernen, Becky Quick and Andrew Ross Sorkin.  Follow Squawk Pod for the best moments, interviews and analysis from our TV show in an audio-first format.

Na jaren van van een gebrek aan beursgangen, gaat het over een paar weken gebeuren. Na de zomer komen er bedrijven naar de beurs. Dat verwachten ze bij Goldman Sachs. Alle groenen staan op sein in Europa, zeggen ze tegen het FD. Wij kijken deze aflevering wat dat voor jou als belegger betekent. Wat voor bedrijven komen er dan naar de Amsterdamse beurs bijvoorbeeld? En zijn dat ook aandelen die je moet hebben?Hebben we het ook over een mogelijke beursgang van webbrowser Chrome. Geen idee of dat gaat gebeuren, maar wél dat er ineens enorme interesse in het onderdeel van Google is. Een startup biedt 35 miljard dollar. Een ander (naar verluidt) 50 miljard. Wanneer gaat Google overstag?Over afscheid nemen gesproken: het was bekend dat president Trump af wil van Fed-baas Jerome Powell. Maar nu blijkt ook dat er een heel elftal aan mogelijke vervangers is. We bespreken de namen en wat je er van kan verwachten.Ook kan je verwachten dat dit in de uitzending zit: De Japanse beurs tikt een record aan, net als Amerikaanse indices. Is dat terecht? Trump wil dat Goldman Sachs z'n hoofdeconoom ontslaat Shell lijdt een pijnlijke nederlaag En China krijgt gelijk. Er zitten trackers in Amerikaanse chips... See omnystudio.com/listener for privacy information.

In this week's episode, hosts Daniel Newman and Patrick Moorhead dissect a whirlwind of tech news! From Palantir, Lip-Bu, Trump, and tariffs to the latest in GPT-5, they break down the key announcements and market shifts that are shaping the industry:    Tech Industry News and Analysis: Trump's tariff threats on semiconductors and chips. Apple's investment commitments in the US. Rumors about GPT-5 release and its potential impact.   Intel Leadership Challenges: Trump's call for Intel CEO Lip-Bu Tan's removal. Analysis of Intel's missed opportunities in the US chip manufacturing push.   Palantir's Meteoric Rise: Discussion of Palantir's market valuation and performance. Analysis of the company's government contracts and AI positioning.   Other Tech Company Performances: Lattice Semiconductor's positive market reception. IonQ's progress in quantum computing. Astera's growth and dependence on Nvidia.   Impact of AI on Knowledge Work: How advancements in AI, particularly with the release of GPT-5, could significantly impact knowledge-based industries and consulting firms.   Challenges for Chip Manufacturers: Various challenges faced by chip manufacturers, including Super Micro's underperformance and the potential impact on competitors like Dell and HPE in the AI server market. For a deeper dive into each topic, please click on the links above. Be sure to subscribe to The Six Five Pod so you never miss an episode.

In der heutigen Folge sprechen die Finanzjournalisten Anja Ettel und Holger Zschäpitz über einen smarten Abo-Trick der New York Times, Margen-Flaute bei AirBnB und Hoffnung auf ein serienreifes Happy End bei Disney. Außerdem geht es um Apple, Amazon, Tesla, Nvidia, Intel, McDonald's, Uber, Bayer, Siemens Energy, Zalando, Beiersdorf, Vonovia, TAG, Aroundtown, Opendoor Technologies, Snap, Lucid, AMD, Super Micro, Shopify, Match Group, Bumble, Softbank, OpenAI, Novo Nordisk und Solactive China Humanoid Robotics Index. Wir freuen uns an Feedback über aaa@welt.de. Noch mehr "Alles auf Aktien" findet Ihr bei WELTplus und Apple Podcasts – inklusive aller Artikel der Hosts und AAA-Newsletter. Hier bei WELT: https://www.welt.de/podcasts/alles-auf-aktien/plus247399208/Boersen-Podcast-AAA-Bonus-Folgen-Jede-Woche-noch-mehr-Antworten-auf-Eure-Boersen-Fragen.html. Der Börsen-Podcast Disclaimer: Die im Podcast besprochenen Aktien und Fonds stellen keine spezifischen Kauf- oder Anlage-Empfehlungen dar. Die Moderatoren und der Verlag haften nicht für etwaige Verluste, die aufgrund der Umsetzung der Gedanken oder Ideen entstehen. Hörtipps: Für alle, die noch mehr wissen wollen: Holger Zschäpitz können Sie jede Woche im Finanz- und Wirtschaftspodcast "Deffner&Zschäpitz" hören. +++ Werbung +++ Du möchtest mehr über unsere Werbepartner erfahren? Hier findest du alle Infos & Rabatte! https://linktr.ee/alles_auf_aktien Impressum: https://www.welt.de/services/article7893735/Impressum.html Datenschutz: https://www.welt.de/services/article157550705/Datenschutzerklaerung-WELT-DIGITAL.html

Carl Quintanilla, David Faber, and Leslie Picker discussed the latest on the earnings front: starting with AMD's China concerns and the disappointing guide sending Super Micro shares slumping – along with the better-than-feared numbers boosting McDonalds shares with one analyst forecasting even more gains ahead. Plus: the President announcing an additional 25% tariff on goods from India as Apple announces an additional $100 billion investment to beef up U.S. manufacturing… Hear former Goldman Asset Management Chairman Jim O'Neill's take on all these fast changing tariff headlines.   Also in focus: how consumer credit is holding up with the CEO of AI lender Upstart, fresh off earnings that have shares falling double digits. A deep-dive on Disney's big sports bet along with key takeaways from quarterly results. Hear the interim CEO of Lucid break down the road ahead for his company – and the challenges that remain for the EV market… Along with the staggering numbers behind a new generation of “AI Billionaires”.

Today, we await the imminent announcement of the identity of the next Fed Chair as Trump has two empty Fed board seats to play with and could fill one of them with his next Fed Chair nominee. We also talk earnings yesterday (AMD, Supermicro and Novo Nordisk) and upcoming earnings today, whether the USD bears are set to get the upper hand again here, key resistance that is still in place for US equities, some great links and more. Today's pod hosted by Saxo Global Head of Macro Strategy John J. Hardy. Links discussed on the podcast can be found on the John J. Hardy substack (with a one or two hour delay from the time of the podcast release). Read daily in-depth market updates from the Saxo Market Call and the Saxo Strategy Team here. Please reach out to us at marketcall@saxobank.com for feedback and questions. Click here to open an account with Saxo. Intro and outro music by AShamaluevMusic

From Wall Street to Main Street, the latest on the markets and what it means for your money. Updated regularly on weekdays, featuring CNBC expert analysis and sound from top business newsmakers. Anchored by CNBC's Jill Schneider.

In der heutigen Folge sprechen die Finanzjournalisten Anja Ettel und Nando Sommerfeldt über die Pizza-Delle, ein Achtungszeichen von Arista und die Wende bei BP. Außerdem geht es um Palantir, Pfizer, DuPont, Yum Brands, Domino's Pizza Group, Snap, Meta, AMD, Microsoft, Super Micro, Dell, Hewlett Packard Enterprise, Hims & Hers, Novo Nordisk, Coinbase, BP, Infineon, Continental, Fresenius Medical Care, Aurubis, Fraport, Invesco Global Buyback Achievers ETF (WKN: A114UD), SAP, Wells Fargo, Shell, iShares Core MSCI World (WKN: A0RPWH), FTSE All-World (WKN: A2PKXG), iShares STOXX Global Select Dividend 100 ETF (WKN: A0F5UH) und VanEck Morningstar DM Dividend Leaders (A2JAHJ). Wir freuen uns an Feedback über aaa@welt.de. Noch mehr "Alles auf Aktien" findet Ihr bei WELTplus und Apple Podcasts – inklusive aller Artikel der Hosts und AAA-Newsletter. Hier bei WELT: https://www.welt.de/podcasts/alles-auf-aktien/plus247399208/Boersen-Podcast-AAA-Bonus-Folgen-Jede-Woche-noch-mehr-Antworten-auf-Eure-Boersen-Fragen.html. Der Börsen-Podcast Disclaimer: Die im Podcast besprochenen Aktien und Fonds stellen keine spezifischen Kauf- oder Anlage-Empfehlungen dar. Die Moderatoren und der Verlag haften nicht für etwaige Verluste, die aufgrund der Umsetzung der Gedanken oder Ideen entstehen. Hörtipps: Für alle, die noch mehr wissen wollen: Holger Zschäpitz können Sie jede Woche im Finanz- und Wirtschaftspodcast "Deffner&Zschäpitz" hören. +++ Werbung +++ Du möchtest mehr über unsere Werbepartner erfahren? Hier findest du alle Infos & Rabatte! https://linktr.ee/alles_auf_aktien Impressum: https://www.welt.de/services/article7893735/Impressum.html Datenschutz: https://www.welt.de/services/article157550705/Datenschutzerklaerung-WELT-DIGITAL.html

Het was hét aandeel van het jaar. De AEX-lieveling, het aandeel dat het het beste deed. Maar vandaag kwamen er scheurtjes in dat succes. ABN Amro kan de torenhoge verwachtingen van beleggers toch niet waarmaken.Het overtrof de winstverwachting én het koopt voor 250 miljoen euro aan eigen aandelen in, maar dat alles is niet genoeg voor beleggers. Deze aflevering duiken we in de resultaten van ABN en kijken of het een tijdelijk dipje is of dat beleggers (langer gaan) afhaken.Hebben we het ook over het online succes van Ahold Delhaize. Beleggers moesten er een kwart eeuw (!) op wachten, maar dan heb je ook wat. Winst in dit geval, want de online tak van Ahold is eindelijk winstgevend.Verder bespreken we de cijfers van Disney. Topman Bob Iger heeft de boel helemaal weer op de rit en verhoogt ook de winstverwachting. De kwakkelende streamingtak is inmiddels verandert in dé concurrent van Netflix. Waar eindigt dit?Dat is ook de vraag die aandeelhouders van Snap hebben. Het moederbedrijf komt met ouderwets slecht nieuws. Nieuws dat de beurswaarde een rotschop geeft. Verder deze aflevering: Kersverse ceo van NovoNordisk gaat ingrijpen AMD en SuperMicro Computer hebben één ding gemeen: teleurstelling Meme-aandeel OpenDoor wordt toch weer gedumpt Uber gaat voor 20 (!) miljard dollar aan eigen aandelen inkopen McDonald's verrast met goede cijfers See omnystudio.com/listener for privacy information.

Erfahre hier mehr über unseren Partner Scalable Capital - dem Broker mit Flatrate und Zinsen. Alle weiteren Infos gibt's hier: scalable.capital/oaws. Aktien + Whatsapp = Hier anmelden. Lieber als Newsletter? Geht auch. Das Buch zum Podcast? Jetzt lesen. Infineon verbessert sich. Pfizer spart. Vertex scheitert in Studie. Hims & Hers widerspricht Novo Nordisk. Alcon kauft Staar Surgical. Arista kann KI. AMD kann KI bisschen. Super Micro kann grad keine KI. Das PayPal und Amazon Südamerikas wächst und wächst. Nur die Marge von MercadoLibre (WKN: A0MYNP) tut das nicht. DHL (WKN: 555200) schlägt UPS & FedEx. Aber schlägt DHL auch den Markt? Diesen Podcast vom 06.08.2025, 3:00 Uhr stellt dir die Podstars GmbH (Noah Leidinger) zur Verfügung.

Most people think building AI infrastructure is all about software. But the real bottlenecks? Power, cooling, and optimizing hardware.Vik Malyala, Managing Director at Supermicro, reveals the surprising struggles in building data centers to meet the AI demand.He explains:▫️ Why most data centers aren't ready for the AI boom▫️ How Supermicro optimizes hardware for maximum efficiency▫️ Why 200 kilowatts per rack is just the beginning▫️ The future of liquid cooling and energy sustainability▫️ How AI will move from massive clusters to the edge▫️ What every business needs to know before scaling AI infrastructureIf you want to understand the future of AI, hardware, and data centers, this is a must-watch.Follow more of the Liftoff with Keith:- Spotify: https://open.spotify.com/show/3cFpLXfYvcUsxvsT9MwyAD- Apple Podcasts: https://podcasts.apple.com/us/podcast/liftoff-with-keith-newman/id1560219589- Substack: https://keithnewman.substack.com/- LinkedIn: https://www.linkedin.com/company/liftoffwithkeith/- Newman Media Studios: https://newmanmediastudios.com/For sponsorship inquiries, please contact: sponsorships@wherewithstudio.com

Notas del Show: En este episodio cubrimos los eventos más relevantes antes de la apertura del mercado: • Wall Street se estabiliza tras presión arancelaria: Futuros moderadamente al alza tras caídas por anuncios de tarifas del 25–40 % a 14 países y hasta 200 % a fármacos. Hoy se esperan las minutas del FOMC. Ayer: $SPX -0.07 %, $US100 plano, $INDU -0.4 %. • Super Micro apuesta por Europa y Asia: $SMCI ampliará su planta en Países Bajos y evalúa nuevas fábricas en la región para enfrentar demanda de IA. También sumará capacidad en Malasia y Taiwán. Su CEO destacó que, pese a retrasos por GPUs Blackwell de $NVDA, la demanda se mantiene fuerte. • Merck compra Verona Pharma por $10B: $MRK adquirirá $VRNA por 107 USD/ADR (+23 % de prima). Verona comercializa Ohtuvayre, inhalador aprobado por la FDA con potencial en varias enfermedades respiratorias. El cierre se espera para Q4 2025. $VRNA +20 % premarket. • Starbucks atrae fondos en China: $SBUX recibió interés de ~30 fondos para invertir en su filial china, valorada entre $5B–$10B. Mantendría 30 % de participación. Goldman Sachs asesora la operación. China representa ~8 % de sus ingresos globales. • Jeff Bezos vende más acciones de Amazon: $AMZN | Bezos vendió 3 millones de acciones por $0.666B en julio, parte de un plan para desprenderse de hasta 25 millones de títulos (hasta $4.75B) antes de mayo 2026. Sigue siendo el mayor accionista con 900M de acciones (~$200B). Una jornada con foco en adquisiciones, expansión global y nuevos episodios del reordenamiento fiscal y comercial. ¡No te lo pierdas!

Welcome to Holistic Investments, where we explore the future of technology and innovation! In this in-depth interview, we sit down with Sebastian Pfeiffer, Co-Founder and Managing Director of Impossible Cloud Network (ICN), a groundbreaking decentralized cloud platform challenging the dominance of traditional cloud giants like AWS, Google Cloud, and Microsoft Azure. Sebastian takes us through the fascinating origin story of ICN, its mission to decentralize the cloud, and how it leverages a multi-service DePIN (Decentralized Physical Infrastructure Network) to deliver enterprise-grade performance.Discover how ICN is addressing critical issues like digital sovereignty, vendor lock-in, and the growing demand for edge computing in the era of AI and Web3. From its ICNT token mechanics to strategic partnerships with industry leaders like Supermicro and IoTeX, this conversation uncovers why ICN is poised to reshape the $300B+ cloud computing industry. Learn about real-world use cases, regulatory compliance in the Swiss-EU framework, and ICN's vision for a decentralized, scalable, and open cloud ecosystem.************Follow Sebastian Pfeiffer:

Michel Amar, CEO of DigiPower X (DGXX), reveals how DGXX turned a boring utility asset into an AI goldmine… the company's explosive revenue potential… why the market is missing this $750M story (for now)... and a massive tailwind for DGXX. In this episode: Welcome, Michel Amar, Chairman and CEO of DigiPower X [0:15] DGXX is soaring—here's why it's just beginning [0:41] How DGXX turned a boring utility asset into a rare AI goldmine [3:10] Bitcoin mining + AI data centers = explosive revenue potential [8:33] Why the market is missing this $750M story (for now) [9:50] A game-changing partnership to fast-track execution [11:11] A massive tailwind for DGXX: Power scarcity [15:31] This legendary investor is backing DGXX [17:35] Did you like this episode? Get more Wall Street Unplugged FREE each week in your inbox. Sign up here: https://curzio.me/syn_wsu Find Wall Street Unplugged podcast… --Curzio Research App: https://curzio.me/syn_app --iTunes: https://curzio.me/syn_wsu_i --Stitcher: https://curzio.me/syn_wsu_s --Website: https://curzio.me/syn_wsu_cat Follow Frank… X: https://curzio.me/syn_twt Facebook: https://curzio.me/syn_fb LinkedIn: https://curzio.me/syn_li

On this episode host Justin Barnes recorded live at HIMSS25 in Las Vegas. Stay tuned for the next few weeks to hear all his guests.This week his guests are Carl Brown, General Manager Business Development at Supermicro and Tony Black, Global Director, Healthcare, Privacy & Digital Transformation at Kyndryl. To stream our Station live 24/7 visit www.HealthcareNOWRadio.com or ask your Smart Device to “….Play Healthcare NOW Radio”. Find all of our network podcasts on your favorite podcast platforms and be sure to subscribe and like us. Learn more at www.healthcarenowradio.com/listen