Podcasts about fpga

Rethinking AI Compute Infrastructure: The TensorWave ApproachIn this episode, Jeff Tatarchuk, co-founder of TensorWave, shares how his deep industry experience and innovative mindset are transforming AI compute infrastructure. We explore how building specialized data centers, focusing on AMD GPUs, and creating flexible ecosystems are shaping the future of scalable AI.In this episode:The evolution of cloud companies and the rise of Neo clouds focused on AI computeTensorWave's unique strategy of deploying AMD GPUs in custom data centersLessons learned from FPGA cloud business and transitioning into GPU infrastructureThe technical challenges and solutions in scaling data centers quickly amidst power and supply chain constraintsThe importance of software ecosystems, interoperability, and supporting AMD's software stackHow TensorWave differentiates itself from purely financial arbitrage models and pure Nvidia-centric cloudsAMD's advantages in memory capacity, chiplet architecture, and software supportThe technical intricacies of CUDA versus ROCm, and efforts to build an open ecosystemFuture vision: democratized, reliable, and flexible AI compute options for enterprise and labsTimestamps:00:00 – Introduction to TensorWave and the AI compute landscape02:30 – The rise of Neo clouds and innovation waves in cloud infrastructure06:00 – How TensorWave's FPGA cloud background shaped its GPU strategy10:00 – Challenges in deploying large data centers: power, supply chain, and permitting14:00 – Building and scaling AMD GPU data centers quickly and efficiently19:00 – Software ecosystems: the CUDA moat and TensorWave's ‘Beyond CUDA' summit23:00 – Market differentiation: technical and operational challenges in the Neo cloud space27:00 – Supporting enterprise fine tuning and large-scale training demands32:00 – AMD's technical advantages: VRAM, chiplet architecture, and software support36:00 – Building an open, heterogeneous AI ecosystem beyond CUDA40:00 – What success looks like: a resilient, accessible AI compute futureResources & Links:⁠TensorWave⁠⁠Beyond CUDA Summit⁠⁠Scalar LM by Greg De Almos⁠⁠AMD MI300X Data Center Chip⁠⁠Nvidia H100⁠⁠RoCM Software Stack⁠⁠LinkedIn⁠⁠Twitter⁠This conversation offers a strategic look at how focused infrastructure development, software ecosystem support, and hardware differentiation are critical in shaping the future of accessible, scalable AI compute. Whether you're building data centers, developing AI hardware, or just interested in industry shifts, this episode provides valuable insights into how companies like TensorWave are reshaping the landscape.

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

La documentation et les liens de cette émission sont sur http://cpu.pm/0234 . Cette release fait partie de la série “Composants”. Dans cette release : Un Commodore 64 en 2026, des machines caméléons, fouiner chez des antiquaires, et un cadre légal très flou. Nous recevons Fred Requin, alias FrenchShark, concepteur de FPGA. Ceci est la troisième partie du sujet. le début a été…

In episode 105, we finally get the stream dialed and dive straight into hands‑on Bitcoin mining and open-source hardware updates. We share the latest on Ember One: a sneaky IO voltage domain bug uncovered by Mujina dev Ryan led to a desk‑side hardware fix that's now pushing ~2 TH/s (target is 3.6 TH/s across 12 chips with proper cooling). We unpack chip and hashboard design lore—from stacked voltage domains and reliability in long chains to the insider politics at big silicon shops like Intel. We talk why selling chips openly matters, how spec sheets unlock real builder momentum, and why third‑party system builders (think Epic Blockchain) can grease the skids between chipmakers and end products.We cover Mujina's trajectory toward a universal, Linux‑first, open firmware for miners—auto‑detect dreams vs config realities—and near‑term support for Ember One's Intel boards and existing Antminers. We riff on home‑miner UX, remote monitoring, and agent/LLM tooling (cron‑job‑with‑superpowers, heartbeats, MCP integrations) to tune, alert, and manage miners. There's buzz around FutureBit's Apollo 3 (likely Auradine chips), open vs lawyered licenses, and the path from FPGA teaching rigs to community‑designed ASICs. We celebrate community hashing on the 256F HydroPool hash‑dash, solo‑block wins, and Heat Punk Summit prep (immersion hot tub included). Plus, a call to action: support developer freedom at change.org/billandkeonne. It's a dense, builder‑first session on chips, firmware, agents, and bringing practical hashrate‑heat products to life.

Setanta Space Systems (Setanta Space), a new Irish space technology start-up, has announced its official launch. The company is focused on developing novel modular onboard computing hardware and artificial intelligence (AI) software designed to make spacecraft more autonomous, resilient and capable. Founded by a team of engineers with backgrounds in European Space Agency (ESA) missions, launch vehicle systems and flight-ready embedded software, Setanta Space aims to address one of the most persistent limitations in modern spacecraft, the lack of high-performance, flexible computing at the edge. While satellites are generating increasing volumes of data and operating in more complex environments, much of today's avionics still relies on legacy architectures that constrain autonomy and require heavy dependence on ground operations. Setanta Space's new approach is to place intelligence directly onboard. The company is developing a family of modular and scalable computing platforms that combine radiation-tolerant electronics with deployable AI, enabling spacecraft to process sensor data, detect anomalies and make operational decisions in orbit rather than waiting for instructions from Earth. By reducing latency and bandwidth requirements, this architecture allows missions to respond faster, operate more independently and extract more value. "At Setanta Space, we believe spacecraft need to be smarter," said James Murphy, Founder and Chief Technical Officer. "Our goal is to provide the hardware and software foundation that enables true onboard autonomy, from health monitoring and anomaly detection to perception and real-time data processing. We want intelligence to be built into every mission from day one." Headquartered at NovaUCD in Dublin, Setanta Space is building its product line around a modular hardware concept that allows computing subsystems to be integrated, upgraded or reconfigured without redesigning an entire spacecraft avionics stack. This design philosophy is intended to shorten development cycles and give mission designers greater flexibility as requirements evolve. The company's roadmap includes scalable onboard computers, radiation-tolerant vision sensors and a software platform for developing and deploying AI workloads across flight hardware. Murphy added, "Over the coming year, Setanta Space plans to deliver early development kits and pilot projects with customers, expand partnerships with European and international integrators, and participate in ESA and EU innovation programmes to accelerate technology maturation. We also intend to establish a presence in the United States to support commercial growth and closer engagement with the broader aerospace ecosystem." He concluded, "Our ambition is to become a trusted provider of intelligent computing for space. Whether supporting a CubeSat, a constellation or a deep-space mission, we want our systems to give spacecraft the ability to sense, decide and act independently." In addition to James Murphy, founding team members, Adam Taylor, Jake O'Brien and Tomas Chester, bring experience spanning spacecraft electronics, embedded systems, FPGA design and applied machine learning. Team members have previously delivered flight systems for launch vehicles and deep space missions and have worked closely with ESA programmes and commercial partners across Europe. Setanta Space is also a client company of Enterprise Ireland, the Irish government's enterprise development agency. More about Irish Tech News Irish Tech News are Ireland's No. 1 Online Tech Publication and often Ireland's No.1 Tech Podcast too. You can find hundreds of fantastic previous episodes and subscribe using whatever platform you like via our Anchor.fm page here: https://anchor.fm/irish-tech-news If you'd like to be featured in an upcoming Podcast email us at Simon@IrishTechNews.ie now to discuss. Irish Tech News have a range of services available to help promote your business. Why not drop us a line at Info...

La documentation et les liens de cette émission sont sur http://cpu.pm/0233 . Cette release fait partie de la série “Composants”. Dans cette release : De l'électronique les-doigts-dans-le-nez, un FPGA dans l'espace, un analyseur logique et on compte les reprogrammations. Nous recevons Fred Requin, alias FrenchShark, concepteur de FPGA. Ceci est la deuxième partie du sujet. Le…

Every six months, we get a new version of Java. Java 26 is just around the corner and will be released soon. But most companies stick to LTS (Long-Term Support) versions, which are maintained and receive security updates for many more years. Versions 8, 11, 17, 21, and 25 are such LTS versions. Hopefully, most of your systems are already on the latest versions and you are not stuck on 8 or earlier. As a reminder, 8 was released in 2014, so much has changed since then.If you are doubting moving from 21 to 25, or even from an earlier version to the latest LTS, this podcast is for you! Together with Jakob Jenkov, we discussed the most important changes, and this episode includes a few quotes from interviews recorded at conferences last year.GuestsJakob Jenkovhttps://www.linkedin.com/in/jakob-jenkov-4a3a8/Jonathan Vilahttps://www.linkedin.com/in/jonathanvila/Ryan Svihlahttps://www.linkedin.com/in/ryan-svihla-096752182/Mary Grygleskihttps://www.linkedin.com/in/mary-grygleski/Anton Arhipovhttps://www.linkedin.com/in/antonarhipov/Ronald Dehuysserhttps://www.linkedin.com/in/ronalddehuysser/Jonathan Ellishttps://www.linkedin.com/in/jbellis/Content00:00 Introduction of topic and guestTutorials by JakobPodcast #89: Quarkus and Agentic Commerce03:30 Bugfixes and performance improvements "under the hoods"Quote Jonathan Vila08:00 Java as a scripting languageQuote Ryan SvihlaCompact Source Files and Instance Main methodsLaunch Multi-File Source-Code Programshttps://www.jbang.dev/Quote Mary Grygleski15:03 GC ImprovementsGenerational ShenandoahTrash Talk - Exploring the JVM memory management by Gerrit GrunwaldWhat Should I Know About Garbage Collection as a Java Developer?19:44 Project Loom: Virtual Threads and Structured ConcurrencyQuote Anton Arhipov29:44 How Java evolves6-months release cycleHow incubator and preview features are used to get feedback from the communityLong-Term Support Short-Term Support versionsFoojay Podcast #28: Java 21 Has Arrived!Foojay Podcast #45: Welcome to Java 22Foojay Podcast #57: Welcome to OpenJDK (Java) 23Foojay Podcast #68: Welcome to OpenJDK (Java) 24Foojay Podcast #78: Welcome to OpenJDK 25!32:15 Project Leyden: Ahead-of-time featuresAhead-of-Time Command-Line ErgonomicsAhead-of-Time Method ProfilingAhead-of-Time Class Loading & Linking39:15 Project BabylonJava on CPU, GPU, FPGA?This is already possible with TornadoVMFoojay Podcast #82: OpenJDK Projects (Leyden, Babylon, Panama) and TornadoVM43:25 Class-File APIQuote Ronald DehuysserJavaFX In Action #22 with Matt Coley, diving into byte code and JARs with Recaf and JavaFX libraries49:20 Foreign Function and Memory APIThe FFM API: How OpenJDK Changed the Game for Native Interactions (And Made Pi4J Better!)jChampions Conference talk 'Foreign Function & Memory (FFM) API on Raspberry Pi'54:26 Vector APIQuote Jonathan Ellis + Ryan Svihla59:59 Removal of String templates01:00:26 Taking a look into the JVM of the future01:03:08 Conclusion

