Podcasts about stallman

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

See omnystudio.com/listener for privacy information.

I avsnittet pratar Alex & Tobias om "skitifiering" (hej Windows 11!) och nya Omarchy Linux. De delar också sina tankar från Richard Stallmans föreläsning i Bahnhof-bunkern - om digital frihet, vikten av kontanter, LibreJS och GNU Taler. https://trevligmjukvara.se Hosted on Acast. See acast.com/privacy for more information.

In this episode ⁠⁠⁠Crawlspace Media⁠⁠⁠'s Tim Pilleri and Lance Reenstierna speak with Jennifer MacPhee and Katie Wilshire about the unsolved murder of Jennifer's mom Julianne Stallman from Butte, Montana in 1994. Listener discretion is advised. This is part 2 of 2. This interview was originally published on Missing on August 3rd, 2023. To report a tip anonymously, call Crime Stoppers at 406-782-7336. Sources: ⁠⁠https://www.kxlf.com/news/local-news/murder-in-the-mining-city-who-killed-julianne-stallman⁠⁠. ⁠⁠⁠https://www.facebook.com/groups/177837217637/⁠⁠. ⁠⁠https://www.co.silverbow.mt.us/203/Crimestoppers⁠⁠. ⁠⁠⁠https://nbcmontana.com/news/local/homicide-cold-case-still-unsolved-in-butte⁠⁠⁠. ⁠⁠⁠https://omny.fm/shows/impact-statement/the-unsolved-murder-of-julianne-stallman⁠⁠⁠. ⁠⁠⁠https://billingsgazette.com/news/state-and-regional/montana/investigator-probes--year-old-murder/article_7d33a134-028d-5da9-a2e3-93c8a4234188.html⁠⁠⁠. Follow Missing: IG: ⁠⁠https://www.instagram.com/MissingCSM⁠⁠. TT:⁠⁠ https://www.tiktok.com/@missingcsm⁠⁠. FB:⁠⁠ https://www.facebook.com/MissingCSM⁠⁠. X:⁠⁠ https://twitter.com/MissingCSM⁠⁠. Spotify:⁠⁠ https://open.spotify.com/show/0yRXkJrZC85otfT7oXMcri⁠⁠. Youtube:⁠⁠ https://www.youtube.com/missingcsm⁠⁠. Apple:⁠⁠ https://podcasts.apple.com/us/podcast/missing/id1006974447⁠⁠. Follow Crawlspace: IG:⁠⁠ https://www.instagram.com/Crawlspacepodcast⁠⁠. TT:⁠⁠ https://www.tiktok.com/@crawlspacepodcast⁠⁠. FB:⁠⁠ https://www.facebook.com/Crawlspacepodcast⁠⁠. X:⁠⁠ https://twitter.com/crawlspacepod.⁠⁠ Spotify:⁠⁠ https://open.spotify.com/show/7iSnqnCf27NODdz0pJ1GvJ⁠⁠. Youtube:⁠⁠ https://www.youtube.com/crawlspace⁠⁠. Apple:⁠⁠ https://podcasts.apple.com/us/podcast/crawlspace-true-crime-mysteries/id1187326340⁠⁠. Check out our entire network at⁠⁠ http://crawlspace-media.com/⁠⁠. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode ⁠⁠Crawlspace Media⁠⁠'s Tim Pilleri and Lance Reenstierna speak with Jennifer MacPhee and Katie Wilshire about the unsolved murder of Jennifer's mom Julianne Stallman from Butte, Montana in 1994. Listener discretion is advised. This is part 2 of 2. This interview was originally published on Missing on August 3rd, 2023. To report a tip anonymously, call Crime Stoppers at 406-782-7336. Sources: ⁠https://www.kxlf.com/news/local-news/murder-in-the-mining-city-who-killed-julianne-stallman⁠. ⁠⁠https://www.facebook.com/groups/177837217637/⁠. ⁠https://www.co.silverbow.mt.us/203/Crimestoppers⁠. ⁠⁠https://nbcmontana.com/news/local/homicide-cold-case-still-unsolved-in-butte⁠⁠. ⁠⁠https://omny.fm/shows/impact-statement/the-unsolved-murder-of-julianne-stallman⁠⁠. ⁠⁠https://billingsgazette.com/news/state-and-regional/montana/investigator-probes--year-old-murder/article_7d33a134-028d-5da9-a2e3-93c8a4234188.html⁠⁠. Follow Missing: IG: ⁠https://www.instagram.com/MissingCSM⁠. TT:⁠ https://www.tiktok.com/@missingcsm⁠. FB:⁠ https://www.facebook.com/MissingCSM⁠. X:⁠ https://twitter.com/MissingCSM⁠. Spotify:⁠ https://open.spotify.com/show/0yRXkJrZC85otfT7oXMcri⁠. Youtube:⁠ https://www.youtube.com/missingcsm⁠. Apple:⁠ https://podcasts.apple.com/us/podcast/missing/id1006974447⁠. Follow Crawlspace: IG:⁠ https://www.instagram.com/Crawlspacepodcast⁠. TT:⁠ https://www.tiktok.com/@crawlspacepodcast⁠. FB:⁠ https://www.facebook.com/Crawlspacepodcast⁠. X:⁠ https://twitter.com/crawlspacepod.⁠ Spotify:⁠ https://open.spotify.com/show/7iSnqnCf27NODdz0pJ1GvJ⁠. Youtube:⁠ https://www.youtube.com/crawlspace⁠. Apple:⁠ https://podcasts.apple.com/us/podcast/crawlspace-true-crime-mysteries/id1187326340⁠. Check out our entire network at⁠ http://crawlspace-media.com/⁠. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode ⁠Crawlspace Media⁠'s Tim Pilleri and Lance Reenstierna speak with Jennifer MacPhee and Katie Wilshire about the unsolved murder of Jennifer's mom Julianne Stallman from Butte, Montana in 1994. Listener discretion is advised. This is part 1 of 2. This interview was originally published on Missing on August 3rd, 2023. To report a tip anonymously, call Crime Stoppers at 406-782-7336. Sources: https://www.kxlf.com/news/local-news/murder-in-the-mining-city-who-killed-julianne-stallman. ⁠https://www.facebook.com/groups/177837217637/. https://www.co.silverbow.mt.us/203/Crimestoppers. ⁠https://nbcmontana.com/news/local/homicide-cold-case-still-unsolved-in-butte⁠. ⁠https://omny.fm/shows/impact-statement/the-unsolved-murder-of-julianne-stallman⁠. ⁠https://billingsgazette.com/news/state-and-regional/montana/investigator-probes--year-old-murder/article_7d33a134-028d-5da9-a2e3-93c8a4234188.html⁠. Follow Missing: IG: https://www.instagram.com/MissingCSM. TT: https://www.tiktok.com/@missingcsm. FB: https://www.facebook.com/MissingCSM. X: https://twitter.com/MissingCSM. Spotify: https://open.spotify.com/show/0yRXkJrZC85otfT7oXMcri. Youtube: https://www.youtube.com/missingcsm. Apple: https://podcasts.apple.com/us/podcast/missing/id1006974447. Follow Crawlspace: IG: https://www.instagram.com/Crawlspacepodcast. TT: https://www.tiktok.com/@crawlspacepodcast. FB: https://www.facebook.com/Crawlspacepodcast. X: https://twitter.com/crawlspacepod. Spotify: https://open.spotify.com/show/7iSnqnCf27NODdz0pJ1GvJ. Youtube: https://www.youtube.com/crawlspace. Apple: https://podcasts.apple.com/us/podcast/crawlspace-true-crime-mysteries/id1187326340. Check out our entire network at http://crawlspace-media.com/. Learn more about your ad choices. Visit megaphone.fm/adchoices