La documentation et les liens de cette émission sont sur http://cpu.pm/0232 . Cette release fait partie de la série “Composants”. Dans cette release : Une révolution programmable, un proto à 200 MHz, un FPGA pour les simuler tous, et un réseau de neurones sur 4 bits ! Nous recevons Fred Requin, alias FrenchShark, concepteur de FPGA. Ceci est la première partie du sujet. La…

Gabe Ravacci, CTO and co-founder at Internet Backyard, breaks down what the “computer economy” really looks like when you zoom in on data centers, billing, invoicing, and the financial plumbing nobody wants to touch. He shares how a rejected YC application, a finance stint, and a handful of hard lessons pushed him from hardware curiosity to building fintech infrastructure for compute.If you care about where compute is headed, or you are early in your career and trying to find your path without overplanning it, this one will land.Key Takeaways• Startups often happen “by accident” when your competence meets the right problem at the right time• Compute accessibility is not only a chip problem, it is also a finance and operations problem• Rejection can be data, not a verdict, treat it as feedback to sharpen the craft• A real online presence is less about networking and more about being genuinely useful in public• Time blocking and single task focus beats grinding when you are juggling school, work, and a startupTimestamped Highlights00:28 What Internet Backyard is building, fintech infrastructure for data center financial operations01:37 The first startup attempt, cheaper compute via FPGA based prototyping, and why investors passed04:48 The pivot, from hardware tools to a finance informed view of compute and transparency gaps06:55 How Gabe reframed YC rejection, process over outcome, “a tree of failures” that builds skill08:29 Building a digital brand on X, what he posted, how he learned in public, and why it worked13:36 The real balancing act, dropping classes, finishing the degree well, and strict time blocking20:00 Books that shaped his thinking, Siddhartha, The Art of Learning, Finite and Infinite GamesA line worth keeping“The process is really more important than any outcome.”Pro Tips for builders• Treat learning like a skill, ask better questions before you chase better answers• Make focus a system, set blocks, mute distractions, and do one thing at a time• Share what you are learning in public, not to perform, but to be useful and find signalCall to ActionIf this episode sparked an idea, follow or subscribe so you do not miss the next one. Also check out Amir's newsletter for more conversations at the intersection of people, impact, and technology.

Chances are, you either grew up with a Commodore 64 or you knew someone who did. From Space Taxi to Ultima, it was the other side of 80s gaming across North America and Europe. Now the C64 is back. Last year, a YouTuber and hardcore retro computer superfan bought the Commodore brand and, building on a popular FPGA project, relaunched the C64 for a modern audience of longtime fans and curious newcomers alike. Sinistar picked one up, and he is here to walk you through exactly why he loves it. Press B To Cancel also on YouTube! For updates and more episodes please visit our website www.pressbtocancel.com, or find us on Twitter @pressbtocancel Want to support the show? Donate via our Patreon and gain additional Discord perks and behind the scenes clips. Press B is a member of the SuperPod Network; a gaming collective of fellow podcasters and shows. Special thanks to The Last Ancient on SoundCloud for our podcast theme. Find out more at http://pressbtocancel.comRead transcript

Quantum computing is no longer confined to research labs—it's entering the commercial space, and electrical engineers are uniquely positioned to contribute. In this episode of the OnTrack Podcast, host Zach Peterson sits down with quantum hardware designer Šimon Marek to explore the fascinating world of superconducting quantum chips. From transmon qubits and Josephson junctions to control electronics and FPGA-based systems, Šimon breaks down the engineering principles that make quantum computers work, revealing how familiar microwave and RF design concepts translate directly into this cutting-edge field. Whether you're a PCB designer curious about quantum technology or an engineer looking for your next challenge, this conversation offers a practical roadmap for understanding quantum hardware. Šimon shares his journey from Arduino projects to quantum chip design, walks through actual chip layouts and simulation workflows, and discusses the fabrication processes that bring these devices to life. Discover why quantum computing might be more accessible to traditional electronics engineers than you think.

In this episode of the Crazy Wisdom podcast, host Stewart Alsop sits down with Peter Schmidt Nielsen, who is building FPGA-accelerated servers at Saturn Data. The conversation explores why servers need FPGAs, how these field-programmable gate arrays work as "IO expanders" for massive memory bandwidth, and why they're particularly well-suited for vector database and search applications. Peter breaks down the technical realities of FPGAs - including why they "really suck" in many ways compared to GPUs and CPUs - while explaining how his company is leveraging them to provide terabyte-per-second bandwidth to 1.3 petabytes of flash storage. The discussion ranges from distributed systems challenges and the CAP theorem to the hardware-software relationship in modern computing, offering insights into both the philosophical aspects of search technology and the nuts-and-bolts engineering of memory controllers and routing fabrics.For more information about Peter's work, you can reach him on Twitter at @PTRSCHMDTNLSN or find his website at saturndata.com.Timestamps00:00 Introduction to FPGAs and Their Role in Servers02:47 Understanding FPGA Limitations and Use Cases05:55 Exploring Different Types of Servers08:47 The Importance of Memory and Bandwidth11:52 Philosophical Insights on Search and Access Patterns14:50 The Relationship Between Hardware and Search Queries17:45 Challenges of Distributed Systems20:47 The CAP Theorem and Its Implications23:52 The Evolution of Technology and Knowledge Management26:59 FPGAs as IO Expanders29:35 The Trade-offs of FPGAs vs. ASICs and GPUs32:55 The Future of AI Applications with FPGAs35:51 Exciting Developments in Hardware and BusinessKey Insights1. FPGAs are fundamentally "crappy ASICs" with serious limitations - Despite being programmable hardware, FPGAs perform far worse than general-purpose alternatives in most cases. A $100,000 high-end FPGA might only match the memory bandwidth of a $600 gaming GPU. They're only valuable for specific niches like ultra-low latency applications or scenarios requiring massive parallel I/O operations, making them unsuitable for most computational workloads where CPUs and GPUs excel.2. The real value of FPGAs lies in I/O expansion, not computation - Rather than using FPGAs for their processing power, Saturn Data leverages them primarily as cost-effective ways to access massive amounts of DRAM controllers and NVMe interfaces. Their server design puts 200 FPGAs in a 2U enclosure with 1.3 petabytes of flash storage and terabyte-per-second read bandwidth, essentially using FPGAs as sophisticated I/O expanders.3. Access patterns determine hardware performance more than raw specs - The way applications access data fundamentally determines whether specialized hardware will provide benefits. Applications that do sparse reads across massive datasets (like vector databases) benefit from Saturn Data's architecture, while those requiring dense computation or frequent inter-node communication are better served by traditional hardware. Understanding these patterns is crucial for matching workloads to appropriate hardware.4. Distributed systems complexity stems from failure tolerance requirements - The difficulty of distributed systems isn't inherent but depends on what failures you need to tolerate. Simple approaches that restart on any failure are easy but unreliable, while Byzantine fault tolerance (like Bitcoin) is extremely complex. Most practical systems, including banks, find middle ground by accepting occasional unavailability rather than trying to achieve perfect consistency, availability, and partition tolerance simultaneously.5. Hardware specialization follows predictable cycles of generalization and re-specialization - Computing hardware consistently follows "Makimoto's Wave" - specialized hardware becomes more general over time, then gets leapfrogged by new specialized solutions. CPUs became general-purpose, GPUs evolved from fixed graphics pipelines to programmable compute, and now companies like Etched are creating transformer-specific ASICs. This cycle repeats as each generation adds programmability until someone strips it away for performance gains.6. Memory bottlenecks are reshaping the hardware landscape - The AI boom has created severe memory shortages, doubling costs for DRAM components overnight. This affects not just GPU availability but creates opportunities for alternative architectures. When everyone faces higher memory costs, the relative premium for specialized solutions like FPGA-based systems becomes more attractive, potentially shifting the competitive landscape for memory-intensive applications.7. Search applications represent ideal FPGA use cases due to their sparse access patterns - Vector databases and search workloads are particularly well-suited to FPGA acceleration because they involve searching through massive datasets with sparse access patterns rather than dense computation. These applications can effectively utilize the high bandwidth to flash storage and parallel I/O capabilities that FPGAs provide, making them natural early adopters for this type of specialized hardware architecture.

We're back to start the new year with the second and final installment of our ranking of startup sounds. To close out the tier list we consider later consoles like the Xbox 360 and PlayStation 3, more recent Windowses that we didn't even realize had startup sounds, most of the handhelds from Nintendo and Sony, and even some offbeat entries like Analogue's FPGA consoles and older operating systems like BeOS and OS/2. It's an aural extravaganza!The final tier list: https://tiny.cc/tp320-sounds Support the Pod! Contribute to the Tech Pod Patreon and get access to our booming Discord, a monthly bonus episode, your name in the credits, and other great benefits! You can support the show at: https://patreon.com/techpod

In this episode of the Crazy Wisdom podcast, host Stewart Alsop interviews Marcin Dymczyk, CPO and co-founder of SevenSense Robotics, exploring the fascinating world of advanced robotics and AI. Their conversation covers the evolution from traditional "standard" robotics with predetermined pathways to advanced robotics that incorporates perception, reasoning, and adaptability - essentially the AGI of physical robotics. Dymczyk explains how his company builds "the eyes and brains of mobile robots" using camera-based autonomy algorithms, drawing parallels between robot sensing systems and human vision, inner ear balance, and proprioception. The discussion ranges from the technical challenges of sensor fusion and world models to broader topics including robotics regulation across different countries, the role of federalism in innovation, and how recent geopolitical changes are driving localized high-tech development, particularly in defense applications. They also touch on the democratization of robotics for small businesses and the philosophical implications of increasingly sophisticated AI systems operating in physical environments. To learn more about SevenSense, visit www.sevensense.ai.Check out this GPT we trained on the conversationTimestamps00:00 Introduction to Robotics and Personal Journey05:27 The Evolution of Robotics: From Standard to Advanced09:56 The Future of Robotics: AI and Automation12:09 The Role of Edge Computing in Robotics17:40 FPGA and AI: The Future of Robotics Processing21:54 Sensing the World: How Robots Perceive Their Environment29:01 Learning from the Physical World: Insights from Robotics33:21 The Intersection of Robotics and Manufacturing35:01 Journey into Robotics: Education and Passion36:41 Practical Robotics Projects for Beginners39:06 Understanding Particle Filters in Robotics40:37 World Models: The Future of AI and Robotics41:51 The Black Box Dilemma in AI and Robotics44:27 Safety and Interpretability in Autonomous Systems49:16 Regulatory Challenges in Robotics and AI51:19 Global Perspectives on Robotics Regulation54:43 The Future of Robotics in Emerging Markets57:38 The Role of Engineers in Modern WarfareKey Insights1. Advanced robotics transcends traditional programming through perception and intelligence. Dymczyk distinguishes between standard robotics that follows rigid, predefined pathways and advanced robotics that incorporates perception and reasoning. This evolution enables robots to make autonomous decisions about navigation and task execution, similar to how humans adapt to unexpected situations rather than following predetermined scripts.2. Camera-based sensing systems mirror human biological navigation. SevenSense Robotics builds "eyes and brains" for mobile robots using multiple cameras (up to eight), IMUs (accelerometers/gyroscopes), and wheel encoders that parallel human vision, inner ear balance, and proprioception. This redundant sensing approach allows robots to navigate even when one system fails, such as operating in dark environments where visual sensors are compromised.3. Edge computing dominates industrial robotics due to connectivity and security constraints. Many industrial applications operate in environments with poor connectivity (like underground grocery stores) or require on-premise solutions for confidentiality. This necessitates powerful local processing capabilities rather than cloud-dependent AI, particularly in automotive factories where data security about new models is paramount.4. Safety regulations create mandatory "kill switches" that bypass AI decision-making. European and US regulatory bodies require deterministic safety systems that can instantly stop robots regardless of AI reasoning. These systems operate like human reflexes, providing immediate responses to obstacles while the main AI brain handles complex navigation and planning tasks.5. Modern robotics development benefits from increasingly affordable optical sensors. The democratization of 3D cameras, laser range finders, and miniature range measurement chips (costing just a few dollars from distributors like DigiKey) enables rapid prototyping and innovation that was previously limited to well-funded research institutions.6. Geopolitical shifts are driving localized high-tech development, particularly in defense applications. The changing role of US global leadership and lessons from Ukraine's drone warfare are motivating countries like Poland to develop indigenous robotics capabilities. Small engineering teams can now create battlefield-effective technology using consumer drones equipped with advanced sensors.7. The future of robotics lies in natural language programming for non-experts. Dymczyk envisions a transformation where small business owners can instruct robots using conversational language rather than complex programming, similar to how AI coding assistants now enable non-programmers to build applications through natural language prompts.

I know we said we were waiting till 2026 to record more episodes, but we couldn't resist getting on Clyde Shaffer to talk about his brand new 8-bit game console, ‘the GameTank'. This isn't FPGA or emulation - it's new hardware with brand new games celebrating all things retro in 2025, and you guys flocked to our website in droves to check it out. We sat down with Clyde to get all of the information on the GameTank that we possibly could, from how the idea started to the design process and game development. If you're into your retro gaming (which you all should be if you've read this far), then you'll absolutely love this episode.So sit back, grab a hot chocolate, and enjoy a sneaky episode before we return in 2026!