Fermento nel mondo dei browser. Stallman presenta GNU Taler. Dipendenti infiltrati dalla Corea del Nord. Il flash che crashava i Raspberry Pi. Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Franco Solerio, Francesco Facconi, Giulio CupiniProduttori esecutivi:Sandro Acinapura, ---, Riccardo Peruzzini, @Geckonode, Fiorenzo Pilla, Matteo Faccio, Mirto Tondini, Paolo Boschetti, @User36452908, Arzigogolo, Elisa Emaldi - Marco Crosa, Nicola Gabriele Del Popolo, Nicola Bisceglie, Roberto Medeossi, Stefano Augusto Innocenti, Fabrizio Bianchi, Mauro Boffa, Matteo Molinari, @Stefano, Roberto Esposito, @Akagrinta, Marco Zambianchi (Astronauticast), Flavio Castro, @Jh4Ckal, Simone Pignatti, Idle Fellow, Diego Venturin, Il Pirata Lechuck, Paolo Bernardini, Davide Tinti, Giuseppe Benedetti, Manuel Zavatta, Michele Coiro, Roberto Tarzia, Christian A Marca, Gianfranco Di SummaSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo del primo acquisto.Links:Letter to Arc members 2025Michael Tsai - Arc and DiaChatGPT future just revealed — get ready for a ‘super assistant'Zen BrowserRichard Stallman presenta GNU Taler: pagamenti digitali sicuriDigital Payment System GNU Taler Gets Green Light in SwitzerlandJapan Post launches 'digital address' systemIl collega infiltrato della Corea del NordFrattasi 'Portare hacker in Agenzia sarebbe un rischio'The Xenon Death Flash: How a Camera Nearly Killed the Raspberry Pi 2Cloudflare CEO: Football Piracy Blocks Will Claim Lives; I Pray No One DiesUE sceglie AGCOM per testare nuova app di verifica dell'età onlineThe Times and Amazon Announce an A.I. Licensing DealDuolingo CEO tries to walk back AI-first comments, failsGoogle Maps can't explain why it falsely labeled German autobahns as closed‘Humanity deserves better': Jony Ive and Laurene Powell JobsDentro il Matebook Fold di Huawei è il chip più importante al mondoValve CEO Gabe Newells Neuralink competitorAnduril and Meta Team Up to Transform XR for the American MilitaryFacebook Served Beauty Ads to Teen Girls Who Deleted SelfiesTrump Taps Palantir to Create Master Database on Every AmericanPS5, strategia dei live service e conseguenze su esclusive single playerGingilli del giorno:Lee Boonstra - Prompt Engineering - White Paperundercut-f1 - tempi e dati dei GP di Formula 1 in direttaSigmaOS - nuovo browser con AISupporta Digitalia, diventa produttore esecutivo.