This week we talk about Bolt graphics, a new graphics start up that is working on a graphics card with upgrade-able memory for a competitive price. A software developer has released an open source alternative firmware for the Nest v1 and v2 thermostats, and of course your questions! -- During The Show -- 00:45 Intro Dakota's weather 01:51 Email! - William Listener recommends porkbun (https://porkbun.com/) Mailbox.org (https://mailbox.org/en/) Simple Login (https://simplelogin.io/) DuckDuckGo Email Alias (https://duckduckgo.com/duckduckgo-help-pages/email-protection/duck-addresses) Proton's built in features Reasons for protecting privacy Privacy.com (https://www.privacy.com/) 11:25 Data Science & Self Hosting - Annon Value based approach Consenting data collection Tool vs Pillar A job can be a tool Get a job in a different field hadoop Nextcloud Anti Virus Network Protection Medical Science Red Hat data sciences 22:15 News Wire LXQT 2.3 - lxqt-project.org (https://lxqt-project.org/release/2025/11/05/release-lxqt-2-3-0) Calibre 8.14 - newwin.net (https://www.neowin.net/software/calibre-8140) MKVtoolnix - mkvtoolnix.download (https://mkvtoolnix.download/windows/releases/96.0) Curly COMrades - darkreading.com (https://www.darkreading.com/endpoint-security/pro-russian-hackers-linux-vms-hide-windows) Porteux 2.4 - distrowatch.com (https://distrowatch.com/?newsid=12628) MXLinux 25 - mxlinux.org (https://mxlinux.org/blog/mx-25-infinity-isos-now-available) Devuan 6.0 - serverhost.com (https://serverhost.com/blog/devuan-gnu-linux-6-0-launches-a-systemd-free-distro-based-on-debian-13-trixie) IncusOS - phoronix.com (https://www.phoronix.com/news/Incus-IncusOS-Announced) NVIDIA AI Stack - hpcwire.com (https://www.hpcwire.com/off-the-wire/ciq-integrates-full-nvidia-ai-stack-into-rocky-linux-for-faster-deployment-and-scaling) Omnilingual ASR - venturebeat.com (https://venturebeat.com/ai/meta-returns-to-open-source-ai-with-omnilingual-asr-models-that-can) Kimi K2 Thinking - venturebeat.com (https://venturebeat.com/ai/moonshots-kimi-k2-thinking-emerges-as-leading-open-source-ai-outperforming) Drax - prnewswire.com (https://www.prnewswire.com/news-releases/aiola-unveils-drax-an-open-source-speech-model-with-state-of-the-art-accuracy-and-up-to-5O-faster-than-models-from-direct-competitors-302607278.html) Linux Desktop 5% - webpronews.com (https://www.webpronews.com/linux-breaks-5-desktop-share-in-u-s-signaling-open-source-surge-against-windows-and-macos) 23:50 Jill Mueller - Bolt Graphics Bolt Graphics Key differences Build of the card Why did you come to Ubuntu Summit? 27:25 Antonio Salvemini - Ray Tracing Bolt Graphics Ray Tracing vs Raster Why start with FPGA? Next steps Current Stage Available 2027 Bolt Graphics (https://bolt.graphics/) Untapped markets Upgradeable GPU 34:34 No Longer Evil Thermostat Google EOLs Nest Thermostats Gen 1 and Gen 2 No Longer Evil (https://nolongerevil.com/) FULU Foundation (https://fulu.org/our-story) "Feature Complete" AXIS A1001 Good piece of hardware Reservations Connects to "No Longer Evil Server" Server planned to be open sourced Centralite Perl HA Thermostat (Zigbee) (https://www.amazon.com/Centralite-Thermostat-Xfinity-Comcast-Centrallite/dp/B01LXD3EBN) Needs to be repaired 1 or 2 times a year Temperature Sensors Govee H5075 (https://us.govee.com/products/govee-bluetooth-hygrometer-thermometer-h5075) IoT Maintenance Why temperature sensors ESP32 receive blue-tooth and send to Home Assistant -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/466) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed) Special Guests: Antonio Salvemini and Jill Mueller.

Signals have to get into the FPGA and out of the FPGA. Here we need input/output pins. Here we will have a closer look. Content of this Episode: * I/O pad * Logic block * I/O standards * Single-Ended Standards * Differential Standards * Key Considerations for I/O Standards And for now come into our Newsletter and also follow us on LinkedIn. The post WFP033 – FPGA I/Os appeared first on World of FPGA by David Kirchner.

This is a recap of the top 10 posts on Hacker News on October 04, 2025. This podcast was generated by wondercraft.ai (00:30): The UK is still trying to backdoor encryption for Apple usersOriginal post: https://news.ycombinator.com/item?id=45476273&utm_source=wondercraft_ai(01:52): Flock's gunshot detection microphones will start listening for human voicesOriginal post: https://news.ycombinator.com/item?id=45473698&utm_source=wondercraft_ai(03:14): How I influence tech company politics as a staff software engineerOriginal post: https://news.ycombinator.com/item?id=45473852&utm_source=wondercraft_ai(04:37): Alibaba cloud FPGA: the $200 Kintex UltraScale+Original post: https://news.ycombinator.com/item?id=45471136&utm_source=wondercraft_ai(05:59): Paged Out Issue #7 [pdf]Original post: https://news.ycombinator.com/item?id=45472319&utm_source=wondercraft_ai(07:21): ProofOfThought: LLM-based reasoning using Z3 theorem provingOriginal post: https://news.ycombinator.com/item?id=45475529&utm_source=wondercraft_ai(08:44): Circular Financing: Does Nvidia's $110B Bet Echo the Telecom Bubble?Original post: https://news.ycombinator.com/item?id=45473033&utm_source=wondercraft_ai(10:06): A comparison of Ada and Rust, using solutions to the Advent of CodeOriginal post: https://news.ycombinator.com/item?id=45473861&utm_source=wondercraft_ai(11:29): Self-hosting email like it's 1984Original post: https://news.ycombinator.com/item?id=45473730&utm_source=wondercraft_ai(12:51): New antibiotic targets IBD and AI predicted how it would workOriginal post: https://news.ycombinator.com/item?id=45469579&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

We have an internal digital highway inside an FPGA to connect all the different blocks. This highway has a lot of interesting features. Content of this Episode: * Routing Resources * Connection lines * Connection boxes * Switching boxes * But it depends * Routing process * Routing Algorithms * Routing key challenges And for now come into our Newsletter and also follow us on LinkedIn. The post WFP032 – FPGA Routing appeared first on World of FPGA by David Kirchner.

Memory is essential for a lot of things in your FPGA design. And FPGAs have a lot of different memory. Content of this Episode: * Flip-Flops * SRAM blocks * Ultra RAM * Flash Memory * High Bandwidth Memory * Memory-Controller * External Memory And for now come into our Newsletter and also follow us on LinkedIn. The post WFP031 – FPGA Memory appeared first on World of FPGA by David Kirchner.

Blockchains operate as a public ledger, ‘disclosing' the entire transaction history and associated data to everyone. While verifiability and traceability are key traits, as blockchains gain global adoption, those very features hinder the process. Self custody, on-chain identities, corporate strategies, transaction history, private deals, all represent highly sensitive information that call for provable confidentiality. Fully homomorphic encryption has long been considered the ‘holy grail' of cryptography as it enables computation to be performed on encrypted data without the need of prior decryption. This basically translates to true end-to-end encryption, both on-chain and off-chain. As cryptographic research advances, so does the scalability and applicability of FHE. As a result of more than 5 years of work, Zama has now released Zama Protocol, which enables confidential smart contracts on top of any L1 or L2 using FHE, without any additional execution burden. By encrypting all ciphertexts with the same public key, FHE ensures composability and seamless integration across different blockchains and applications, making it a true cross-chain confidentiality layer. Through parallel execution, Zama Protocol already surpasses Ethereum's throughput, yet future roadmap includes open-source development of FPGA & ASIC in order to scale it even further, to accommodate faster, non-EVM chains.Topics covered in this episode:Zama's progress in FHEZama's confidential blockchain ProtocolSecurity guarantees of MPC coprocessorsMaintaining a healthy operator setSlashing and governanceZama's throughputOpen-sourcing FPGA & ASIC developmentThe Zama token & its implicationsZama's public testnetPrivate votingZama fundingRegulationsExpanding use cases beyond blockchainsFuture goals and expectationsEpisode links:Rand Hindi on XZama on XSponsors:Gnosis: Gnosis builds decentralized infrastructure for the Ethereum ecosystem, since 2015. This year marks the launch of Gnosis Pay— the world's first Decentralized Payment Network. Get started today at - gnosis.ioChorus One: one of the largest node operators worldwide, trusted by 175,000+ accounts across more than 60 networks, Chorus One combines institutional-grade security with the highest yields at - chorus.oneThis episode is hosted by Friederike Ernst.

Podcast: IoT For All Podcast (LS 40 · TOP 2% what is this?)Episode: Bringing LPWAN to Industrial IoT | Miromico's Liliane Paradise & Alex Raimondi | Internet of Things PodcastPub date: 2025-08-20Get Podcast Transcript →powered by Listen411 - fast audio-to-text and summarizationIn this episode of the IoT For All Podcast, Liliane Paradise and Alex Raimondi, COO and CTO of Miromico respectively, join Ryan Chacon to discuss bringing LPWAN to industrial IoT. The conversation covers the shift towards wireless solutions in the industrial sector, the advantages of LPWAN, sustainable IoT solutions, energy harvesting, battery-free IoT devices, the challenges and strategies in building successful industrial IoT solutions, and the critical role of a strong partner ecosystem.Liliane Paradise is a dynamic tech leader and IoT innovator currently serving as Chief Operating Officer of Miromico. She holds a Master's in Mechanical Engineering from ETH Zurich and began her journey at Miromico as a hardware developer around four years ago. At Miromico, Liliane has driven several major breakthroughs—most notably the launch of the miro EdgeCard mioty®, a compact LPWAN gateway accessory enabling scalable, energy‑efficient deployments. She oversees global operations, focusing on bringing innovative IoT devices—such as rugged gateways and battery‑free sensors—to mass production while championing sustainability and Swiss engineering excellence.Alex Raimondi is an IoT and embedded systems expert with a Master's in Electrical Engineering and Information Technology from ETH Zurich. Since 2004, he has led the embedded design team at Miromico, developing everything from high-performance FPGA systems to ultra-low-power sensor devices. He is also a co-founder of the high-tech startup Chip-ing, which is pioneering next generation "Golf 3.0" products. A frequent speaker at IoT industry events like IoT Visions—where he has presented on topics such as scalable and sustainable LoRaWAN logistics—Alex combines deep technical leadership with entrepreneurial drive.Miromico AG is a Zurich-based high-tech company specializing in innovative IoT and wireless solutions. Founded in 2002 as a spin-off from ETH Zurich, Miromico develops and manufactures advanced devices such as sensors, gateways, and embedded systems for smart cities, industrial automation, logistics, and more. Known for its expertise in LPWAN technologies like LoRaWAN and mioty®, the company provides end-to-end services from design to mass production, combining Swiss engineering quality with a global impact.Discover more about IoT and LPWAN at https://www.iotforall.comFind IoT solutions: https://marketplace.iotforall.comMore about Miromico: https://miromico.ch/en/homeConnect with Liliane: https://www.linkedin.com/in/liliane-paradise-5ab212137/Connect with Alex: https://www.linkedin.com/in/alexraimondi/Our sponsor: https://www.hologram.io(00:00) Ad(00:29) Intro(00:41) Liliane Paradise, Alex Raimondi, and Miromico(02:14) The shift to wireless IoT solutions(04:44) What is LPWAN?(05:57) Why makes mioty stand out?(07:00) Building an industrial LPWAN solution with mioty(10:18) Sustainable IoT and battery-free devices(13:02) Challenges of designing for ultra low power(14:42) Getting to market faster(16:09) Balancing hardware and customer demands(19:48) Moving from proof-of-concept to deployment(20:57) Navigating competing demands in battery life(23:40) Regulations and certifications(25:00) Differentiation in IoT hardware(27:43) Learn more and follow upSubscribe on YouTube: https://bit.ly/2NlcEwmJoin Our Newsletter: https://newsletter.iotforall.comFollow Us on Social: https://linktr.ee/iot4allThe podcast and artwork embedded on this page are from IoT For All, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.

In this episode of the IoT For All Podcast, Liliane Paradise and Alex Raimondi, COO and CTO of Miromico respectively, join Ryan Chacon to discuss bringing LPWAN to industrial IoT. The conversation covers the shift towards wireless solutions in the industrial sector, the advantages of LPWAN, sustainable IoT solutions, energy harvesting, battery-free IoT devices, the challenges and strategies in building successful industrial IoT solutions, and the critical role of a strong partner ecosystem.Liliane Paradise is a dynamic tech leader and IoT innovator currently serving as Chief Operating Officer of Miromico. She holds a Master's in Mechanical Engineering from ETH Zurich and began her journey at Miromico as a hardware developer around four years ago. At Miromico, Liliane has driven several major breakthroughs—most notably the launch of the miro EdgeCard mioty®, a compact LPWAN gateway accessory enabling scalable, energy‑efficient deployments. She oversees global operations, focusing on bringing innovative IoT devices—such as rugged gateways and battery‑free sensors—to mass production while championing sustainability and Swiss engineering excellence.Alex Raimondi is an IoT and embedded systems expert with a Master's in Electrical Engineering and Information Technology from ETH Zurich. Since 2004, he has led the embedded design team at Miromico, developing everything from high-performance FPGA systems to ultra-low-power sensor devices. He is also a co-founder of the high-tech startup Chip-ing, which is pioneering next generation "Golf 3.0" products. A frequent speaker at IoT industry events like IoT Visions—where he has presented on topics such as scalable and sustainable LoRaWAN logistics—Alex combines deep technical leadership with entrepreneurial drive.Miromico AG is a Zurich-based high-tech company specializing in innovative IoT and wireless solutions. Founded in 2002 as a spin-off from ETH Zurich, Miromico develops and manufactures advanced devices such as sensors, gateways, and embedded systems for smart cities, industrial automation, logistics, and more. Known for its expertise in LPWAN technologies like LoRaWAN and mioty®, the company provides end-to-end services from design to mass production, combining Swiss engineering quality with a global impact.Discover more about IoT and LPWAN at https://www.iotforall.comFind IoT solutions: https://marketplace.iotforall.comMore about Miromico: https://miromico.ch/en/homeConnect with Liliane: https://www.linkedin.com/in/liliane-paradise-5ab212137/Connect with Alex: https://www.linkedin.com/in/alexraimondi/Our sponsor: https://www.hologram.io(00:00) Ad(00:29) Intro(00:41) Liliane Paradise, Alex Raimondi, and Miromico(02:14) The shift to wireless IoT solutions(04:44) What is LPWAN?(05:57) Why makes mioty stand out?(07:00) Building an industrial LPWAN solution with mioty(10:18) Sustainable IoT and battery-free devices(13:02) Challenges of designing for ultra low power(14:42) Getting to market faster(16:09) Balancing hardware and customer demands(19:48) Moving from proof-of-concept to deployment(20:57) Navigating competing demands in battery life(23:40) Regulations and certifications(25:00) Differentiation in IoT hardware(27:43) Learn more and follow upSubscribe on YouTube: https://bit.ly/2NlcEwmJoin Our Newsletter: https://newsletter.iotforall.comFollow Us on Social: https://linktr.ee/iot4all

Dan is joined by Mamta Gupta, She leads the Security Product Marketing, Datacenter and the Communications Segment Marketing Teams at Lattice. She brings with her over 20 years of FPGA experience in product development with special focus on security, aerospace and defense segments. Dan explores the growing area of cybersecurity… Read More

In this episode, Dave dives into the newly announced Commodore 64 Ultimate - a modern, FPGA-powered revival of the classic C64 - and compares it to his previously acquired Ultimate 64 Elite II board. He breaks down the different editions, pricing tiers, and what makes this official reboot stand out in a crowded retro hardware scene. John talks about modding his original Atari 2600 with a composite video output and the guys also check out the impressive MovieCart, a full-motion video cartridge for the Atari 2600, revisit the just-announced THEC64 Mini Black Edition, and discuss the surprise return of Compute!'s Gazette. Plus: John explains why he returned his preorder for the My Arcade Atari Watch.

It was time for a little trip again. I went to Munich to the three-day FPGA conference of PLC2 and the Vogel Verlag. * FPGA Conference the biggest event in Europe * Some facts * 3 days * 430 Participants * 128 Lectures * 110 Speakers * 39 Exhibitors * This year triple anniversary * 40 years FPGA * 30 years PLC2 * 10 years FPGA Conference * All my visited talks * Welcome to the Post-European Cyber Resilience Act (CRA) Era * FPGAs and the Cyber Resilience Act * Cyber Resilience Act: Planning your Security Future * Making Simple FPGA Testbenches – Utilising Important Quality Measures * A Cuckoo Hash-Based CAM Architecture for FPGA and ASIC Implementations * Elevate your Design: Security and Power Efficiency with AMD Spartan UltraScale+ FPGAs * Faster Change of Probe Signals using the Vivado Logic Analyzer * Warning! Your FPGAs & SoC FPGAs are Under Attack * Functional Safety for Hardware and Software * Security, Regulations and FPGA-Based Systems – How to Make Your System Secure * Verify the Bits that Fly : A Demonstration of Bitstream to HDL Equivalence Checking * Why VUnit? * Managing and Versioning Gateware Source Code on Git with Hog * A Baseboard Management Controller for FPGA/SoC Board Supervision and Faster Bringup * GateMate FPGA: Qualification for Radiation-Tolerant Applications * GateMate FPGA: High-Speed Transceiver (SerDes) Hands-On * Project-Based and Non-Project-Based Scripting in Vivado * Multi-Run Management Using Vivado * How to Drive Parallel High-Speed Circuits from an AMD FPGA Next FPGA conference is from 30 June - 2 July 2026 And for now come into our Newsletter and also follow us on LinkedIn. The post WFP030 – FPGA Conference 2025 appeared first on World of FPGA by David Kirchner.

An airhacks.fm conversation with Michalis Papadimitriou (@mikepapadim) about: starting with Java 8, first computer experiences with Pentium 2, doom 2 and Microsoft Paint, university introduction to Object-oriented programming using Objects First and bluej IDE, Monte Carlo simulations for financial portfolio optimization in Java, porting Java applications to OpenCL for GPU acceleration achieving 20x speedup, working at Huawei on GPU hardware, writing unit tests as introduction to TornadoVM, working on FPGA integration and Graal compiler optimizations, experience at OctoAI startup doing AI compiler optimizations for TensorFlow and PyTorch models, understanding model formats evolution from ONNX to GGUF, standardization of LLM inference through Llama models, implementing GPU-accelerated Llama 3 inference in pure Java using TornadoVM, achieving 3-6x speedup over CPU implementations, supporting multiple models including Mistral and working on qwen 3 and deepseek, differences between models mainly in normalization layers, GGUF becoming quasi-standard for LLM model distribution, TornadoVM's Consume and Persist API for optimizing GPU data transfers, challenges with OpenCL deprecation on macOS and plans for Metal backend, importance of developer experience and avoiding python dependencies for Java projects, runtime and compiler optimizations for GPU inference, kernel fusion techniques, upcoming integration with langchain4j, potential of Java ecosystem with Graal VM and Project Panama FFM for high-performance inference, advantages of Java's multi-threading capabilities for inference workloads Michalis Papadimitriou on twitter: @mikepapadim

A teardown of the Uni-T UTE 310 Digital Power Meter, and an example meausing the power consumption of the new Brymen BM786BT multimeter in bluetooth data transmission mode. https://uni-trendus.com/products/ute310-digital-power-meter Forum: https://www.eevblog.com/forum/blog/eevblog-1693-uni-t-ute310-power-meter-teardown-practical-demo/ 00:00 – Uni-T UTE310 Power Meter 02:44 – Teardown 06:54 – Power supply 07:47 – FPGA and ARM processors (plural) 09:23- Seperate isolated volatge …

In this episode, Dave finally unboxes the long-awaited Ultimate 64 Elite II - an FPGA-based modern C64 replacement - and shares why it might be the last 64 he ever needs. John dives into his surprising change of heart on the Nintendo Switch 2, covering game upgrades, new features, and how it compares to the Steam Deck. Plus: a custom Synthcart controller project and a quick review of the wireless Atari CX-40 joystick.

As time goes on the games and the consoles we grew up with have a hard time keeping up with modern technology. Plug in your NES or Sega Genesis into a modern HD TV and it just doesn't feel the way you remember it. You may ask, did my games always look and play like this? The answer no. Well sort of... Returning to the show today is my good friend Try from the YouTube channel My Life in Gaming, and we do a pretty thorough overview of what to do to play your retro game systems and retro games on modern televisions. We talk about video signals, resolutions, upscaling, emulation of all kinds and much more. If you ever wanted to learn about how to get the most out of your old game consoles, use this episode as a jumping off point! Checkout My Life in Gaming on YouTube! https://www.youtube.com/@mylifeingaming Check out The Backloggery! https://backloggery.com/ Shout-out Song: Dedede's Theme (from Kirby's Dream Land) Artist: Karl Brueggemann Album: Micropower https://karlbmusic.bandcamp.com/album/micropower End Song: BITGEN07 [Super Mario Land] Artist: Karl Brueggemann Album: Micropower https://karlbmusic.bandcamp.com/album/micropower Get Still Loading Podcast merch! https://www.teepublic.com/user/still-loading-podcast Check out the Bit by Bit Foundation! https://www.bitbybitfoundation.org/ Support the Podcast! https://www.patreon.com/stillloadingpod

In this week's episode, Trump delays the TikTok ban for the third time—because procrastination is the new policy—and Twitter's old sign finds new purpose as desert firewood. Tesla continues its streak of “hold my beer” engineering by blowing past a school bus in FSD tests, then mysteriously dumps Cybertrucks in Jersey parking lots while prepping a July 4th factory nap. Meanwhile, Elon's xAI is incinerating a billion bucks a month and allegedly poisoning Memphis, OpenAI and Microsoft are beefing over who's the bigger megalomaniac, and Sam Altman thinks your power bill should fund his robot overlords.In other signs of the apocalypse: Amazon is gleefully replacing workers with AI, Microsoft finally admits it might've wasted billions chasing Skynet, and Wikipedia's editors say no thanks to dumbed-down AI summaries. Studies warn ChatGPT may be turning your brain into smooth pudding, while swearing data reveals the internet prefers the F-word with regional flair. A broke crypto TikToker gets released because he's too poor to ransom, and bankruptcies spike across the Bay as tech jobs vanish like investor confidence.Media Candy brings a buffet from Inside Out to Murderbot to Stick, and Liam Neeson somehow makes the Naked Gun reboot look awesome; Apple tunes CarPlay to fit your weird dashboard, Trump sells a gold Android that's tackier than his ties, and Dave goes full retro with Open EMU 2 and FPGA gaming; plus: Dr. Demento retires, Disneyland hits your screen, and we swear this isn't all a fever dream.Sponsors:DeleteMe - Head over to JoinDeleteMe.com/GOG and use the code "GOG" for 20% off.Private Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordShow notes at https://gog.show/702FOLLOW UPDonald Trump will delay a looming TikTok ban for a third timeThe 560-pound Twitter sign met a fiery end in a Nevada desertIN THE NEWSTesla blows past stopped school bus and hits kid-sized dummies in Full Self-Driving testsFerris Bueller's Day Off: Nine TimesWhat are hundreds of Teslas doing in a New Jersey mall parking lot?Residents Baffled as Tesla Dumps Dozens of Cybertrucks in Shopping CenterTesla plans to shut down Model Y and Cybertruck production over the week of July 423andMe founder Anne Wojcicki will regain control of embattled DNA company after allOpenAI and Microsoft Tensions Are Reaching a Boiling PointAmazon says it will reduce its workforce as AI replaces human employeesMusk's xAI Burns Through $1 Billion a Month as Costs Pile UpMicrosoft CEO Satya Nadella shocks industry by admitting AI has yet to deliver real value despite massive investmentWikipedia cancels plan to test AI summaries after editors skewer the ideaYour Brain on ChatGPT: Accumulation of Cognitive Debt when Using an AI Assistant for Essay Writing TaskSam Altman Says "Significant Fraction" of Earth's Total Electricity Should Go to Running AIxAI faces legal threat over alleged Colossus data center pollution in MemphisKidnappers free TikTok crypto influencer after realizing he has no moneyPersonal bankruptcy surges in the Bay as tech employment sags - The San Francisco Standard201 ways to say ‘f**k': what 1.7 billion words of online text shows about how the world swearsVulgarity in online discourse around the English-speaking worldMEDIA CANDYBraveInside OutFamilies Like OursStickMurderbotFUBARSinnersRear WindowThe SnakeThe Naked Gun - Official Trailer (2025) Liam Neeson, Pamela AndersonThe Sandman: Season 2 | Official Trailer | NetflixDavid Zaslav Is Getting a Pay CutHow adversarial attacks in audio files give musicians new power against AI theft – Here's what you need to knowMusic Music tech Tech WebBenn Jordan's AI poison pill and the weird world of adversarial noiseAPPS & DOODADSiOS 26 will fit CarPlay to better match the shape of your car's screenMahjong Titan+Trump's New Cash Grab Is a Gold iPhone Lookalike That's Worse Than Any Budget AndroidThe golden Trump Phone is almost certainly not made in the USAT THE LIBRARYHappy: Why More or Less Everything is Absolutely Fine by Derren BrownAI Snake Oil: What Artificial Intelligence Can Do, What It Can't, and How to Tell the Difference by Sayash Kapoor, Arvind NarayananDiaries 1969–1979: The Python Years (Michael Palin Diaries Book 1)THE DARK SIDE WITH DAVEDave BittnerThe CyberWireHacking HumansCaveatControl LoopOnly Malware in the BuildingOpen EMU 2Analogue Pocket OpenFPGA GuideAll Major Gen-AI Models Vulnerable to ‘Policy Puppetry' Prompt Injection AttackVisit Disneyland From the Comfort of Disney+ With More POV WalkthroughsDr. Demento Announces Retirement After 55 YearsStar Wars metal.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

How can FPGAs calculate so fast? The secret inside an FPGA is a digital signal processing block. Content of this Episode: * What does DSP stand for? * Common parts inside an DSP block * Function representation * Important facts And for now come into our Newsletter and also follow us on LinkedIn. The post WFP029 – FPGA DSP appeared first on World of FPGA by David Kirchner.

Send us a textIn this episode of Embedded Insiders, Ken O'Neil, Space Systems Architect at AMD, joins us to explore the company's advancements in AI for space. He delves into how AMD is enabling on-board processing for satellites and spacecraft, including the adoption of FPGAs in spaceflight applications.But first, Embedded Computing Design's Editor-in-Chief, Ken Briodagh, shares highlights from Computex 2025, providing insights into the top technological innovations unveiled at the event, including advancements in AI and edge computing.For more information, visit embeddedcomputing.com

We're back for Episode 154! In this episode Cody and Eric catch up on the news and cover 6 Good Games With Double Jump   11:27 - Quick Questions 29:36 - Patreon Song 34:08 - Tea Time With Tim - AliExpress Pickups 1:02:49 - Cody's Corner - Dreamcast 1:34:22 - News 2:11:32 - 6 Good Games With Double Jump   News Tim – The Multisystem2 from Heber has now been released for general sale. This is the successor to the original Multisystem that allowed you to consolise the DE10 Nano MiSTer system. The Muiltisystem2 offers everything including the FPGA on board along with all the connections you might need for controllers, inputs and outputs. There is a digital and analog version of the system, shipping starts with pre-orders in August.  https://shop.heber.co.uk/mister-multisystem/    Cody - https://www.timeextension.com/news/2025/04/alan-wake-and-max-payne-dev-mikko-huovinen-is-creating-a-space-harrier-style-shooter-for-vectrex  Eric - Slap Fight set to Slap Back onto Genesis - Retro News https://www.retronews.com/slap-fight-set-to-slap-back-onto-genesis/  Cody – Reviving the use of a great old controller. https://www.timeextension.com/news/2025/05/the-wavephoenix-brings-nintendos-best-controller-back-to-life-for-usd5  Tim – Vicky Lamburn (Vix) has started a new series of videos all about the rise and fall of one of our favorite software and hardware publishers Hudson Soft on her Vix (not) in Japan YouTube channel. Vicky explained this video to me on our recent travel to the South West Amiga Group, now its out for everyone to enjoy, please give it a watch.  https://youtu.be/sYAxNEJRs1s?si=079vLJHw7k_xOvOR  Cody - https://www.timeextension.com/news/2025/04/random-this-new-3d-demo-for-the-neo-geo-is-seriously-blowing-our-minds  Eric - Retro gaming lounge at Seattle airport lets you play for free - The Points Guy https://thepointsguy.com/news/retro-gaming-lounge-seattle-airport/  Cody - https://www.timeextension.com/news/2025/04/evercades-namco-carts-now-work-on-the-vs-thanks-to-a-stealthy-update  Eric - Neo Geo Evercade Cartridge Delayed - Retro News https://www.retronews.com/neo-geo-evercade-cartridge-delayed/  Cody - https://www.timeextension.com/news/2025/04/retro-fighters-latest-release-is-a-wireless-evolution-of-the-classic-xbox-360-controller  Eric - Retro-style Tower Defence Gnomes Steam review - Retro News https://www.retronews.com/retro-style-tower-defence-gnomes-steam-review/  Cody - https://www.timeextension.com/news/2025/04/limited-run-games-is-releasing-doom-plus-doom-ii-in-a-box-that-can-run-doom  Eric -

Steve Summers speaks with SE Radio host Sam Taggart about securing test and measurement equipment. They start by differentiating between IT and OT (Operational Technology) and then discuss the threat model and how security has evolved in the OT space, including a look some of the key drivers. They then examine security challenges associated with a specific device called a CompactRIO, which combines a Linux real-time CPU with a field programmable gate array (FPGA) and some analog hardware for capturing signals and interacting with real-world devices. Brought to you by IEEE Computer Society and IEEE Software magazine.

Supercharge your analysis with AI! Get 15% of your membership with our special link here: https://finchat.io/csi/Join us on Discord with Semiconductor Insider, 25% off an annual membership through May 15! Get clarity when other investors panic. https://ko-fi.com/chipstockinvestor/link/MARKETMELTDOWN25In this episode of Chip Stock Investor, we discuss the sale of Intel's Altera and what that means for FPGA pure play, Lattice Semiconductor. We explore the implications for Lattice, analyze their current valuation metrics, and discuss potential market changes following the Altera deal. Learn about Lattice's financial health, market strategy, and how Intel's strategic sale could influence their future.Sign Up For Our Newsletter: https://mailchi.mp/b1228c12f284/sign-up-landing-page-short-formJoin us on Discord with Semiconductor Insider: https://ko-fi.com/chipstockinvestor/tiersSafeguard your personal information with Aura's monitoring service – try it free for two weeks and see where your data might be lurking: https://aura.com/chipstockinvestor

In this episode of Validated, host Austin talks with Chaofan Shou about building Solayer, high-performance side chain for Solana. Chaofan describes the specifics of Solayer's hybrid model, which sits between a traditional Layer 1 and Layer 2, offering faster execution environments for market makers and reducing high priority fees. They get into its technical architecture, including the use of specialized hardware like FPGA and SDN for optimized transaction processing and state management. The conversation also touches on their plans for ecosystem development, particularly within the DeFi and gaming sectors, and addresses the balance between scalability and decentralization.  

-New Qualcom chip for Arm gaming: https://www.engadget.com/gaming/next-gen-snapdragon-g-series-chips-will-power-handhelds-from-ayaneo-onexsugar-and-retroid-pocket-131733930.html -5090 review -Palmer Luckey is making an FPGA n64? https://www.timeextension.com/news/2025/03/palmer-luckey-just-invoked-the-matrix-to-tease-a-new-nintendo-64-console -2 seasons of God of War at least at Amazon: Amazon's God of War TV series is already looking toward season 2 -Analogue 3D is delayed: Analogue's 4K Nintendo 64 retro console has been delayed, again -Xbox Copilot will help you cheat: Microsoft's new Xbox Copilot will act as an AI gaming coach -Half Life 2 RTX Demo available for download. https://www.reddit.com/r/Games/comments/1je4wtx/halflife_2_rtx_demo_available_now_for_download/ https://www.youtube.com/watch?v=bLxWqZy1U-8 -Maybe I DO need an xbox 360 https://www.theverge.com/news/631102/xbox-360-hack-homebrew-badupdate-exploit-usb

[Original air date: 06/14/2024] This week, Gerry and Aaron sit down with Jamie - better known as her internet handle, Kitrinx, to talk all about the MiSTer FPGA Project. Jamie has developed and contributed to several cores on MiSTer, and we take a deep dive into what its like to develop cores, manage and create the MiSTer Discord, and of course relive some video game memories.CREDITS Aaron

Ultra I&C, headquartered in Austin, Texas, has a 50-year history in the cleared community focusing on multi-domain communications, command and control, and cybersecurity. DaVontte Archie, Talent Acquisition and HR Partner, shares why thoughtful interview follow-up can really make you stand out from your competition, plus why failure at Ultra is OK.5:09 Hiring engineers in general, including software engineers, data scientists, systems engineers, artificial intelligence, machine learning, FPGA engineers, program finance, IT, and information security.7:50 In general core hours are 9am – 3pm local time. Monday through Thursday work week with half days on Fridays.8:46 Mission-focused culture. 750 employees. Leadership is very accessible. Agile organization that understands it has to change. Find show notes and additional links at: https://clearedjobs.net/ultra-intelligence-and-communications-fail-fast-podcast/_ This show is brought to you by ClearedJobs.Net. Have feedback or questions for us? Email us at rriggins@clearedjobs.net. Sign up for our cleared job seeker newsletter. Create a cleared job seeker profile on ClearedJobs.Net. Engage with us on LinkedIn, Facebook, Instagram, X, or YouTube. _

Lords: * Andi * Casey Topics: * Lifehacks as communion with the divine * I decided to fire my computer * Winston is starting to forget things Microtopics: * A Star Trek watchalong podcast that doesn't exist yet. * Positing that what you said is no longer an NDA violation by the time this episode comes out. * Plugging a fake game that you worked on. * Astrobot. * Horror movie clinky noises that you can't hear over the PS4 fan noises. * Caffeine-infused mints with Tux the Penguin branding on Think Geek dot com. * The pre-eminent source for Life Hacks. * Using a hotel shower cap to bake bread. * Anime girls that are happy to see you. * That one time Film Crit Hulk broke character. * The joy of moving efficiently through the world. * More efficient ways to set the microwave timer. * Hotel rooms that you can bake bread in. * Whether bread should contain hair. * Tricking yourself into not being bored while doing something you have to do. * Reading 50 life hacks and applying none of them because. * Viral Life Hack that's killed 33 people. * A life hack that already had a body count in the double digits before someone made a TikTok about it. * Getting really fed up with computers. * Cryptographic signing processes that you can't participate in. * The HDCP certification board taking steps to ensure nobody can take a screen shot of their Crunchy Roll anime. * The analog hole. * Open source web browsers that can't see DRM content. * Microsoft-authenticated Linux installations. * Designing a circuit that solves a math problem. * Stamping a circuit onto your circuit clay. * An independent circuit re-implementation of video game hardware. * Should you use FPGA to do a thing? * Ridiculous multi-level memory caching systems. * Bootstrapping an FPGA design tool that runs on an FPGA device. * Every single circuit doing something on every single cycle. * Voltages going high and/or low. * Making a bunch of CPUs and testing them afterwards to see how many GHz they have. * Why the PS3 Cell processor had 7 SPUs * The industrial uses of the Cell processor. * A GLSL compiler that outputs FPGA circuits. * Mr. MiSTer. * Open-hardware laptops. * Inventing an open-source GPU. * Multics or Minix. * Writing a Breakout clone in Rust targeting the weird CPU your friend just invented. * Making a terrible first effort that is the right kind of good enough. * A laptop that has a FPGA where the CPU/GPU usually goes. * 1970s-era TV games. * The Epoch Cassette Vision. * A game console with interchangeable cartridges where the CPU is on the cartridge. * The Glasgow Interface Explorer. * Describing your FPGA circuit in Python. * Manufacturing homebrew Cassette Vision Homebrew cartridges for the audience of zero Cassette Vision owners. * Making art just for you, in the most overly elaborate and overly complicated way possible. * The programmer equivalent of going to swim with the dolphins. * Diagonal pixels. * Childhood amnesia. * Remembering your memories. * Using 10% of your brain. (And also the other 90%.) * Knowing things about stuff. * When one brother dies, the other brother gets their memories. * Memories that are formed before vs. after you learn to talk. * Being persecuted for being friends with a girl. * Rules of heteronormativity being enforced by three year olds. * Getting off of Wordpress.

Some great new functionality being added to consoles old, new, and even a whole new FOSS based handheld to check out! The wpa2psp plugin for PSP was released and took off, allowing most PSP consoles to get back onto modern WiFi networks again. The PS Vita gets some more love with a couple more ports, one for Carmageddon and another being the Ultimate Spiderman game on Android. We even go to the library on this episode thanks to the Video Game History Foundation's launch of a digital library! PS5's JAR Loader gets updated as we now see read and write access on firmwares up to 7.61! A newer minimalist type setup for a PlayStation ODE is shown thanks to PicoStation's recent updates allowing for better compatibility across the PS1's library. After the pleasant surprise of Grand Theft Auto 3 being ported to the Dreamcast, we're in for another surprise seeing the beginnings of Grand Theft Auto: Vice City being ported over! A whole new system you can build from scratch, the Game Bub, is a project we check out being a handheld FPGA console compatible with the Game Boy family of games. Finally, we take a look at... McDonald's India API security? Yeah, I won't explain that one, just give it a listen and a laugh.

[Original air date: 05/17/2024] This week we kick off the first in our series of Retrospected & Rehabbed - where we talk about a console, best ways to play today, some fun facts, and our memories with the games and hardware. The console for our first edition is none other than The Nintendo Entertainment System - or Regular-Ass Nintendo if you will.CREDITS Gerry With a G - Host Aaron

4:30 - Nintendo Switch 2 31:27 - Magic Mind 35:50 - Mortal Kombat 46:58 - P47 II MD 54:05 - Lunar 1:03:48 - No Man's Sky 1:16:35 - Forza Horizon 5 1:22:00 - Ninja Gaiden 4 1:31:47 - Turbo Overkill 1:35:27 - GalaxyLand 1:40:22 - Skydance's Behemoth 1:43:36 - PlayStation 5 Pro Switch 2 officially revealed, details coming April 2nd, 2025 Ted Price is retiring

Here's the Supporter-only Q&A from January 2nd, 2025. All comments and questions are fielded through the supporter service Q&A page. Please consider supporting this channel via monthly support services, tips, or even just by using our affiliate links to purchase things you were already going to buy anyway, at no extra cost to you: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.retrorgb.com/support.html⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ T-Shirts: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://retrorgb.link/tshirts⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Amazon Recommended List: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://retrorgb.link/amazon⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ TIMESTAMPS (please assume all links are affiliate / paid links that pay RetroRGB a commission on each sale.  Even if links are currently not affiliate, I may update them with one, should a partner list that item for sale in the future): 00:00  Welcome 00:11  Power Cord Orientation 03:01  Ramond HyperV VM's:  Hyper V Windows 10 : https://mega.nz/file/zx4n3YbJ#ukqnFeA_E1gIibIGHvt0IUCHbCzInh912MYVWiefIEU Hyper V Windows 11: https://mega.nz/file/29xjGYgS#MY8D02KIH2X97lj5bYSdzJ3szX3jAg1jMjNXSKErfMU VMWare / Player 16.2: https://mega.nz/file/K5xVjCKZ#ecGI4oYi4FKKSIN4P4F0HZOznfAYZjaqeuaEKjdV6-k 03:50  Cables through a wall for a new room setup 10:37  FPGA-based IC replacements 13:50   MiSTer-based Arcade Machine 18:03  Genesis - 32x- SCD - Everdrive - Anything needed?:  https://retrorgb.link/toppsu 20:53  Inline UPS as Power Conditioner:  https://www.cyberpowersystems.com/blog/how-does-a-ups-work/  https://amzn.to/4gC8CYB   23:55  GameCube:  https://www.retrorgb.com/flippy-drive-updates.html 24:55  LCDCRT Issues:  https://github.com/MiSTer-devel/Main_MiSTer/blob/master/MiSTer.ini  /  https://www.retrorgb.com/scanline-filters-on-the-lcd-crt-kit.html 27:17  Why NOT to use USB-PD:  https://youtube.com/live/OsuLAy2lgIk 28:31  Lumacode:  https://www.retrorgb.com/ossc-lumacode-functionality-demod.html 30:27  PS2 on TINK5x…or get the CE?:  https://youtu.be/LvfWZ5coqCA 33:26  Thank you!:  https://www.retrorgb.com/support.html

Welcome to episode 285 of the Explain it to me Like I'm 5 Podcast, formerly known as The Cloud Pod – where the forecast is always cloudy! We've got a lot of news this week, including the last of our coverage from re:Invent, ChatGTP Pro, FPGA, and even some major staffing turnovers. Titles we almost went with this week: Throw $200 dollars in a fire with ChatGPT Pro Jeff Barr is wrapped up by Agentic AI The Tribble with Trilliums The Wind in the Quantum Willows  Rise of the dead instances FPGA and PowerPC Jeff Barr is replaced by Nova The Cloud Pod: Return of the dead instances types After 6 year Jeff Barr hands over the reigns to the CloudPod For our 6th birthday Jeff barr Retires For our 6th birthday jeff barr delegates announcements to the cloud pod 6 years of meaningless PR drivel 6 years of cloud news and we still don't know what Quantum computing is A big thanks to this week's sponsor: We're sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You've come to the right place! Send us an email or hit us up on our slack channel for more info.  General News HAPPY 6th BIRTHDAY!  2:00 HashiCorp at re:Invent 2024: Security Lifecycle Management with AWS Hashi is a big sponsor of re:Invent, so of course they had some news of their own to release.  HCP Vault Secrets auto-rotation is now generally available.  Dynamic secrets are generally available via HCP Vault Secrets. Secrets sync will help keep your secrets synced with AWS Secrets Manager. It still appears to be one direction, but you can now also view secrets in AWS Secrets Manager that are managed by vault.  HCP Vault Radar, now in beta, automates the detection and identification of unmanaged secrets in your code, including AWS infrastructure configurations 03:10 Matthew – “This qualifies under the category of things that I feel like we talked about so long ago, I just already assumed was GA. I’m surprised that it wasn’t.” 03:34 HashiCorp at re:Invent 2024: Infrastructure Lifecycle Management with AWS Terraform AWS provider is now at 3 billion downloads.  The

We're back for Episode 144! In this episode Cody and Eric catch up on the news + Battle Of The Systems: Major Title (SNES) vs Human Sports Festival (PCE-CD)   13:30 - Quick Questions 43:08 - Patreon Song 48:04 - Eric's Take - Gaming Roadmap 2025 1:07:26 - Tea Time With Tim - The Spectrum 1:41:14 - News 2:56:08 - Battle Of The Systems: Major Title (SNES) vs Human Sports Festival (PCE-CD)   News -     CODY – VR Contra is a thing? https://www.timeextension.com/features/how-x8s-contra-super-wall-storm-is-taking-konamis-series-into-the-realm-of-vr  Tim – New all in one MiSTer board coming from Heber the makers of the Multisystem. The Multisystem 2 is coming in 2025, this will be a fully consolised board with all the connections, RAM, outputs and the FPGA all on the same board, completely plug and play. Richard and the team at Heber are working hard to bring us this new system, it will require a new enclosure design that they are starting to work on. More details to follow in the new year.    Eric - Indie Retro News: Sarah Jane Avory is working an Ultima-style RPG for the C64!  https://www.indieretronews.com/2024/12/sarah-jane-avory-is-working-ultima.html  Cody – Killer NES and Genesis Shmups - https://www.brokestudio.fr/product/changeable-guardian-estique-nes/      https://www.timeextension.com/news/2024/12/missed-zpfs-kickstarter-you-can-now-pre-order-the-promising-mega-drive-genesis-shmup-online  Tim – New Atari STE racing game now available (from the 9th of December). FASTER is an arcade style racer from Jonathan Thomas. He has previously ported Pole Position to the STE. FASTER builds on this with a similar look and feel to the aracde racer WEC Lemans. This will be released at the Silly Venture game competition on the weekend of the 6th of December and then released on the 9th.  https://youtu.be/T6nQeMhw2Es?si=hlzRHOnuTVINUs1I  Cody - Want to buy a worse TV just because? https://retrododo.com/theres-a-new-retro-themed-monitor-that-allows-you-to-play-your-games-in-monochrome/  Cody – Where was this last episode!? https://www.indieretronews.com/2024/12/tank-in-dungeon-battle-dangerous-robots.html  Eric - Fan-Made Doom 64 Dreamcast Port Now The "Definitive" Version Of The Game  https://www.timeextension.com/news/2024/12/fan-made-doom-64-dreamcast-port-now-the-definitive-version-of-the-game  Cody – Star Wars + Amiga + New Release = Really Cool! https://www.timeextension.com/news/2024/12/the-amiga-just-got-an-amazing-new-star-wars-game-made-by-fans  Cody – Gameboy Retrogame update! https://modretro.com/collections/games  Tim – Just announced coming soon in 2025, Raspberry Pi P500 all in one system with keyboard, same kind of look as the P400 but with Pi 5 internals. Also, a new Raspberry Pi monitor with 15.6″ full HD IPS panel colur and branding matching the Pi P500. The P500 coming in around $90 and the screen around $100. Pre-orders are open.  https://www.raspberrypi.com/news/raspberry-pi-500-and-raspberry-pi-monitor-on-sale-now/  CODY – Shoutout to Indie Retro News Staying in Business!  https://www.indieretronews.com/2024/12/the-future-of-indieretronews-part-2.html#more  Cody – More Keyboards!? https://retrododo.com/8bitdo-announce-new-mechanical-keyboard-that-pays-homage-to-the-original-xbox/   https://retrododo.com/8bitdo-s-edition-mechanical-keyboard-review/    Eric (From Pajaco) - Pico-8 Handhled Coming? - https://www.lexaloffle.com/bbs/?tid=144180  Cody - More EXA-Arcadia News? https://www.timeextension.com/news/2024/11/yuzo-koshiros-genesis-shmup-earthion-is-getting-an-upgraded-arcade-release  Cody - https://retrododo.com/the-donkey-kong-country-expansion-opens-this-december-at-super-nintendo-world/  Eric (From Pajaco) - Another bit of fun news https://evercade.co.uk/evercade-game-of-the-month-2024-9-murtop/  Cody - https://ozzyouzo.itch.io/captain-barrel  Cody – NEWS OF THE WIERD! https://retrododo.com/kfc-release-new-tamagotchi-where-you-look-after-a-chicken-drumstick/  https://www.ebay.com/sch/i.html?_from=R40&_trksid=p2334524.m570.l1313&_nkw=kfc+tamogachi&_sacat=0&_odkw=kfc+tamogathi&_osacat=0  https://www.timeextension.com/news/2024/11/piglets-big-game-gets-compared-to-resident-evil-and-silent-hill-starts-selling-for-big-bucks  Please give us a review on Apple Podcasts! Thanks for listening! You can always reach us at podcast@pixelgaiden.com. Send us an email if we missed anything in the show notes you need. You can now support us on Patreon.  Thank you to Henrik Ladefoged, Roy Fielding, Matthew Ackerman, Josh Malone, Daniel James, 10MARC, Eric Sandgren, Brian Arsenault, Retro Gamer Nation, Maciej Sosnowski, Paradroyd, RAM OK ROM OK, Mitsoyama, David Vincent, Ant Stiller, Mr. Toast, Jason Holland, Mark Scott, Vicky Lamburn, Mark Richardson, Scott Partelow, Paul Jacobson, Steve Rasmussen, Steve Rasmussen's Mom, Retro Gamer Nation, Peter Price, Brett Alexander, Jason Warnes, Josh Malone (48kram), AndrewSan, and Adam from Commodore Chronicles for making this show possible through their generous donation to the show.   Support our sponsor Retro Rewind for all of your Commodore needs! Use our page at https://retrorewind.ca/pixelgaiden and our discount code PG10 for 10%    

ANTIC Episode 112 In this episode of ANTIC The Atari 8-Bit Computer Podcast… we have several Christmas ideas for you, we tell you about projects that would allow creating a new reproduction Atari 800XL, and we wet our appetites for the current Atari's hot sauce while wearing their ugly Christmas sweater … READY! Recurring Links  Floppy Days Podcast  AtariArchives.org  AtariMagazines.com  Kay's Book “Terrible Nerd”  New Atari books scans at archive.org  ANTIC feedback at AtariAge  Atari interview discussion thread on AtariAge  Interview index: here  ANTIC Facebook Page  AHCS  Eaten By a Grue  Next Without For  Links for Items Mentioned in Show: What we've been up to Vox ex Machina: A Cultural History of Talking Machines by Sarah A. Bell - https://archive.org/details/mit_press_book_9780262375870/page/169/mode/2up?q=savetz  Intellivision: How a Videogame System Battled Atari and Almost Bankrupted Barbie by Tom Boellstorff and Braxton Soderman - https://archive.org/details/mit_press_book_9780262380553/  MIT Press: Open Access Materials - https://archive.org/details/mit_press_open_access  A Treasure Chest of Ampex Tapes Saves Early Computer History - https://www.ampex.com/a-treasure-chest-of-ampex-tapes-saves-early-computer-history/  Atari 400/800 Reference Card (Atari BASIC and Microsoft BASIC) by Nanos Systems Corp. - https://archive.org/details/1984-03-anticmagazine/page/102/mode/2up  Best of Creative Computing (Volumes I & III): https://archive.org/details/Best_of_Creative_Computing_Vol_1_1978_Creative_Computing_Press  https://archive.org/details/bestofcreativeco0003unse  Cassette repair - https://www.amazon.com/dp/B0DCGJ7GQF  Stray Pointers podcast with the ANTIC crew - Jim Lawless - https://straypointers.com/e/s2e19.htm  Recent Interview Shows ANTIC Interview 442 - Bob Stein, Atari Research ANTIC Interview 443 - Rick Reaser, Current Notes Magazine ANTIC Interview 444 - Nick Kennedy, SIO2PC and ATR ANTIC Interview 445 - Vince Cate, The Critical Connection News Ugly Christmas sweaters - https://atari.com/collections/holiday-collection?filter.p.product_type=Sweatshirts&sort_by=manual  Atari Hot Sauce - https://atarisauce.com/  Christmas Critters: https://www.atariteca.net.pe/2024/11/anuncian-demo-de-christmas-critters.html  And at AtariAge - https://forums.atariage.com/topic/375904-christmas-critters-wip-game-demo/  he just released an “engine prototype demo” - https://tigerskunk.itch.io/atari-xmasdemo  And Saberman has already done a quick video on it - https://youtu.be/efP2WOLnxvY  Revive Machines is working on the injection molds of RM 800XL, the modern FPGA recreation of the Atari 800XL - Philsan69: https://x.com/philsan69/status/1856461217792999494?s=58  https://revive-machines.com/index-en.html  Clear Case Kickstarter for 800XL has begun (Nov. 1) - https://www.kickstarter.com/projects/seethruit/injection-molded-clear-case-for-atari-800xl-computer/  Brian Reifsnyder Designs an "Advanced Remake" of Atari's 800XL Mainboard - https://www.hackster.io/news/brian-reifsnyder-designs-an-advanced-remake-of-atari-s-800xl-mainboard-95cbc0823bb3.amp  AtariBASICs November newsletter - John Zielke - https://ataribasics.com/  Atari Addict Collector's Magazine - https://www.pixel.addict.media/shop/atari-addict-magazine  Atari Programmers Society Newsletter: https://archive.org/details/wire-taps-atari-programmers-society-newsletter-april-1986-vol-4-num-4  v1n6 1983 - https://archive.org/details/wiretaps-v1n6  Cartridge extender card for the Atari 1200XL - ReifsnyderB - https://www.tindie.com/products/5cfab/cartridge-extender-card-for-the-atari-1200xl/  Improved Keyboard on an XE - https://amzn.to/4i10QZz  Vintage Computer Center starting back up (Gavin Haubelt) - http://www.vintagecomputercenter.com  FastBASIC install/debugger - Eric Carr https://marketplace.visualstudio.com/items?itemName=EricCarr.fastbasic-debugger  https://www.youtube.com/watch?v=0fOm8Mq4qFA  400 mini it is available from Amazon Germany for $54 plus shipping. - https://www.amazon.de/-/en/RETROGAMES-THE400MINI/dp/B0CRYXTL82  Upcoming Shows REMAINING IN 2024 Silly Venture WE (Winter Edition) - Dec. 5-8 - Gdansk, Poland - https://www.demoparty.net/silly-venture/silly-venture-2024-we  Atari Party 2024 - Dec. 7 (noon - 4p.m.) - Quakertown Train Station, Quakertown, PA - http://atariparty.org/  2025 Vintage Computer Festival SoCal - February 15-17, 2025 - Hotel Fera Events Center, Orange, CA - vcfsocal.com  Midwest Gaming Classic - April 4-6 - Baird Center, Milwaukee, WI - https://www.midwestgamingclassic.com/  VCF East - April 4-6, 2024 - Wall, NJ - http://www.vcfed.org  Indy Classic Computer and Video Game Expo - April 12-13 - Crowne Plaza Airport Hotel, Indianapolis, IN - https://indyclassic.org/  Fujiama - August 11-17 - Lengenfeld, Germany - http://atarixle.ddns.net/fuji/2025/  YouTube Videos The Atari 1200xl - Atari's 8-bit red-headed stepchild - Power of Vintage - https://www.youtube.com/watch?v=cTLTJzZ7-I8  Atari XE memory extension (512 KB) in 2 easy ways - RetroKernal - https://www.youtube.com/watch?v=BvBkMEnONgs  Atari 65 XE vs Commodore 64 | 70s 80s Computer System Competition TV Commercial - VideoGames Replay - https://www.youtube.com/watch?v=jwMNGMHKZ0w  Atari Computers Sales, Marketing Strategy 80's TV Commercial - VideoGames Replay - https://www.youtube.com/watch?v=OA7kY9pkFxM  Atari 800 Game: Scram (1980 Atari) - Old Classic Retro Gaming - https://www.youtube.com/watch?v=M8XRtICfBuQ  CHM: Oral History of Nolan Bushnell - https://youtu.be/izYWqhUGBGA?si=M4T43I-tJ2mp2EhA  New at Archive.org  https://archive.org/details/computer-shopper-jan-1989-vol-9-num-1-atari-articles  https://archive.org/details/atari-price-list-june-1982-and-letters  https://archive.org/details/europa-america-aventuras-com-o-atari  https://archive.org/details/computer-83-special-section-the-oregonian-june-16-1983  “The Dirty Book”: https://archive.org/details/the-dirty-book-v-2-n-2  https://archive.org/details/TheDirtyBookV2N1  Referenced by - https://bsky.app/profile/lainenooney.bsky.social/post/3lbldh3w2hk2m  A Word From Our Sponsor https://www.youtube.com/watch?v=jwMNGMHKZ0w  New at GitHub https://github.com/pvbestinfoo/Atari_8-Bit_Rom_Image_File_Explorer  https://github.com/sidneycadot/sam  https://github.com/dpicken/atari-hw  https://github.com/JSJvR/atari-8-bit-utils  https://github.com/GRHOnline/Mono8bitmap  https://github.com/fredlcore/1K-RainBox