Perche' Navigare senza Javascript - La versione di StallmanStallman ha una crociata personale contro Javascript.Non l'ho seguita da tempo, ma le soluzioni che ho adottato al problema che conosco e condivido perfettamente (ne ho parlato in passato piu' volte) tendono a risolvere la questione.Ma non sempre e' possibile.Vediamo come funziona e perche' non js non rispetta le nostre libertà.

Freedom for users and open and free software - differences (italiano)Scusate il titolo inglese, mi e' venuto naturalmente.Parliamo ora di Stallman, FSF, EFF, FSFE, le freedom e come riconoscerle ora

Tra me e Stallman solo un piatto di ravioli, per due oreUn incontro fantastico. Ve lo passo live, episodio sporco come deve essere, ma sincero.

Stallman a Milano e il problema di tracciare i processi digitaliIl software proprietario e' quello che fa le cose che vuole lui sui nostri computer.E' un male ?Bonolis al Poretcast: i telefoni creano mille mondi che esistono e non conosciamo, e non sappiamo come difendere i figli.Dove e' il male: nel telefono, nei mondi, nel non conoscerli ?E se tutto fosse solo una questione di semplificazione e trasparenza ? Di comunicare schiettamente ?Per info: gli organizzatori chiedono per esigenze eccezionali di portare la mascherina. Info su https://poul.org/2025/05/richard-stallman-2025/

The most prominent leaders in Free and Open Source Software (from Stallman to Torvalds) are regularly attacked, ostracized, or outright banned by Leftist Extremists. More from The Lunduke Journal: https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe

​​In September 2019, Richard Stallman, a prominent computer scientist and founder of the Free Software Foundation (FSF), resigned from both the Massachusetts Institute of Technology (MIT) and the FSF following controversial comments related to the Jeffrey Epstein case. Specifically, Stallman questioned the use of the term "sexual assault" concerning allegations against the late MIT professor Marvin Minsky, suggesting that the victim may have appeared "entirely willing." These remarks were widely criticized as insensitive and dismissive of the coercive circumstances surrounding Epstein's trafficking of minors.The backlash against Stallman's comments led to his immediate resignation from both institutions. However, in March 2021, he announced his return to the FSF's board of directors, a move that sparked renewed controversy and led to significant criticism from the open-source community. Organizations such as Mozilla and the Open Source Initiative opposed his reinstatement, citing concerns over his past behavior and statements.Leon Botstein, president of Bard College, engaged in a controversial relationship with Jeffrey Epstein, a convicted sex offender, by accepting donations and maintaining contact even after Epstein's 2008 conviction. Epstein contributed $75,000 and 66 laptops to Bard in 2011, and in 2016, he personally gave Botstein $150,000, which Botstein redirected to the college as part of his own $1 million donation. Botstein defended these actions by emphasizing his fundraising responsibilities and Bard's commitment to rehabilitation, stating, "We believe in rehabilitation."Despite knowing Epstein's criminal history, Botstein met with him over a dozen times to solicit further donations, raising ethical questions about engaging with disreputable donors. Botstein acknowledged Epstein's past but justified the interactions as part of his role in securing funding for the college, reflecting the complex dynamics between institutional fundraising and ethical considerations.to contact me:bobbycapucci@protonmail.com

​​In September 2019, Richard Stallman, a prominent computer scientist and founder of the Free Software Foundation (FSF), resigned from both the Massachusetts Institute of Technology (MIT) and the FSF following controversial comments related to the Jeffrey Epstein case. Specifically, Stallman questioned the use of the term "sexual assault" concerning allegations against the late MIT professor Marvin Minsky, suggesting that the victim may have appeared "entirely willing." These remarks were widely criticized as insensitive and dismissive of the coercive circumstances surrounding Epstein's trafficking of minors.The backlash against Stallman's comments led to his immediate resignation from both institutions. However, in March 2021, he announced his return to the FSF's board of directors, a move that sparked renewed controversy and led to significant criticism from the open-source community. Organizations such as Mozilla and the Open Source Initiative opposed his reinstatement, citing concerns over his past behavior and statements.Leon Botstein, president of Bard College, engaged in a controversial relationship with Jeffrey Epstein, a convicted sex offender, by accepting donations and maintaining contact even after Epstein's 2008 conviction. Epstein contributed $75,000 and 66 laptops to Bard in 2011, and in 2016, he personally gave Botstein $150,000, which Botstein redirected to the college as part of his own $1 million donation. Botstein defended these actions by emphasizing his fundraising responsibilities and Bard's commitment to rehabilitation, stating, "We believe in rehabilitation."Despite knowing Epstein's criminal history, Botstein met with him over a dozen times to solicit further donations, raising ethical questions about engaging with disreputable donors. Botstein acknowledged Epstein's past but justified the interactions as part of his role in securing funding for the college, reflecting the complex dynamics between institutional fundraising and ethical considerations.to contact me:bobbycapucci@protonmail.com

​​In September 2019, Richard Stallman, a prominent computer scientist and founder of the Free Software Foundation (FSF), resigned from both the Massachusetts Institute of Technology (MIT) and the FSF following controversial comments related to the Jeffrey Epstein case. Specifically, Stallman questioned the use of the term "sexual assault" concerning allegations against the late MIT professor Marvin Minsky, suggesting that the victim may have appeared "entirely willing." These remarks were widely criticized as insensitive and dismissive of the coercive circumstances surrounding Epstein's trafficking of minors.The backlash against Stallman's comments led to his immediate resignation from both institutions. However, in March 2021, he announced his return to the FSF's board of directors, a move that sparked renewed controversy and led to significant criticism from the open-source community. Organizations such as Mozilla and the Open Source Initiative opposed his reinstatement, citing concerns over his past behavior and statements.Leon Botstein, president of Bard College, engaged in a controversial relationship with Jeffrey Epstein, a convicted sex offender, by accepting donations and maintaining contact even after Epstein's 2008 conviction. Epstein contributed $75,000 and 66 laptops to Bard in 2011, and in 2016, he personally gave Botstein $150,000, which Botstein redirected to the college as part of his own $1 million donation. Botstein defended these actions by emphasizing his fundraising responsibilities and Bard's commitment to rehabilitation, stating, "We believe in rehabilitation."Despite knowing Epstein's criminal history, Botstein met with him over a dozen times to solicit further donations, raising ethical questions about engaging with disreputable donors. Botstein acknowledged Epstein's past but justified the interactions as part of his role in securing funding for the college, reflecting the complex dynamics between institutional fundraising and ethical considerations.to contact me:bobbycapucci@protonmail.comBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

Matt is back with another episode of Stay Ready The Podcast! On this episode is sits down with frequent guest and known Titans critic, Jared Stillman. They dive into the episode discussing the state of the Titans and Colts franchises, what should happen next and if it were right for Pat McAfee to call out the Colts for their lack of accountability. Listen in as the guys who are passionate about these teams try to figure out what when wrong and who can right the ship of both struggling franchises moving forward. Other topics they discuss include: Matt's funny interaction with Mike McDanielwhat Jared thinks of Ran Carthon and Brian Callahan Jared's time with Floyd Reese (former Titans GM) and what he learned about no bad days in footballMatt volunteering at Page High School this past seasonMatt's plans for playing next season and so much more! 

Warning: While this episode keeps things "PG", a few of the topics mentioned are deeply disturbing. Viewer discretion, as they say, is advised. More from The Lunduke Journal: https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe

Dunwoody College of Technology President Scott Stallman talks to F&C reporter Brian Johnson. Stallman discusses Dunwoody's history and future, efforts to improve diversity in the construction trades, the ongoing need for skilled labor, and other topics.

Döndük, hem de dönmek üzerine konuşarak! Eylül Görmüş ve Tuğçe Arslan Üçer, yeni sezonun ilk bölümünde "dönmek" meselesi üzerine söyleşiyor. Geri dönmek, eve dönmek, içe dönmek, kendine dönmek... Dönmenin pek çok farklı biçimini ve onlara eşlik eden duyguları didikliyor, akıl yürütüyoruz: pek tabii kitaplar ve filmlerden aldığımız ipuçları ile. Bölümde adı geçen tüm kitap ve filmlerin listesini ⁠⁠⁠⁠⁠⁠⁠⁠⁠@1kitap1film.us⁠⁠⁠⁠⁠⁠⁠⁠⁠ instagram hesabımızda bulabileceğinizi hatırlatalım. Bu bölüme sponsor olarak bizi destekleyen ⁠⁠⁠⁠⁠⁠⁠⁠⁠Doku Clinic⁠⁠⁠⁠⁠⁠⁠⁠⁠'e katkılarından ötürü sonsuz teşekkür ederiz. Podcast kapağı için seçtiğimiz Stallman eserinin de kendilerinin koleksiyonundan olduğunu belirtelim. Geri dönmüş olmak pek güzel - dileriz ki siz de bizi özlemişsinizdir!

2/9/2024 PODCAST Episodes #1171 - #1174 GUEST: Chris Saxman, Phill Kline, Jeff Clark, Seb Gorka, Peter McCullough, Dave Brat, Delois Stallman, Sheriff David Clarke, Steve Stern, Mallory Staples + YOUR CALLS! at 1-888-480-JOHN (5646) and GETTR Live! @jfradioshow #GodzillaOfTruth #TruckingTheTruth   Want more of today's show? Episode #1171 Trump Blows Out Haley in Virgin Islands 75%-25% Episode #1172 Jeff Clark, Seb Gorka and Dr. Peter McCullough Unplugged Episode #1173 Janet Yellen Spews Out Lies, Spin and Nonsense Episode #1174 Callers of The Day, Sheriff Clarke, Delois Stallman and Steve Stern   https://johnfredericksradio.libsyn.com/

I talked to Aaron van WIrdum about his new book "The Genesis Book" which covers both the economic and technological origins of Bitcoin going back all the way back to Hayek and Stallman.

Step into the world of Sheriff Bo Stallman, a true local hero with a deep connection to Brazoria County. Born and raised here, Bo's journey started at Danbury High School before he proudly served in the United States Marine Corps. Returning to Texas, he dedicated almost a decade to protecting our roads as a Texas State Trooper, continually enhancing his skills with a Masters' Degree in Criminal Justice from Sam Houston State University. In 2013, Bo took a pivotal role as a Criminal Investigator with the Brazoria County District Attorney's Office. Our conversation with Sheriff Stallman covers more than just his professional journey – we touch on family, the crucial role of a sheriff, and how the region's growth impacts the lives of Brazoria County residents. Get a firsthand account of the positive changes Bo has spearheaded since taking office in 2021 and gain valuable insights into the dynamics of law enforcement and community service in our area. Follow Jon & Mike below: Jon and Mike on Instagram @curiositywithjonandmike Follow Jon and Mike on Facebook @curiositywithjonandmike Subscribe to Jon and Mike's YouTube channel for more content: https://www.youtube.com/channel/UCbXt...

Welcome, to episode #81 of The Exploring Antinatalism Podcast! A podcast, showcasing the wide range of perspectives & ideas throughout Antinatalism as it exists today, through interviews with Antinatalist & non-Antinatalist thinkers & creators of all kinds - now running 5 years strong! I'm your host, Amanda Sukenick, and today, I'm speaking with legendary founder of the Free Software Foundation, developer of the GNU Project, winner of the MacArthur Fellowship Genius Grant, and author of the 2012 article, Why it is important to have few or no children – Richard Stallman! Richard Stallman and I hope that this episode will be watched HERE!: https://www.exploringantinatalism.com/episodes/ep81/14 min video about the GNU project: https://www.fsf.org/blogs/rms/20140407-geneva-tedx-talk-free-software-free-society/https://www.fsf.org/https://www.gnu.org/https://stallman.org/https://stallman.org/articles/children.htmlhttps://stallman.org/articles/nonexistence-not-good-or-bad.html*Dr. Stallman was concerned here lest it appear he accepts singular "they",but couldn't use his gender-neutral singular pronouns in this point.See https://stallman.org/articles/genderless-pronouns.html.

11/08/2023 PODCAST Episodes #1005 - #1007 GUEST: Mike Watson, Chris Paxman, Ashley Hayek, Nicole Tsai, Sheriff J.D. “Danny” Diggs, Ryan McDougle, DeLois Stallman, Matt Strickland + YOUR CALLS! at 1-888-480-JOHN (5646) and GETTR Live! @jfradioshow #GodzillaOfTruth #TruckingTheTruth   Want more of today's show? Episode #1005 Ashley Hayek At The Tip Of The Spear-Building A Real Mail In Ballot Plan For MAGA Episode #1006 Mike Watson, Danny Diggs Break Down VA Elections Episode #1007 JF, Mike Watson, Ryan McDougle And Delois Stallman-What's The Plan Now?   https://johnfredericksradio.libsyn.com/

In this episode Crawlspace Media's Tim Pilleri and Lance Reenstierna speak with Jenn Macphee and Katie Wilshire about the unsolved murder of Jenn's mom Julianna Stallman from Butte, Montana in 1994. Main Theme by Kevin Macleod. Check out his work at https://incompetech.com/. Additional music by David Williams. See his work at http://williamsflutes.com. Sources: https://www.facebook.com/justiceforJS https://nbcmontana.com/news/local/homicide-cold-case-still-unsolved-in-butte https://omny.fm/shows/impact-statement/the-unsolved-murder-of-julianne-stallman https://billingsgazette.com/news/state-and-regional/montana/investigator-probes--year-old-murder/article_7d33a134-028d-5da9-a2e3-93c8a4234188.html Follow Missing: TikTok: https://www.tiktok.com/@missingcsm Twitter: https://twitter.com/MissingCSM FB: https://www.facebook.com/MissingCSM IG: https://www.instagram.com/MissingCSM/ Check out our entire network at http://crawlspace-media.com/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Richard Matthew Stallman leads the Free Software Movement, which shows how the usual non-free software subjects users to the unjust power of its developers, plus their spying and manipulation, and campaigns to replace it with free (freedom-respecting) software. Born in 1953, Stallman graduated Harvard in 1974 in physics. He worked at the MIT Artificial Intelligence Lab from 1971 to 1984, developing system software including the first extensible text editor Emacs (1976), plus the AI technique of dependency-directed backtracking, also known as truth maintenance (1975). In 1983 Stallman launched the Free Software Movement by announcing the project to develop the GNU operating system, planned to consist entirely of free software. Stallman began working on GNU on January 5, 1984, resigning from MIT employment in order to do so. In October 1985 he established the Free Software Foundation. Stallman invented the concept of copyleft, "Change it and redistribute it but don't strip off this freedom," and wrote (with lawyers) the GNU General Public License, which implements copyleft. This inspired Creative Commons. Stallman personally developed a number of widely used software components of the GNU system: the GNU Compiler Collection, the GNU symbolic debugger (gdb), GNU Emacs, and various others. The GNU/Linux system, which is a variant of GNU that also contains the kernel Linux developed by Linus Torvalds, is used in tens or hundreds of millions of computers. Alas, people often call the system "Linux", giving the GNU Project none of the credit. Their versions of GNU/Linux often disregard the ideas of freedom which make free software important, and even include nonfree software in those systems. Nowadays, Stallman focuses on political advocacy for free software and its ethical ideas. He spends most of the year travelling to speak on topics such as "Free Software And Your Freedom" and "Copyright vs Community in the Age of the Computer Networks". Another topic is "A Free Digital Society", which treats several different threats to the freedom of computer users today. In 1999, Stallman called for development of a free on-line encyclopedia through inviting the public to contribute articles. This idea helped inspire Wikipedia. Stallman was a Visiting Scientist at MIT from 1991 (approximately) to 2019. Free Software, Free Society is Stallman's book of essays. His semiautobiography, Free as in Freedom, provides further biographical information. Original video ⁠here⁠⁠ Full Wikipedia entry ⁠here⁠ Richard Stallman's books ⁠here --- Support this podcast: https://podcasters.spotify.com/pod/show/theunadulteratedintellect/support

Dans cet épisode estival Guillaume, Emmanuel et Arnaud parcourent les nouvelles du début d'été. Du Java, du Rust, du Go du coté des langages, du Micronaut, du Quarkus pour les frameworks, mais aussi du WebGPU, de l'agilité, du DDD, des sondages, de nombreux outils et surtout de l'intelligence artificielle à toutes les sauces (dans les bases de données, dans les voitures…). Enregistré le 21 juillet 2023 Téléchargement de l'épisode LesCastCodeurs-Episode-298.mp3 News Langages La release candidate de Go 1.21 supporte WASM et WASI nativement https://go.dev/blog/go1.21rc StringBuilder ou contatenation de String https://reneschwietzke.de/java/the-stringbuilder-advise-is-dead-or-isnt-it.html StringBuilder était la recommendation ca cela créait moins d'objects notamment. Mais la JVM a évolué et le compilateur ou JIT remplace cela par du code efficace Quelques petites exceptions le code froid (e.g. startup time) qui est encore interprété peut beneficier de StringBuilder autre cas, la concatenation dans des boucles où le JIT ne pourrait peut etre pas optimiser le StringBuilder “fluid” est plus efficace (inliné?) ces regles ne changement pas si des objects sont stringifié pour etre concaténés GPT 4 pas une revolution https://thealgorithmicbridge.substack.com/p/gpt-4s-secret-has-been-revealed rumeur ca beaucou de secret pas u modele a 1 trillion de parametres maus 8 a 220 Milliards combinés intelligeament les chercheurs attendaient un breakthrough amis c'est une envolution et pas particulierement nouveau methode deja implem,entee par des cherchers chez google (maintenant chez ooenai ils ont retarde la competition avec ces rumeurs de breakthrough amis 8 LLaMA peut peut etre rivaliser avec GPT4 Le blog Open Source de Google propose un article sur 5 mythes ou non sur l'apprentissage et l'utilisation de Rust https://opensource.googleblog.com/2023/06/rust-fact-vs-fiction-5-insights-from-googles-rust-journey-2022.html Il faut plus de 6 mois pour apprendre Rust : plutôt faux; quelques semaines à 3-4 mois max Le compilateur Rust est pas aussi rapide qu'on le souhaiterait — vrai ! Le code unsafe et l'interop sont les plus gros challanges — faux, c'est plutôt les macros, l'owernship/borrowing, et la programmation asynchrone Rust fournit des messages d'erreur de compilation géniaux — vrai Le code Rust est de haute qualité — vrai InfoQ sort un nouveau guide sur le Pattern Matching pour le switch de Java https://www.infoq.com/articles/pattern-matching-for-switch/ Le pattern matching supporte tous les types de référence L'article parle du cas de la valeur null L'utilisation des patterns “guarded” avec le mot clé when L'importance de l'ordre des cases Le pattern matching peut être utilisé aussi avec le default des switchs Le scope des variables du pattern Un seul pattern par case label Un seul case match-all dans un bloc switch L'exhaustivité de la couverture des types L'utilisation des generics La gestion d'erreur avec MatchException Librairies Sortie de Micronaut 4 https://micronaut.io/2023/07/14/micronaut-framework-4-0-0-released/ Langage minimal : Java 17, Groovy 4 et Kotlin 1.8 Support de la dernière version de GraalVM Utilisation des GraalVM Reachability Metadata Repository pour faciliter l'utilisation de Native Image Gradle 8 Nouveau Expression Language, à la compilation, pas possible au runtime (pour des raisons de sécurité et de support de pré-compilation) Support des Virtual Threads Nouvelle couche HTTP, éliminant les stack frames réactives quand on n'utilise pas le mode réactif Support expérimental de IO Uring et HTTP/3 Des filtres basés sur les annotations Le HTTP Client utilise maintenant le Java HTTP Client Génération de client et de serveur en Micronaut à partir de fichier OpenAPI L'utilisation YAML n'utilise plus la dépendance SnakeYAML (qui avait des problèmes de sécurité) Transition vers Jackarta terminé Et plein d'autres mises à jour de modules Couverture par InfoQ https://www.infoq.com/news/2023/07/micronaut-brings-virtual-thread/ Quarkus 3.2 et LTS https://quarkus.io/blog/quarkus-3-2-0-final-released/ https://quarkus.io/blog/quarkus-3-1-0-final-released/ https://quarkus.io/blog/lts-releases/ Infrastructure Red Hat partage les sources de sa distribution au travers de son Customer Portal, et impacte la communauté qui se base dessus https://almalinux.org/blog/impact-of-rhel-changes/ RedHat a annoncé un autre changement massif qui affecte tous les rebuilds et forks de Red Hat Enterprise Linux. À l'avenir, Red Hat publiera uniquement le code source pour les RHEL RPMs derrière leur portail client. Comme tous les clones de RHEL dépendent des sources publiées, cela perturbe encore une fois l'ensemble de l'écosystème Red Hat. Une analyse du choix de red hat sur la distribution du code source de rhel https://dissociatedpress.net/2023/06/24/red-hat-and-the-clone-wars/ Une reponse de red hat aux feux démarrés par l'annonce de la non distribution des sources de RHEL en public https://www.redhat.com/en/blog/red-hats-commitment-open-source-response-gitcentosorg-changes et un lien vers une de ces feux d'une personne proheminente dans la communauté Ansible https://www.jeffgeerling.com/blog/2023/im-done-red-hat-enterprise-linux Oracle demande a garder un Linux ouvert et gratuit https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/ Suite à l'annonce d'IBM/RedHat, Oracle demande à garder Linux ouvert et gratuit IBM ne veut pas publier le code de RHEL car elle doit payer ses ingénieurs Alors que RedHat a pu maintenir son modèle économique durante des années L'article revient sur CentOS qu'IBM “a tué” en 2020 Oracle continue ses éfforts de rendre Linux ouvert et libre Oracle Linux continuera à être compatible avec RHEL jusqu'à la version 9.2, après ça sera compliqué de maintenir une comptabilité Oracle embauche des dev Linux Oracle demande à IBM de récupérer le downstream d'Oracle et de le distribuer SUSE forke RHEL https://www.suse.com/news/SUSE-Preserves-Choice-in-Enterprise-Linux/ SUSE est la société derrière Rancher, NeuVector, et SUSE Linux Enterprise (SLE) Annonce un fork de RHEL $10M d'investissement dans le projet sur les prochaines années Compatibilité assurée de RHEL et CentOS Web Google revent sont service de nom de domaine a Squarespace https://www.reddit.com/r/webdev/comments/14agag3/squarespace_acquires_google_domains/ et c'était pas gratuit donc on n'est pas censé etre le produit :wink: Squarespace est une entreprise américaine spécialisée dans la création de site internet Squarespace est un revendeur de Google Workspace depuis longtemps La vente devrait se finaliser en Q3 2023 Petite introduction à WebGPU en français https://blog.octo.com/connaissez-vous-webgpu/ Data Avec la mode des Large Language Models, on parle de plus en plus de bases de données vectorielles, pour stocker des “embeddings” (des vecteurs de nombre flottant représentant sémantiquement du texte, ou même des images). Un article explique que les Vecteurs sont le nouveau JSON dans les bases relationnelles comme PostgreSQL https://jkatz05.com/post/postgres/vectors-json-postgresql/ L'article parle en particulier de l'extension pgVector qui est une extension pour PostgreSQL pour rajouter le support des vectors comme type de colonne https://github.com/pgvector/pgvector Google Cloud annonce justement l'intégration de cette extension vectorielle à CloudSQL pour PostgreSQL et à AlloyDB pour PostgreSQL https://cloud.google.com/blog/products/databases/announcing-vector-support-in-postgresql-services-to-power-ai-enabled-applications Il y a également une vidéo, un notebook Colab, et une article plus détaillé techniquement utilisant LangChain https://cloud.google.com/blog/products/databases/using-pgvector-llms-and-langchain-with-google-cloud-databases Mais on voit aussi également Elastic améliorer Lucene pour utiliser le support des instructions SIMD pour accélérer les calculs vectoriels (produit scalaire, distance euclidienne, similarité cosinus) https://www.elastic.co/fr/blog/accelerating-vector-search-simd-instructions Outillage Le sondage de StackOverflow 2023 https://survey.stackoverflow.co/2023/ L'enquête a été réalisée auprès de 90 000 développeurs dans 185 pays. Les développeurs sont plus nombreux (+2%) que l'an dernier à travailler sur site (16% sur site, 41% remote, 42% hybrid) Les développeurs sont également de plus en plus nombreux à utiliser des outils d'intelligence artificielle, avec 70 % d'entre eux déclarant les utiliser (44%) ou prévoyant de les utiliser (25) dans leur travail. Les langages de programmation les plus populaires sont toujours JavaScript, Python et HTML/CSS. Les frameworks web les plus populaires sont Node, React, JQuery. Les bases de données les plus populaires sont PostgreSQL, MySQL, et SQLite. Les systèmes d'exploitation les plus populaires sont Windows puis macOS et Linux. Les IDE les plus populaires sont Visual Studio Code, Visual Studio et IDEA IntelliJ. Les différents types de déplacement dans Vim https://www.barbarianmeetscoding.com/boost-your-coding-fu-with-vscode-and-vim/moving-blazingly-fast-with-the-core-vim-motions/ JetBrains se mets aussi à la mode des assistants IA dans l'IDE https://blog.jetbrains.com/idea/2023/06/ai-assistant-in-jetbrains-ides/ une intégration avec OpenAI mais aussi de plus petits LLMs spécifiques à JetBrains un chat intégré pour discuter avec l'assistant, puis la possibilité d'intégrer les snippets de code là où se trouve le curseur possibilité de sélectionner du code et de demander à l'assistant d'expliquer ce que ce bout de code fait, mais aussi de suggérer un refactoring, ou de régler les problèmes potentiels on peut demander à générer la JavaDoc d'une méthode, d'une classe, etc, ou à suggérer un nom de méthode (en fonction de son contenu) génération de message de commit il faut avoir un compte JetBrains AI pour y avoir accès Des commandes macOS plus ou moins connues https://saurabhs.org/advanced-macos-commands caffeinate — pour garder le mac éveillé pbcopy / pbpaste — pour interagir avec le clipboard networkQuality — pour mesurer la rapidité de l'accès à internet sips — pour manipuler / redimensionner des images textutil — pour covertir des fichers word, texte, HTML screencapture — pour faire un screenshot say — pour donner une voix à vos commandes Le sondage de la communauté ArgoCD https://blog.argoproj.io/cncf-argo-cd-rollouts-2023-user-survey-results-514aa21c21df Un client d'API open-source et cross-platform pour GraphQL, REST, WebSockets, Server-sent events et gRPC https://github.com/Kong/insomnia Architecture Moderniser l'architecture avec la decouverte via le domain driven discovery https://www.infoq.com/articles/architecture-modernization-domain-driven-discovery/?utm_source=twitter&utm_medium=link&utm_campaign=calendar Un article très détaillé pour moderniser son architecture en utilisant une approche Domain-Driven Discovery qui se fait en 5 étapes: Encadrer le problème – Clarifier le problème que vous résolvez, les personnes touchées, les résultats souhaités et les contraintes de solution. Analyser l'état actuel – Explorer les processus opérationnels et l'architecture des systèmes existants afin d'établir une base de référence pour l'amélioration. Explorer l'état futur – Concevoir une architecture modernisée fondée sur des contextes délimités, établir des priorités stratégiques, évaluer les options et créer des solutions pour l'état futur. Créer une feuille de route – Créer un plan pour moderniser l'architecture au fil du temps en fonction des flux de travail ou des résultats souhaités. Récemment, Sfeir a lancé son blog de développement sur https://www.sfeir.dev/ plein d'articles techniques sur de nombreux thèmes : front, back, cloud, data, AI/ML, mobile aussi des tendances, des success stories par exemple dans les derniers articles : on parle d'Alan Turing, du Local Storage en Javascript, des la préparation de certifications React, l'impact de la cybersécurité sur le cloud Demis Hassabis annonce travailler sur une IA nommée Gemini qui dépassera ChatGPT https://www.wired.com/story/google-deepmind-demis-hassabis-chatgpt/ Demis Hassabis CEO de Google DeepMind créateur de AlphaGOet AlphaFold Travaille sur une IA nommé Gemini qui dépasserait ChatGPT de OpenAI Similair à GPT-4 mais avec des techniques issues de AlphaGO Encore en developpement, va prendre encore plusieurs mois Un remplaçant a Bard? Méthodologies Approcher l'agilité par les traumatismes (de developement) passés des individus https://www.infoq.com/articles/trauma-informed-agile/?utm_campaign=infoq_content&utm_source=twitter&utm_medium=feed&utm_term=culture-methods Nous subissons tous un traumatisme du développement qui rend difficile la collaboration avec d'autres - une partie cruciale du travail dans le développement de logiciels agiles. Diriger d'une manière tenant compte des traumatismes n'est pas pratiquer la psychothérapie non sollicitée, et ne justifie pas les comportements destructeurs sans les aborder. Être plus sensible aux traumatismes dans votre leadership peut aider tout le monde à agir de façon plus mature et plus disponible sur le plan cognitif, surtout dans des situations émotionnellement difficiles. Dans les milieux de travail tenant compte des traumatismes, les gens accordent plus d'attention à leur état physique et émotionnel. Ils s'appuient aussi davantage sur le pouvoir de l'intention, fixent des objectifs d'une manière moins manipulatrice et sont capables d'être empathiques sans s'approprier les problèmes des autres. Loi, société et organisation Mercedes va rajouter de l'intelligence artificielle dans ses voitures https://azure.microsoft.com/en-us/blog/mercedes-benz-enhances-drivers-experience-with-azure-openai-service/ Programme béta test de 3 mois pour le moment Assistance vocale “Hey Mercedes” Permet de discuter avec la voiture pour trouver son chemin, concocter une recette, ou avoir tout simplement des discussions Ils travaillent sur des plugin pour reserver un resto, acheter des tickets de cinéma Free software vs Open Source dans le contexte de l'intelligence artificielle par Sacha Labourey https://medium.com/@sachalabourey/ai-free-software-is-essential-to-save-humanity-86b08c3d4777 on parle beaucoup d'AI et d'open source mais il manque la dimension de controle des utilisateurs finaux Stallman a crée la FSF par peur de la notion d'humain augmenté par des logiciels qui sont controllés par d'autres (implants dans le cerveau etc) d'ou la GPL et sa viralité qui propage la capacité a voir et modifier le conde que l'on fait tourner dans le debat AI, ce n'est pas seulement open source (casser oligopolie) mais aissu le free software qui est en jeu La folie du Cyber Resilience Act (CRA) europeen https://news.apache.org/foundation/entry/save-open-source-the-impending-tragedy-of-the-cyber-resilience-act Au sein de l'UE, la loi sur la cyber-résilience (CRA) fait maintenant son chemin à travers les processus législatifs (et doit faire l'objet d'un vote clé le 19 juillet 2023). Cette loi s'appliquera à un large éventail de logiciels (et de matériel avec logiciel intégré) dans l'UE. L'intention de ce règlement est bonne (et sans doute attendue depuis longtemps) : rendre le logiciel beaucoup plus sûr. Le CRA a une approche binaire: oui/non et considère tout le monde de la même manière Le CRA réglementerait les projets à source ouverte à moins qu'ils n'aient « un modèle de développement entièrement décentralisé ». Mais les modèles OSS sont de complexes mélanges de pur OSS et éditeurs de logiciels les entreprises commerciales et les projets open source devront être beaucoup plus prudents quant à ce que les participants peuvent travailler sur le code, quel financement ils prennent, et quels correctifs ils peuvent accepter. Certaines des obligations sont pratiquement impossibles à respecter, par exemple l'obligation de « livrer un produit sans vulnérabilités exploitables connues ». Le CRA exige la divulgation de vulnérabilités graves non corrigées et exploitées à l'ENISA (une institution de l'UE) dans un délai mesuré en heures, avant qu'elles ne soient corrigées. (complètement opposé aux bonnes pratiques de sécu) Une fois de plus une bonne idée à l'origine mais très mal implémentée qui risque de faire beaucoup de dommages Octave Klaba, avec Miro, son frère, et la Caisse des Dépôts, finalisent la création de Synfonium qui va maintenant racheter 100% de Qwant et 100% fe Shadow. Synfonium est détenue à 75% par Jezby Venture & Deep Code et à 25% par la CDC. https://twitter.com/i/web/status/1673555414938427392 L'un de rôles de Synfonium est de créer la masse critique des utilisateurs et des clients B2C & B2B qui vont pouvoir utiliser tous ces services gratuits et payants Vous y retrouverez le moteur de recherche, les services gratuits, la suite collaborative, le social login, mais aussi les services de nos partenaires tech. Le but est de créer une plateforme dans le Cloud SaaS EU qui respectent nos valeurs et nos lois européennes Yann LeCun : «L'intelligence artificielle va amplifier l'intelligence humaine» https://www.europe1.fr/emissions/linterview-politique-dimitri-pavlenko/yann-lecun-li[…]gence-artificielle-va-amplifier-lintelligence-humaine-4189120 Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 2-3 septembre 2023 : SRE France SummerCamp - Chambéry (France) 6 septembre 2023 : Cloud Alpes - Lyon (France) 8 septembre 2023 : JUG Summer Camp - La Rochelle (France) 14 septembre 2023 : Cloud Sud - Remote / Toulouse (France) 18 septembre 2023 : Agile Tour Montpellier - Montpellier (France) 19-20 septembre 2023 : Agile en Seine - Paris (France) 19 septembre 2023 : Salon de la Data Nantes - Nantes (France) & Online 21-22 septembre 2023 : API Platform Conference - Lille (France) & Online 22 septembre 2023 : Agile Tour Sophia Antipolis - Valbonne (France) 25-26 septembre 2023 : BIG DATA & AI PARIS 2023 - Paris (France) 28-30 septembre 2023 : Paris Web - Paris (France) 2-6 octobre 2023 : Devoxx Belgium - Antwerp (Belgium) 6 octobre 2023 : DevFest Perros-Guirec - Perros-Guirec (France) 10 octobre 2023 : ParisTestConf - Paris (France) 11-13 octobre 2023 : Devoxx Morocco - Agadir (Morocco) 12 octobre 2023 : Cloud Nord - Lille (France) 12-13 octobre 2023 : Volcamp 2023 - Clermont-Ferrand (France) 12-13 octobre 2023 : Forum PHP 2023 - Marne-la-Vallée (France) 19-20 octobre 2023 : DevFest Nantes - Nantes (France) 19-20 octobre 2023 : Agile Tour Rennes - Rennes (France) 26 octobre 2023 : Codeurs en Seine - Rouen (France) 25-27 octobre 2023 : ScalaIO - Paris (France) 26-27 octobre 2023 : Agile Tour Bordeaux - Bordeaux (France) 26-29 octobre 2023 : SoCraTes-FR - Orange (France) 10 novembre 2023 : BDX I/O - Bordeaux (France) 15 novembre 2023 : DevFest Strasbourg - Strasbourg (France) 16 novembre 2023 : DevFest Toulouse - Toulouse (France) 23 novembre 2023 : DevOps D-Day #8 - Marseille (France) 30 novembre 2023 : PrestaShop Developer Conference - Paris (France) 30 novembre 2023 : WHO run the Tech - Rennes (France) 6-7 décembre 2023 : Open Source Experience - Paris (France) 7 décembre 2023 : Agile Tour Aix-Marseille - Gardanne (France) 8 décembre 2023 : DevFest Dijon - Dijon (France) 7-8 décembre 2023 : TechRocks Summit - Paris (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via twitter https://twitter.com/lescastcodeurs Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Of all the wedding vendors I know, I've known Cayna the longest. Our families have been friends for over 30 years, and I FINALLY got to sit down with her and talk about her passion for floral design and coordination. You'll hear her tips for maximizing your floral budget and what she sees as the standard for a good centerpiece, and she'll tell you that it's okay to talk about your ideas.Connect with Cayna on her website, Facebook and Instagram.E2iDesign sponsors this episode. Find them on their website or social media @e2idesign.Join me in the fight to find a world without Alzheimer's Disease. Start or join a walk team TODAY at ALZ.org. Hosted on Acast. See acast.com/privacy for more information.

Get snackin' on some Pixel Pizza as you hear from Chris Stallman, the Art Lead at Young Horses. His strikingly funny and weird style has brought the hit games Octodad: Dadliest Catch and Bugsnax to life! Chris tells us how he makes his characters so distinctive, working game design into character design, and what food he ate in the Bugsnax research process

ADVERTENCIA: Durante la grabación de este episodio tuvimos dificultades técnicas que crearon unos ruidos que a veces hace imposible escuchar lo que dicen los hosts. Pedimos disculpas por las molestias. Episodio 200. El Pinta'ó, el chino pega'o directo, La argentina y Voldemort hace mucho tiempo que no están en empresas, tienen una serie nueva de obsesiones muy caras todas y el asunto es que ahora esta gente se desquició y mira… Poco enchufe pa mucho hueco. Olé! ✅ Follow Up Hoy extrañe a Jorge Feedly añade Mastodon Sharing a la versión web luego de escuchar el podcast Touchscreen MacBooks‽ https://www.macrumors.com/2023/01/11/touchscreen-macs-report/ El eero6 funciona igual que el viejo Google WiFi de Jorge

First up in the news, Stallman goes manual on C, DNF5 arrives in Fedora, LibreOffice gets fumigated, GNOME comes into its Shell, they have put hair in the Blender, Avast buys your cookies, and Intel fogs the processor market; In security and privacy, we have multi-stage malware, website leaks, and shell attacks; Then in our Wanderings, Norbert is cutting corners, Moss tries a different mint, Joe keeps modding, and Bill fixes a broken Arch …again. In our Innards section, Ransomware goes to school; And finally, the feedback and a couple of suggestions Download

Following Jesus | Bob Stallman by Northwest University

Scott Stallman is the chief academic and student affairs officer for Dunwoody College of Technology. Dunwoody Technology College Links https://dunwoody.edu/ https://www.linkedin.com/school/dunwoody-college-of-technology/ https://www.youtube.com/user/DunwoodyCollege https://www.instagram.com/dunwoodycollege/ https://www.facebook.com/dunwoodycollege/ https://twitter.com/dunwoodycollege https://www.tiktok.com/@dunwoodycollege ABOUT PODCAST Skill Stadium podcast is the voice of the skilled trades. Every Tuesday morning, we feature guests from all over the world with the following backgrounds: Business Owners Hiring Managers Skilled Trades Professionals Trade School Administrators Career Coaches Skilled Trades Influencers The purpose of the podcast is to share stories, career advice, and job opportunities in the skilled trades. You are invited every week to listen in on a conversation with people who are passionate about the skilled trades. You get the information you cannot google, from real people doing the work.

Thank you for tuning in to episode 21 of the Cheap Flights and Cornbread Podcast featuring special guest Gabe Stallman of Ampevene! The Cheap Flights and Cornbread Podcast with Frankie Cavone and Brett Porter airs every single week live on the Mirth Films YouTube and Twitch channel featuring a variety of guests while covering everything happening in the live music/entertainment world. You can also listen to the Cheap Flights and Cornbread Podcast on iTunes and Spotify. Mirth Films: Website: https://mirth-films.com/ Facebook: https://www.facebook.com/mirthfilms/ Instagram: https://www.instagram.com/mirth_films/ Twitter: https://twitter.com/mirth_films

Highlights from their conversation include:Chris' entry into venture (1:27)Fontinalis' start and current investments (4:58)Automotive's impact on Fontinalis (8:56)Investing in hardware versus software (11:33)Autonomous vehicles (17:02)EVs and commercial applications (21:30)eCommerce enablement (23:11)The of role Spack (24:29)Advice for founders (27:42)Rapid fire round: COVID breaking open the heartland as a place to build a big business, most important daily habit, outlook for Michigan football (30:48)Dynamo is a VC firm led by supply chain and mobility specialists that focus on seed stage, enterprise startups. Find out more at: https://www.dynamo.vc/.

We go live to the border, get updates from NYC, and discuss the rise of Elon Musks 'Skynet' like army Our guests are: Ben Bergquam, Allen West, Andrew Giuliani, Delois Stallman, Joe Allen Stay ahead of the censors - Join us warroom.org/join Aired On: 2/01/2022 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews 

We discuss the border, truckers versus the mandates, the economy, and more.  Our guests are: Ben Bergquam, Dr. Peter Navarro, DeLois Stallman, Karoline Leavitt, Cynthia Hughes Stay ahead of the censors - Join us warroom.org/join Aired On: 1/31/2022 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews 

We discuss the radical DA in NYC and why he should be removed, Pennsylvania, and more.  Our guests are: Ben Bergquam, Rudy Giuliani, Bernie Kerik, Darren Beattie, Delois Stallman, Maureen Murphy Stay ahead of the censors - Join us warroom.org/join Aired On: 1/31/2022 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews 

We discuss polling, populism, and what is taking place in Mexico.   Our guests are: Boris Epshteyn, Josh Mandel, Todd Bensman, DeLois Stallman Stay ahead of the censors - Join us warroom.org/join Aired On: 1/17/2022 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews 

We honor the people who have been leading the charge against the Biden regime, the deplorable's.  Our guests are: Aimee Villella McBride, Bianca Gracia, Quisha King, Tina Peters, DeLois Stallman Stay ahead of the censors - Join us warroom.org/join Aired On: 12/31/2021 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews 

We discuss the victory for MAGA In Virginia and across the states, and the national walk out against vaccine mandates. Our guests are: Dr. Peter Navarro, Patti Lyman, Aimee Villella, DeLois Stallman, Stephanie Locricchio, Vernon Jones, Dr. Naomi Wolf Stay ahead of the censors - Join us warroom.org/join Aired On: 11/03/2021 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews

We discuss the ongoing battle amongst the school board and parents in Virginia as the election inches closer, and transhumanism. Our guests are: Cpt. Maureen Bannon, Elizabeth Schultz, Patti Lyman, DeLois Stallman, Tiffany Polifko, Boris Epshteyn Stay ahead of the censors - Join us warroom.org/join Aired On: 11/01/2021 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews

We discuss the ongoing battle amongst the school board, election board, and parents in Virginia.  Our guests are: Jack Posobiec, Oscar Ramirez, Richard Baris, Pattie Lyman, DeLois Stallman, Bryanna Altman Stay ahead of the censors - Join us warroom.org/join Aired On: 10/30/2021 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews

We go live from the front lines in Loudoun County VA. Our guests are: Tiffany Polifko, Elizabeth Schultz, Scott Mineo, Joe Mobley, DeLois Stallman, Mendez, Elizabeth L. Schultz Stay ahead of the censors - Join us warroom.org/join Aired On: 10/29/2021 Watch: On the Web: http://www.warroom.org On Podcast: http://warroom.ctcin.bio On TV: PlutoTV Channel 240, Dish Channel 219, Roku, Apple TV, FireTV or on https://AmericasVoice.news. #news #politics #realnews

Chris walks us through the history that led to Fontinalis Partners launching one of the very first thematic VC funds specifically targeted on mobility and “Reinventing the way people and goods move”, how the broader mobility ecosystem has evolved over the past 12 years since launching the fund and what that has meant to Fontinalis's thematic strategy, why sector-focus and thematic specialization in venture capital is important to compete in the current VC asset class, why the automotive industry specifically is somewhat unrecognizable from the decades past, and finally his thoughts on “What's Hot and What's Hype” within the mobility ecosystem right now.

We rely on technology more and more, and yet it is one of those most expensive and shortest lifetime investments we can make. In this episode, Im going to explain how you can save mega-bucks by changing how you think about technology, and specifically how you can use the Linux operating system and open source software to get advantages most never see. And I promise I wont get technical and geeky either.

We rely on technology more and more, and yet it is one of those most expensive and shortest lifetime investments we can make. In this episode, Im going to explain how you can save mega-bucks by changing how you think about technology, and specifically how you can use the Linux operating system and open source software to get advantages most never see. And I promise I wont get technical and geeky either.

We rely on technology more and more, and yet it is one of those most expensive and shortest lifetime investments we can make. In this episode, Im going to explain how you can save mega-bucks by changing how you think about technology, and specifically how you can use the Linux operating system and open source software to get advantages most never see. And I promise I wont get technical and geeky either.

We rely on technology more and more, and yet it is one of those most expensive and shortest lifetime investments we can make. In this episode, Im going to explain how you can save mega-bucks by changing how you think about technology, and specifically how you can use the Linux operating system and open source software to get advantages most never see. And I promise I wont get technical and geeky either.