Podcasts about Manta

The Coaster Radio Listener Meetup is OFFICIALLY in the books, and it did not disappoint. Mike and EB take you inside their Sunday at SeaWorld Orlando for the 2026 meetup — Fantastic fans, 11 miles of walking, rain-soaked roller coasters, and a penguin habitat that was a brisk 28 degrees. (They were already wet. It was not fun.)   Ride reviews include Manta, Penguin Trek, Kraken, Mako, Ice Breaker, Expedition Odyssey, and the one everyone was waiting for — Pipeline: The Surf Coaster, which may have just redefined what airtime even means.   Plus: the guys sit down with Banks Lee from SeaWorld's marketing team for an exclusive interview that ends with a riveting riddle, a capitivating clue, and a nugget of breaking news that no one else has. Coaster royalty Taylor Bybee crashes the happy hour. And Bob the Lobster calls in from the deep.   Also on this week's show: Nebraska gets its tallest roller coaster ever (it's 70 feet, and yes, that's a big deal there), Rock N Roller Coaster says goodbye to Aerosmith as the Muppets move in, Fast & Furious: Hollywood Drift testing footage gets Mike to completely change his tune, and the guys review the animated POV of the new RMC Raptor coming to Myrtle Beach.

Tracklist and more info: https://www.bestdrumandbass.com/podcast582/We are back with another huge episode! Not only are we still pushing the brand new CROO EP that is climbing up the charts today (almost to top 50!), but PashaRav is in the guest mix to celebrate the brand new Paperfunk release that we are both a part of that dropped today. So lock it in, and lets rock it out!Subscribe to the podcast: bestdnb.com/podcast  Croo - Juice EP [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd135/Supported by: Neonlight, MNDSCP, Figure, Bad Ace, Contam, Stonx, Manta, Klone, Akrom, Nuvertal, Drone, Nox, Subconscious BSC, MYGR, Michael Paino, Critical Control Point, Ollie Duracell, fibednb, Psidream, Stonerice, Johannes Soppa, Sinuous Recordings, Affirmation, Impex, Hijk, Malasuerte, Korax, Drbblz, BassDrive.com, Lennart Hoffmann, Diode, Crackindomes, Dip Vertigo, Bytecode, dela Moon, Pish Posh, Metric, ESKR, Insom, Scout 22, Tschul, Bons, The d34d b34t, 360 Degrees, CRS, X.morph, Autopsy, The Smell of Males, 9thwave, MV, J. Augustus, AL SEEN, ARI-ON, Needlenose, Lee UHF, Gigan and more!

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

Compra el libro Antihábitos de Borja GirónDuermes mal por estoDormir bien es el mayor secreto de productividad Necesitas entre 7:30 y 8:30Depende de edad y hombre y mujer. Depende de la ilusión que tengas en tu vida. Analiza cómo está cada uno de los 24 factores que afectan a la calidad del sueño y el descanso para mejorarlo:EL ÚLTIMO SEGURO QUE LO COMETES Y ES EL QUE MÁS AFECTA SIN DARTE CUENTA1: Luz: Persianas2: Ruido: Tapones. Ventanas aislantes. Cambiar de habitación. Mudarse. Vecinos. Calle. Coches. Discotecas. 3: Olores4: Temperatura y ventilación. Manta. Aire acondicionado. 21°5: Estrés y pensamientos y problemas. Aprender finanzas. Meditación. Aprender ventas. Divorciarse. 6: Digestión y carbohidratos. Melatonina. Vitamina D sol. Basa tu alimentación en carne, pescado y huevos. Marisco. Acompaña de verduras y hortalizas. Bebé solo agua. Nada de café, tabaco o alcohol. Cafeína, chocolate o teína. Nada de pan, dulces, chocolate, cereales, fruta (solo fresas, arándanos, frambuesas) y de postres. Tampoco sin grasa, sin azúcar porque lleva edulcorantes. Tampoco integral. 7: Cama, colchón y almohada y ropa y coleta8: Solo o acompañado. Tensión familiar. 9: Cansancio y deporte10 Hora de dormir y de levantarse. Estrés de alarma11: Uso de pantallas por luz azul. Usa luz roja. 12: Limpieza de habitación y sábanas. Sudor. Orden de la casa. 13: Salud14: Paz en vida. Felicidad. Propósito. No lo buscas, lo creas. 15. Ritmo circadianoNo es solo la hora de dormir. Es la regularidad. Desajustes continuos → sueño roto.(Despertarte cada día a una hora distinta te revienta el descanso aunque “duermas 8 horas”).16. Exposición a luz solar por la mañanaImpulsa la melatonina de la noche. Sin sol temprano → sueño débil por la noche.(10–15 min al salir de casa ya cambia el día).17. Hidratación… pero con timingBeber poco → mal sueño.Beber tarde → te despiertas para mear.Parece una tontería, pero no lo es.18. Respiración / vías nasalesDormir con la boca abierta o tener la nariz taponada destroza el sueño.Soluciones: tiras nasales, humidificador, limpiar mucosa, alergias tratadas.19. Apnea del sueño no diagnosticadaMuchísima gente la tiene y no lo sabe. Ronquido fuerte + cansancio diurno = sospecha.20. Preparación mental (pre-sleep routine)Tu cerebro necesita una rampa de descenso, no un apagón.Lectura ligera / estiramientos / diario rápido → vale más que mil suplementos.21. Estado hormonalCiclos menstruales, perimenopausia, testosterona baja, tiroides desajustada… Influyen muchísimo.22. Fármacos y suplementos que interfierenAntihistamínicos, antidepresivos, beta bloqueantes, incluso algún suplemento mal usado.Nadie lo quiere mirar… pero cuenta.23. Ruido interior (taquicardia, tensión muscular)No es estrés mental, es fisiológico.Si llegas “acelerado”, dormirte es difícil aunque estés rendido.24: Dormir con el móvil al lado incluso apagado. Reloj inteligente. Auriculares. Bluetooth. WiFi. Nevera. Cosas enchufadas. TV. Del vecino. Torreta de electricidad.Conviértete en un supporter de este podcast: https://www.spreaker.com/podcast/productividad-maxima--5279700/support.Newsletter Marketing Radical: https://marketingradical.substack.com/welcomeNewsletter Negocios con IA: https://negociosconia.substack.com/welcomeMis Libros: https://borjagiron.com/librosSysteme Gratis: https://borjagiron.com/systemeSysteme 30% dto: https://borjagiron.com/systeme30Manychat Gratis: https://borjagiron.com/manychatMetricool 30 días Gratis Plan Premium (Usa cupón BORJA30): https://borjagiron.com/metricoolNoticias Redes Sociales: https://redessocialeshoy.comNoticias IA: https://inteligenciaartificialhoy.comClub: https://triunfers.com

This week's episode starts with some bittersweet news: Silver Dollar City's beloved Thunderation mine train is closing in January 2027 (EB shares how it traumatized his daughter for a year!), plus there's purple track arriving at Six Flags Great Adventure for the Kingda Ka replacement—could it be a record-breaking spinning tower coaster?!   Disney's new CEO Josh D'Amaro is already shaking things up by sending Villains Land back to the drawing board because "it's not good enough," and Dollywood just announced the most creative marketing stunt ever: Flight 925, a themed vacation package flying fans from Orlando to Knoxville with in-flight trivia, Dolly merch, and exclusive park access.   The Coaster Radio Meetup is THIS SUNDAY and Mike & EB are finalizing the game plan! Join the guys as they map out their SeaWorld Orlando strategy for February 22nd—debating whether to rope drop Pipeline or gamble on crowd levels, discussing the merits of a $60 Quick Queue pass, and plotting their attack on Mako, Manta, Kraken, and Ice Breaker.   The guys also debate the eternal question: is it worth buying a Quick Queue when you might be a sucker if there are no lines? Plus details on following the meetup live via X/Twitter, the Seven Seas Food Festival sampler strategy, and why EB refuses to feel bad about eating fish. If you're heading to SeaWorld on Sunday, this is your essential pre-game show!

Tracklist and full info: https://www.bestdrumandbass.com/podcast581/HAPPY FRIDAY! We have a TON of big things happening this week, first and foremost one of the bigest EPs of the year so far, CROO just dropped an epic 4 track EP that if you are here, I know you will love. Also in the guest mix this week is CrackinDomes with a 100% Bad Syntax originals set, that I hope you will dig! Lock it in, and rock it out. Lets get the weekend started!Subscribe to the podcast: bestdnb.com/podcast  Croo - Juice EP [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd135/Supported by: Neonlight, MNDSCP, Figure, Bad Ace, Contam, Stonx, Manta, Klone, Akrom, Nuvertal, Drone, Nox, Subconscious BSC, MYGR, Michael Paino, Critical Control Point, Ollie Duracell, fibednb, Psidream, Stonerice, Johannes Soppa, Sinuous Recordings, Affirmation, Impex, Hijk, Malasuerte, Korax, Drbblz, BassDrive.com, Lennart Hoffmann, Diode, Crackindomes, Dip Vertigo, Bytecode, dela Moon, Pish Posh, Metric, ESKR, Insom, Scout 22, Tschul, Bons, The d34d b34t, 360 Degrees, CRS, X.morph, Autopsy, The Smell of Males, 9thwave, MV, J. Augustus, AL SEEN, ARI-ON, Needlenose, Lee UHF, Gigan and more!

- Gobierno suspende actividades mineras en Napo, El Oro y Loja: esto se conoce sobre la resolución- Ministro John Reimberg dice que municipios no deberían tener la competencia del tránsito- Mónica Palacios presenta noticia criminis contra Cynthia Gellibert por dos presuntos delitos- Esto se sabe del barco atunero Gold Tuna incendiado en Manta y el posible vínculo con alias ‘Mexicano'- Archivos de Epstein salpican a tres casas reales: reuniones a solas con un príncipe y mensajes como ‘cásate conmigo'

Carnaval do Vetor Norte é cultura, pertencimento e bastidor pesado.

Tracklist and more info: https://www.bestdrumandbass.com/podcast578/WELCOME BACK! We have one hell of an episode for you. The stateside giant Super Daddy DIODE is in the guest mix, celebrating the new release that just dropped on Abducted LTD that is currently sitting at #31 on the top 100 beatport charts. LOCK IT IN!ALSO during the podcast I announced that the new croo EP was dropping next week, but in my hurriedness I got the dates mixed up. Next week we will be dropping an epic single from PrayOneMe that you CAN NOT miss! The croo release will be following that :)Subscribe to the podcast: bestdnb.com/podcast  DIODE X GNTLMAN - Pirates / GNTLMAN - Where [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd133/Supported by: DJ Aphrodite, MNDSCP, Stonx, Diode, MV, X.Morph, Spiralus, Drone, BassDrive.com, Quannum Logic, Korax, Nox, Autopsy, Sindicate, Abstr4ct, Manta, ESKR, Lee UHF, Jane Doe DNB, D_E_B_T, ARI-ON, KNGHT, Scout 22, ZIONOV ND, The Smell of Males, Affirmation, Bytecode, Hijk, Needlenose, Metric, Crackindomes, CRS, Confusion, Stonerice, KNGHT, Sinuous Recordings, 360 Degrees, Lennart Hoffmann, Johannes Soppa, Warlock Audio, dela Moon, Critical Control Point, J. Augustus, Jay, Insom and more!

- Allanan vivienda de Luisa González en caso de presunto lavado activos- Tensión en Panamá: Gustavo Petro invitó al diálogo, pero Daniel Noboa no respondió- Daniel Noboa envía a la Asamblea dos proyectos de ley urgentes sobre minería, energía y gobiernos seccionales- Asesinan al hijo de alias Mexicano en Manta: esto se conoce sobre el crimen- Científicos en España logran eliminar el cáncer de páncreas más común en ensayos con ratones

Tracklist and more info: https://www.bestdrumandbass.com/podcast577/We are back, and boy do we have one hell of an episode for you! If you like tings that go PANG this is the mix for you, the destroyer Noisesmith is in the guest mix bringing the heavy tearout sound, and as always your resident mix by Bad Syntax starts things off as we celebrate the epic new single that just dropped on Abducted LTD. Lock it in, its time to GET HEAVY!Subscribe to the podcast: bestdnb.com/podcast  DIODE X GNTLMAN - Pirates / GNTLMAN - Where [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd133/Supported by: DJ Aphrodite, MNDSCP, Stonx, Diode, MV, X.Morph, Spiralus, Drone, BassDrive.com, Quannum Logic, Korax, Nox, Autopsy, Sindicate, Abstr4ct, Manta, ESKR, Lee UHF, Jane Doe DNB, D_E_B_T, ARI-ON, KNGHT, Scout 22, ZIONOV ND, The Smell of Males, Affirmation, Bytecode, Hijk, Needlenose, Metric, Crackindomes, CRS, Confusion, Stonerice, KNGHT, Sinuous Recordings, 360 Degrees, Lennart Hoffmann, Johannes Soppa, Warlock Audio, dela Moon, Critical Control Point, J. Augustus, Jay, Insom and more!

This show has been flagged as Clean by the host. This brings us to a look at some of Arthur C. Clarke's other stories, A Time Odyssey (1951), Tales From the White Hart (1957), The Nine Billion Names of God (1954), The Star (1955), Dolphin Island (1964), and A Meeting With Medusa (1971. These stories will wrap up our look at Clarke's Science Fiction and we have seen a lot of good stuff here. And as a final note, we cover CLarke's Three Laws. Arthur C. Clarke: Other Works, A Time Odyssey A collaboration between two of science fiction's best authors: what could possibly go wrong? Well, something went wrong. This series is not bad, but I hesitate to describe it as good. This series was described by Clarke as neither a prequel nor a sequel, but an “orthoquel”, a name coined from “orthogonal”, which means something roughly like “at right angles”, though it is also used in statistics to denote events that are independent and do not influence each other. And in relativity theory Time is orthogonal to Space. And in multi-dimensional geometry we can talk about axes in each dimension as orthogonal to all of the others. It is something I can't picture, being pretty much limited to three dimensions, but it can be described mathematically. It is sort of like the 2001 series, but not really. It has globes instead of monoliths. And the spheres have a circumference and volume that is related to their radius not by the usual pi, but by exactly three. Just what this means I am not sure, other than they are not sphere's in any usual sense of the word. In this story these spheres seem to be gathering people from various eras and bringing them to some other planet which gets christened “Mir”, though not in any way to the Russian Space Station. It is a Russian word that can mean “peace”, “world”, or “village”. I have seen it used a lot to refer to a village in my studies of Russian history. Anyway, the inhabitants include two hominids, a mother and daughter, a group of British Redcoats, Mongols from the Genghis Khan era, a UN Peacekeeper helicopter, a Russian space capsule, an unknown Rudyard Kipling, the army of Alexander The Great… Well at least they have lots of characters to throw around. They end up taking sides and fighting each other. In the end several of the people are returned to Earth in their own time. But the joke is on them. The beings behind the spheres are call themselves The Firstborn because they were the first to achieve sentience. They figure that best way for them to remain safe is to wipe out any other race that achieves sentience, making them to polar opposite of the beings behind the monoliths in 2001, for whom the mind is sacred. Anyway, the Firstborn have arranged for a massive solar flare that will wipe out all life on Earth and completely sterilize the planet, but conveniently it will happen in 5 years, leaving time for plot development. Of course the people of Earth will try to protect themselves. Then in the third book of the series an ominous object enters the solar system. This is of course a callback to the Rama object. It is like they wanted to take everything from the Rama series and twist it. While I love a lot of Clarke's work and some of Baxter's as well, I think this is eminently skippable. The two of them also collaborated on the final White Hart story, which isn't bad Other Works Tales from the White Hart This collection of short stories has a unity of the setting, a pub called White Hart, where a character tells outrageous stories. Other characters are thinly disguised science fiction authors, including Clarke himself. Clarke mentions that he was inspired to do this by the Jorkens stories of Lord Dunsany, which are also outrageous tall tales, but lacking the science fictions aspects of Clarke's stories. Of course this type of story has a long history, in which we would do well to mention the stories of Baron Munchausen, and of course the stories of L. Sprague de Camp and Fletcher Pratt as found in Tales from Gavagan's Bar. And Spider Robinson would take this basic idea and turn it into a series of books about Callahan's Place. Stories of this type are at least as much Fantasy as anything, but quite enjoyable, and I think I can recommend all of these as worth the time to while away a cold winter's evening while sitting by a warm fire with a beverage of choice. The Nine Billion Names of God This short story won a retrospective Hugo in 2004 as being the best short story of 1954. The idea is that a group of Tibetan monks believe that the purpose of the universe is to identify the nine billion names of God, and once that has been done the universe will no longer have a purpose and will cease to exist. They have been identifying candidates and writing them down, but the work is very slow, so they decide that maybe with a little automation they can speed it up. So they get a computer (and in 1954, you should be picturing a room-sized mainframe), and then hire some Western programmers to develop the program to do this. The programmers don't believe the monks are on to anything here, but a paycheck is a paycheck. They finish the program and start it running, but decide they don't want to be there when the monks discover their theory doesn't work, so they take off early without telling anyone, and head down the mountain. But on the way, they see the stars go out, one by one. The Star This classic short story won the Hugo for Best Short Story in 1956. The story opens with the return of an interstellar expedition that has been studying a system where the star went nova millennia ago. But the expedition's astrophysicist, a Jesuit Priest, seems to be in a crisis of faith. And if you think it implausible that a Jesuit Priest could also be an astrophysicist, I would suggest you look into the case of the Belgian priest Georges Lemaître, who first developed the theory of the Big Bang. Anyway, in the story, they learn that this system had a planet much like Earth, and it had intelligent beings much like Earth, who were peaceful, but in a tragic turn of events they knew that their star was going to explode, but they had no capability of interstellar travel. So they created a repository on the outermost planet of the system that would survive the explosion, and left records of their civilization. And when the Jesuit astrophysicist calculated the time of the explosion and the travel time for light, he is shaken: “[O]h God, there were so many stars you could have used. What was the need to give these people to the fire, that the symbol of their passing might shine above Bethlehem?” Dolphin Island This is a good Young Adult novel about the People of the Sea, who are dolphins. They save a young boy who had stowed away on a hovership that subsequently had crashed, and because no one knew about him he was left among the wreckage when the crew takes off in the life boats. And from here it is the typical Bildungsroman you find in most Young Adult novels. The dolphins bring him to an island, where he becomes involved with a research community led by a professor who is trying to communicate with dolphins. He learns various skills there, survives dangers, and in the end has to risk his life to save the people on the island. If you have a 13 year old in your house, this is worth looking for. A Meeting With Medusa This won the 1972 Nebula Award for Best Novella. It concerns one Howard Falcon, who early in the story has an accident involving a helium-filled airship, is badly injured, and requires time and prosthetics to heal. But then he promotes an expedition to Jupiter that uses similar technology, a Hot-Hydrogen balloon-supported aircraft. This is to explore the upper reaches of Jupiter's atmosphere, which is the only feasible way to explore given the intense gravity of this giant planet. Attempting to land on the solid surface would mean being crushed by the gravity and air pressure, so that is not possible. The expedition finds there is life in the upper clouds of Jupiter. Some of it is microscopic, like a kind of “air plankton” which is bio-luminescent. But there are large creatures as well, one of which is like jellyfish, but about a mile across. This is the Medusa of the title. Another is Manta-like creature, about 100 yards across, that preys on the Medusa. But when the Medusa starts to take an interest on Falcon's craft, he decides to get out quick for safety's sake. And we learn that because of the various prosthetics implanted after the airship accident Falcon is really a cyborg with much faster reactions than ordinary humans. As we have discussed previously, Clarke loved the sea, and in this novella he is using what he knows in that realm to imagine a plausible ecology in the atmosphere of Jupiter. Of course when he wrote this novella no one knew about the truly frightening level of radiation around Jupiter, but then a clever science fiction writer could come up with a way to work around that. Clarke's Three Laws Finally, no discussion of Arthur C. Clarke can omit his famous Three Laws. Asimov had his Three Laws of Robotics, and Clarke had his Three Laws of Technology. When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong. The only way of discovering the limits of the possible is to venture a little way past them into the impossible. Any sufficiently advanced technology is indistinguishable from magic. This concludes our look at Arthur C. Clarke, the second of the Big Three of the Golden Age of Science Fiction. And that means we are ready to tackle the Dean of Science Fiction, Robert A. Heinlein. Links: https://en.wikipedia.org/wiki/A_Time_Odyssey https://en.wikipedia.org/wiki/Tales_from_the_White_Hart https://en.wikipedia.org/wiki/Joseph_Jorkens https://en.wikipedia.org/wiki/Baron_Munchausen https://en.wikipedia.org/wiki/Tales_from_Gavagan%27s_Bar https://en.wikipedia.org/wiki/Callahan%27s_Crosstime_Saloon https://en.wikipedia.org/wiki/The_Nine_Billion_Names_of_God https://en.wikipedia.org/wiki/The_Star_(Clarke_short_story) https://en.wikipedia.org/wiki/Dolphin_Island_(novel) https://en.wikipedia.org/wiki/A_Meeting_with_Medusa https://en.wikipedia.org/wiki/Clarke%27s_three_laws https://www.palain.com/science-fiction/the-golden-age/arthur-c-clarke/arthur-c-clarke-other-works/ Provide feedback on this episode.

En este episodio de 'Carretera y Manta' recibimos a un viajero incansable, David Giménez Ramos, un aventurero que recorre el perímetro de la península ibérica a pie. David ha sacado unos munitos en su 'largo caminar' desde que partió de Salou a Murcia, caminado durante más de doscientos días, acompañado únicamente por su carro de mano llamado Charly.Durante su paso por la Región de Murcia, llega hasta Onda Regional donde nos cuenta las historias de vida de solidaridad y conocimeinto de territorios desconocidos que ha ido descubriendo donde la naturaleza, las playas y la luz del sol son su casa y refugio.Además esta tarde nuestro querido 'motero aventurero' Caludio, nos envia un mensaje dese el otro lado del Atlántico, y nos cuenta cómo ha sido ver por primera vez, 'volcanes que parecen lagos, cascadas que van all reves y el Pacífico'

- Vecino pierde el control y destruye un auto por un conflicto que se salió de las manos - Un adicto a la pizza, salvado por una empleada de Domino's - Joven asesina a una persona en la CDMX y es descubierto tras enviar fotos por error a su mamá - Detienen a dos caníbales en Tabasco; buscan a cinco - Manta en Culiacán acusa a la CIA de intervenir - Ladrones armados roban $100,000 en mercancía de cartas Pokémon - Estudiante de Alaska arrestado por comerse la obra de arte de otra persona con IA - El chihuahua que salvó a su dueño de la muerte en un glaciar suizo - Alistan demanda colectiva defraudados por falsa carrera de Star Wars - El dueño de una verdulería decide echar de su local a un hombre que fue declarado culpable por abuso infantil - Lily Phillips, polémica estrella de OnlyFans, se bautizó: “Quiero reencontrarme con Dios” - Rescatan a hombre atrapado en contenedor de reciclaje en Guadalajara - Quilmes: dos adolescentes iban a robar en caballo y fueron detenidos tras una insólita persecución - Una Orca hace explotar a un Pez Luna - Hombre entrena cuervos a atacar gorras MAGA También puedes escucharnos en Youtube, Spotify, Apple Podcasts, Amazon Music o tu app de podcasts favorita. Apóyanos en Patreon: https://www.patreon.com/leyendaspodcast​ Apóyanos en YouTube: https://www.youtube.com/c/leyendaslegendarias/join Síguenos: https://instagram.com/leyendaspodcast​ https://twitter.com/leyendaspodcast​ https://facebook.com/leyendaspodcast​ #Podcast​ #LeyendasLegendarias​ #HistoriasDelMasAca

- Vecino pierde el control y destruye un auto por un conflicto que se salió de las manos - Un adicto a la pizza, salvado por una empleada de Domino's - Joven asesina a una persona en la CDMX y es descubierto tras enviar fotos por error a su mamá - Detienen a dos caníbales en Tabasco; buscan a cinco - Manta en Culiacán acusa a la CIA de intervenir - Ladrones armados roban $100,000 en mercancía de cartas Pokémon - Estudiante de Alaska arrestado por comerse la obra de arte de otra persona con IA - El chihuahua que salvó a su dueño de la muerte en un glaciar suizo - Alistan demanda colectiva defraudados por falsa carrera de Star Wars - El dueño de una verdulería decide echar de su local a un hombre que fue declarado culpable por abuso infantil - Lily Phillips, polémica estrella de OnlyFans, se bautizó: “Quiero reencontrarme con Dios” - Rescatan a hombre atrapado en contenedor de reciclaje en Guadalajara - Quilmes: dos adolescentes iban a robar en caballo y fueron detenidos tras una insólita persecución - Una Orca hace explotar a un Pez Luna - Hombre entrena cuervos a atacar gorras MAGA También puedes escucharnos en Youtube, Spotify, Apple Podcasts, Amazon Music o tu app de podcasts favorita. Apóyanos en Patreon: https://www.patreon.com/leyendaspodcast​ Apóyanos en YouTube: https://www.youtube.com/c/leyendaslegendarias/join Síguenos: https://instagram.com/leyendaspodcast​ https://twitter.com/leyendaspodcast​ https://facebook.com/leyendaspodcast​ #Podcast​ #LeyendasLegendarias​ #HistoriasDelMasAca

L'analisi dei nuovi arrivi in Serie A in ottica fantacalcistica prosegue. Oggi presentiamo Pol Lirola, nuovo esterno dell'Hellas Verona. A Potrero ne parlano Enrico Zambruno e Roberto Ugliono.Potrero, dove tutto ha inizio. Un podcast sul calcio italiano e internazionale.Su Como TV (https://tv.comofootball.com) nel 2026 potete seguire in diretta le partite della Saudi Pro League, Saudi King's Cup, Supercoppa d'Arabia, Copa Libertadores, Copa Sudamericana, Recopa, Liga Profesional Argentina, Trofeo de Campeones argentino, Eredivisie, Coppa di Francia, Scottish Premiership, Coppa di Scozia, Scottish League Cup, Scottish Championship, Coppa di Portogallo, Supercoppa di Portogallo, HNL croata e tutti i contenuti di calcio italiano e internazionale on demand.Diventa un supporter di questo podcast: https://www.spreaker.com/podcast/potrero--5761582/support.

I denne episoden av Scoochpodden er vi på besøk hos Kenneth Høitomt! Hjemme på tunet har han bygget en låve i beste dragestil – et bygg reist for å romme flest mulig av hans mange interesser. Om drømmen startet med en glødende turbo under vingepanseret på skjet've-stetta, eller med E-typen fra Matchbox er usikkert, men nå står det her... alt sammen! Han påstår selv at han har noe som er mye verre enn ADHD, det lar vi være usag,t men det er hevet over enhver tvil at dette er en kar med arbeidskapasitet og enorm bredde! Gjennom 40 år har han restaurert og samlet på alt han noen gang har drømt om. Det går fra Messerschmitt til Shelby via Manta, fra Cadillac til bølle PV, det er High boy, SOHC, Jaguar, Henderson, Impala, Cobra, folkevogn, Indianere og gassere! Og Kenneth har full kontroll på historien – blant tidligere eiere finner vi shady embedsmenn, konger og Franco Sbarro. Ja og så har han den Mangusta'n du har sett! Takk for praten Kenneth!Bli patreon av Scoochpodden å få episodene reklamefrie: https://www.patreon.com/scoochpodFølg oss på facebook: https://www.facebook.com/profile.php?id=100051375947801Instagram: https://www.instagram.com/scoochpod/ Hosted on Acast. See acast.com/privacy for more information.

Ford praat met BYD om batterijen voor hybrides te kopen, meldt The Wall Street Journal. Het zou volgens bronnen gaan om het importeren van BYD-batterijen voor hybrides die Ford buiten de VS maakt. In Amerika geldt een forse importheffing op onderdelen en batterijen uit China. Ford benadrukt dat met veel partijen overleg plaatsvindt over mogelijke samenwerkingen. Verder in de auto-update: Red Bull Racing onthult de RB22, de nieuwe F1-auto van Max Verstappen. De modelnaam Manta keert voorlopig niet terug bij Opel. De Consumentenbond presenteert vandaag het grootste betrouwbaarheidsonderzoek naar auto's in Nederland.See omnystudio.com/listener for privacy information.

Además Claudio José Pérez nos manda una primera crónica del viaje que está realizando en moto por Argentina.

Ein Unternehmen, mit dem ich schon oft und sehr gerne zusammengearbeitet habe. Eine Firma, die ich außerdem schon seit meiner Kindheit kenne – geprägt durch meinen Vater. Verrückterweise hat er damals sogar schon Nockenwellen für seinen Manta bei DBilas gekauft. Solche Dinge brennen sich ein.Als ich später das klassische Sauger-Tuning für mich wiederentdeckt habe, war klar: DBilas Dynamic ist meine erste Adresse.In diesem Podcast spreche ich mit Zisis, dem Sohn des Unternehmensgründers, über die Entstehung von DBilas – vom heimischen Tuning für Freunde und Bekannte bis hin zum heutigen professionellen Zulieferer für hochwertige Motor-Tuning-Hardware. Und das längst nicht mehr nur im Saugerbereich.Was macht DBilas wirklich aus?Wo liegen die Unterschiede zwischen einer Drag- und einer Langstreckennockenwelle?Wie viel PS kann ein schlecht dimensioniertes Saugrohr kosten?Und wie viel Potenzial steckt vielleicht noch in eurem eigenen Motor?All das – und mehr – hört ihr hier im Podcast

Un sac à parole vient de faire son entrée ESM. Autrement dit un Kouyaté. Un sac à paroles, c'est-à-dire un griot, un diplomate, qui plus est fils de l'immense Sory Kandia Kouyaté, la voix d'or, celle de la Guinée indépendante. (Rediffusion) Le temps et les révolutions ont beau passé, Kandia (on l'appelle Kandia au village) est toujours là, son épopée mandingue toujours puissante, prête à distiller un message à nos conflits contemporains. L'héritier, le fils, Kaabi Kouyaté passe de case en case, de métropole en lieu-dit pour porter la bonne parole griotique. Il est armé pour ça : auteur, compositeur, joueur de ngoni, naviguant entre théâtre, musique traditionnelle et jazz mandingue, il vient déposer à vos pieds deux présents, Tribute to Kandia, son album hommage & le documentaire de Laurent Chevallier intitulé «La trace de Kandia». Une possibilité pour vous de suivre en son et lumière la trace du griot de Manta.   Programmation de notre invité : • Sory Kandia Kouyaté - Keme Bourema  • Kelitigui & ses tambourinis - Maderi • Enrico Macias - Enfant de tous pays • Puccini, Pavarotti - Nessim Dorma  • Kaabi Kouyate - Dari.

Un sac à parole vient de faire son entrée ESM. Autrement dit un Kouyaté. Un sac à paroles, c'est-à-dire un griot, un diplomate, qui plus est fils de l'immense Sory Kandia Kouyaté, la voix d'or, celle de la Guinée indépendante. (Rediffusion) Le temps et les révolutions ont beau passé, Kandia (on l'appelle Kandia au village) est toujours là, son épopée mandingue toujours puissante, prête à distiller un message à nos conflits contemporains. L'héritier, le fils, Kaabi Kouyaté passe de case en case, de métropole en lieu-dit pour porter la bonne parole griotique. Il est armé pour ça : auteur, compositeur, joueur de ngoni, naviguant entre théâtre, musique traditionnelle et jazz mandingue, il vient déposer à vos pieds deux présents, Tribute to Kandia, son album hommage & le documentaire de Laurent Chevallier intitulé «La trace de Kandia». Une possibilité pour vous de suivre en son et lumière la trace du griot de Manta.   Programmation de notre invité : • Sory Kandia Kouyaté - Keme Bourema  • Kelitigui & ses tambourinis - Maderi • Enrico Macias - Enfant de tous pays • Puccini, Pavarotti - Nessim Dorma  • Kaabi Kouyate - Dari.

Más opiniones en: ultimahora.com/opinion

Donate (no account necessary) | Subscribe (account required) Join Bryan Dean Wright, former CIA Operations Officer, as he dives into today's top stories shaping America and the world. In this Monday Headline Brief of The Wright Report, Bryan covers a massive FBI investigation into Somali fraud networks in Minnesota, the Trump administration's accelerating deportation and surveillance strategy, the growing political fight over prices and the Senate filibuster, improving drought conditions in the western United States, and major global developments from Africa, Latin America, China, and Australia. FBI Expands Probe into Somali Fraud Networks: FBI Director Kash Patel surged agents and resources into Minnesota following evidence of roughly nine billion dollars in suspected fraud tied to Somali-run daycare centers, Medicaid programs, food banks, and autism services. Investigators are now examining whether state officials and Democratic politicians enabled the schemes by shutting down early warnings. Bryan explains how viral footage showed dozens of fake daycare centers with no children enrolled, yet receiving massive public funds. Political Fallout and Questions for Democrats: Reports indicate that some Somali donors involved in the fraud also contributed to Democratic campaigns across multiple states. Governor Tim Walz previously halted fraud investigations after activists claimed discrimination. Bryan raises questions about whether these networks were used to generate political donations and votes, calling the potential scale of abuse "almost unimaginable." Trump Escalates Immigration Enforcement: ICE expanded highway operations targeting illegal migrant truck drivers in multiple states, while also arresting migrants at court check-ins who then skipped hearings, making them automatically deportable. The administration is deploying advanced tools, including facial recognition, license plate readers, and data from the IRS and Social Security Administration, to locate illegal migrants. Trump also increased the voluntary self-deportation bonus to $3,000, with airfare included, if migrants leave by December 31. Surveillance Tools Target Extremists: The same tracking systems are now being used to identify Antifa members and left-wing agitators under investigation for violence. DOJ officials say the effort responds to intelligence showing left-wing terrorism is now more prevalent than right-wing violence in the United States. Prices and the Filibuster Fight: President Trump warned that inflation and pricing will decide the 2026 midterms. With another government shutdown looming in January, he urged Senate Republicans to eliminate the filibuster to pass healthcare reform. A new GAO audit found widespread Obamacare fraud, including subsidies paid to deceased individuals and duplicate Social Security numbers. Western Drought Conditions Improve: California's drought has eased significantly, boosting agricultural water supplies. Lake Mead rose by three feet following recent storms, adding roughly seventy-two billion gallons of water, more than southern Nevada's projected annual usage. U.S. Strikes ISIS in Nigeria: The Pentagon launched missile strikes on ISIS training camps in northern Nigeria in coordination with the Nigerian government. Democrats criticized the strikes, while the White House rejected claims of racial motivation. Bryan warns that Islamist groups are attempting to establish a caliphate across central Africa. Trump Expands Influence in Latin America: The United States will reopen a strategic base in Manta, Ecuador, to counter narcotics trafficking and monitor Chinese influence. Conservative allies backed by Trump also won elections in Honduras, strengthening U.S. leverage across the region. China Signals Military Threats: Photos released by Chinese media show ballistic missiles concealed in cargo ship containers, a tactic that could be used to attack U.S. forces or ports during a conflict. Bryan says the images were deliberately leaked and amplified by Chinese bots as a warning to the West. Australia Downplays Islamist Attack: Australian officials claimed a recent ISIS-inspired attack on Jews was not religiously motivated, drawing sharp criticism. Bryan argues that refusing to acknowledge the crisis within Islam mirrors decades of Western denial and will lead to more violence. Listener Questions Close the Episode: Bryan answers questions on Ukraine's mineral deals, fuel supply risks tied to California refinery closures, and whether the American republic still exists. He argues the United States now functions more like a parliamentary democracy and explains why the filibuster debate reflects that deeper shift.   "And you shall know the truth, and the truth shall make you free." - John 8:32     Keywords: FBI Somali fraud Minnesota, Kash Patel investigation, Tim Walz daycare Medicaid scandal, ICE deportation surveillance tools, self deportation bonus Trump, Antifa terrorism DOJ tracking, Obamacare fraud GAO audit, Lake Mead drought recovery, U.S. Nigeria ISIS airstrikes, Ecuador Manta base Trump, Honduras election Asfura, China cargo ship missiles, Australia ISIS attack denial, filibuster healthcare reform debate

NotiMundo Estelar - Patricio Haro, Ecuador y EE. UU. avanzan en seguridad conjunta desde Manta by FM Mundo 98.1

La periodista se ha detenido en los dos mensajes que ha publicado el exministro en el que asegura que si se produjo una reunion entre Sanchez y Otegi y apunta a un uso irregular del piso oficial de Yolanda Diaz.

Agradece a este podcast tantas horas de entretenimiento y disfruta de episodios exclusivos como éste. ¡Apóyale en iVoox! Después de 28 años de absoluto silencio, el testigo más misterioso del Caso Alcàsser rompe su juramento de sombra y hablará EN DIRECTO en nuestro programa. ¿Por qué es el testigo más misterioso de todo este caso? ¿Por qué decidió guardar silencio durante casi tres décadas? ¿Acaso sabe quién fue realmente el responsable de aquel suceso que aún hoy genera escalofríos? ¿Y de dónde salió la información clasificada que aseguró tener… información que jamás debía haber visto la luz? Prepárate para una noche en la que las verdades ocultas, los secretos enterrados y las preguntas prohibidas dejarán de estar en la penumbra. Lo que Valeriano revele podría cambiarlo todo. La verdad ya no podrá esconderse. Escucha este episodio completo y accede a todo el contenido exclusivo de Informe Enigma. Descubre antes que nadie los nuevos episodios, y participa en la comunidad exclusiva de oyentes en https://go.ivoox.com/sq/277207

Full tracklist and info: https://www.bestdrumandbass.com/podcast570/ITS FRIDAY! This week we have a super banging mix from Constructive Sine in the guest mix, and as usual your resident Bad syntax kicks things off to get you prepared for the weekend ahead. Lock it in, its time to rock out! Subscribe to the podcast: bestdnb.com/podcastSindicate - Criminal Remixed ft Karpa & Raido, FauxRealx, Stonx, and Bad Syntax [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd131/Supported by: DJ Aphrodite, Mindscape, The Sect, Figure, BassDrive, Sinuous Recordings, Stonx, 5AH5H, Diode, DJ Odi, Jane Doe DNB, Direct Shift, Skamele Recordings, Critical Control Point, Johannes Soppa, Octane Amy, MYGR, Nox, Murmuration Events, The Smell of Males, Bad Ace, Semantics, fibednb, Inside Dnb, ZIONOV ND, Needlenose, Chief Jesta, Lennart Hoffmann, Manta, Nuvertal, Nightstalker, Korax, ESKR, 360 Degrees, Confusion, Bytecode, dela Moon, J. Augustus, Hijk, Metric, MV, ARI-ON, Scout 22, Drbblz, Stonerice, Dialective, X.morph, Subcat and More!Catch Bad Syntax alongside some of the largest names in the game in Atlanta for Jungle Bells 2025! Click the image for more info!

Tracklist and more info: https://www.bestdrumandbass.com/podcast569/WE ARE BACK my friends, with another epic episode to get your weekend started. This week we have Drillcut in the guest mix after an amazing debut on various labels this year, as well as the resident mix by Bad Syntax. LOCK IT IN, its time to rock!Subscribe to the podcast: bestdnb.com/podcast Sindicate – Criminal Remixed ft Karpa & Raido, FauxRealx, Stonx, and Bad Syntax [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd131/Supported by: DJ Aphrodite, Mindscape, The Sect, Figure, BassDrive, Sinuous Recordings, Stonx, 5AH5H, Diode, DJ Odi, Jane Doe DNB, Direct Shift, Skamele Recordings, Critical Control Point, Johannes Soppa, Octane Amy, MYGR, Nox, Murmuration Events, The Smell of Males, Bad Ace, Semantics, fibednb, Inside Dnb, ZIONOV ND, Needlenose, Chief Jesta, Lennart Hoffmann, Manta, Nuvertal, Nightstalker, Korax, ESKR, 360 Degrees, Confusion, Bytecode, dela Moon, J. Augustus, Hijk, Metric, MV, ARI-ON, Scout 22, Drbblz, Stonerice, Dialective, X.morph, Subcat and More!Catch Bad Syntax alongside some of the largest names in the game in Atlanta for Jungle Bells 2025! Click the image for more info!

Este domingo se realiza en Ecuador un referéndum con cuatro preguntas. La más polémica: ¿están los ciudadanos a favor o en contra de permitir la instalación de bases militares extranjeras en el país? Según el presidente Daniel Noboa, estas bases serían una opción para enfrentar la violencia que azota al país. Sin embargo, la experiencia contradice ese argumento, advierte uno de nuestros expertos entrevistados.  El presidente de Ecuador Daniel Noboa al presentar a finales de octubre la manera en que el ejército estadounidense se instalaría en su país en caso de que los ecuatorianos votaran sí a la instalación de bases militares de ese país en su territorio comentó: “Como vemos, siempre quieren tergiversar las cosas. ¡¿Qué le vamos a regalar a los gringos espacio?! Primero, vamos a organizar una consulta”. Para el ex jefe de inteligencia militar de Ecuador, Mario Pazmiño Silva, la propuesta de Noboa tiene las de ganar en el referendo del domingo. "Esta pregunta va a ser mayoritariamente aceptada. Sin embargo, es necesario manifestar que una base militar por sí sola no va a poder resolver el problema de la inseguridad en Ecuador. Lo que sí va a hacer es contribuir con tecnología, inteligencia, equipamiento, para fortalecer la capacidad operativa de la fuerza pública ecuatoriana", señaló. El presidente Noboa aseguró que, si se modifica la Constitución, también invitaría a fuerzas militares brasileñas y a la policía europea (Europol). Sin embargo, Estados Unidos sería el más interesado, según Pazmiño Silva: Ecuador, uno de los principales puntos de paso del narcotráfico  "Ante el bloqueo que actualmente existe en el Caribe por el despliegue de la flota militar estadounidense, las organizaciones narcotraficantes han redireccionado sus cargamentos hacia otras rutas. Dos de esos corredores atraviesan el territorio ecuatoriano: el del océano Pacífico y el del Amazonas. Antes de este taponamiento, por Ecuador transitaban aproximadamente 950 toneladas de droga al año; sin embargo, con el cierre parcial del corredor caribeño, se estima que el flujo podría aumentar hasta entre 1.400 y 1.500 toneladas anuales. En otras palabras, mientras Estados Unidos logra contener el tráfico por el norte, el problema se expande por los costados, y Ecuador se consolida como uno de los principales puntos de paso del narcotráfico en la región", explicó. Pero Fernando Carrioni, investigador de FLACSO y experto en seguridad, insiste en que las intervenciones extranjeras no reducen la criminalidad: "Cuando tuvimos nosotros en Ecuador la base militar, la tasa de homicidios pasó de 13 homicidios en 1999 a casi 18 homicidios en el 2009. En otras palabras, no se redujo la violencia. Luego salió la base militar de Manta y se crearon dos bases militares en Colombia. Ese país tiene siete bases militares. En Colombia, del 2021 al 2022 hubo un incremento sostenido del cultivo de coca de 2.600 toneladas. Esto muestra que este tipo de iniciativas no reducen la violencia y tampoco reducen el narcotráfico", sostiene Carrioni. Las ciudades costeras de Manta y Salinas se anuncian como posibles ubicaciones para las bases militares extranjeras.

Este domingo se realiza en Ecuador un referéndum con cuatro preguntas. La más polémica: ¿están los ciudadanos a favor o en contra de permitir la instalación de bases militares extranjeras en el país? Según el presidente Daniel Noboa, estas bases serían una opción para enfrentar la violencia que azota al país. Sin embargo, la experiencia contradice ese argumento, advierte uno de nuestros expertos entrevistados.  El presidente de Ecuador Daniel Noboa al presentar a finales de octubre la manera en que el ejército estadounidense se instalaría en su país en caso de que los ecuatorianos votaran sí a la instalación de bases militares de ese país en su territorio comentó: “Como vemos, siempre quieren tergiversar las cosas. ¡¿Qué le vamos a regalar a los gringos espacio?! Primero, vamos a organizar una consulta”. Para el ex jefe de inteligencia militar de Ecuador, Mario Pazmiño Silva, la propuesta de Noboa tiene las de ganar en el referendo del domingo. "Esta pregunta va a ser mayoritariamente aceptada. Sin embargo, es necesario manifestar que una base militar por sí sola no va a poder resolver el problema de la inseguridad en Ecuador. Lo que sí va a hacer es contribuir con tecnología, inteligencia, equipamiento, para fortalecer la capacidad operativa de la fuerza pública ecuatoriana", señaló. El presidente Noboa aseguró que, si se modifica la Constitución, también invitaría a fuerzas militares brasileñas y a la policía europea (Europol). Sin embargo, Estados Unidos sería el más interesado, según Pazmiño Silva: Ecuador, uno de los principales puntos de paso del narcotráfico  "Ante el bloqueo que actualmente existe en el Caribe por el despliegue de la flota militar estadounidense, las organizaciones narcotraficantes han redireccionado sus cargamentos hacia otras rutas. Dos de esos corredores atraviesan el territorio ecuatoriano: el del océano Pacífico y el del Amazonas. Antes de este taponamiento, por Ecuador transitaban aproximadamente 950 toneladas de droga al año; sin embargo, con el cierre parcial del corredor caribeño, se estima que el flujo podría aumentar hasta entre 1.400 y 1.500 toneladas anuales. En otras palabras, mientras Estados Unidos logra contener el tráfico por el norte, el problema se expande por los costados, y Ecuador se consolida como uno de los principales puntos de paso del narcotráfico en la región", explicó. Pero Fernando Carrioni, investigador de FLACSO y experto en seguridad, insiste en que las intervenciones extranjeras no reducen la criminalidad: "Cuando tuvimos nosotros en Ecuador la base militar, la tasa de homicidios pasó de 13 homicidios en 1999 a casi 18 homicidios en el 2009. En otras palabras, no se redujo la violencia. Luego salió la base militar de Manta y se crearon dos bases militares en Colombia. Ese país tiene siete bases militares. En Colombia, del 2021 al 2022 hubo un incremento sostenido del cultivo de coca de 2.600 toneladas. Esto muestra que este tipo de iniciativas no reducen la violencia y tampoco reducen el narcotráfico", sostiene Carrioni. Las ciudades costeras de Manta y Salinas se anuncian como posibles ubicaciones para las bases militares extranjeras.

Un sac à parole vient de faire son entrée ESM. Autrement dit un Kouyaté. Un sac à paroles, c'est-à-dire un griot, un diplomate, qui plus est fils de l'immense Sory Kandia Kouyaté, la voix d'or, celle de la Guinée indépendante. Le temps et les révolutions ont beau passé, Kandia (on l'appelle Kandia au village) est toujours là, son épopée mandingue toujours puissante, prête à distiller un message à nos conflits contemporains. L'héritier, le fils, Kaabi Kouyaté passe de case en case, de métropole en lieu-dit pour porter la bonne parole griotique. Il est armé pour ça : auteur, compositeur, joueur de ngoni, naviguant entre théâtre, musique traditionnelle et jazz mandingue, il vient déposer à vos pieds deux présents, Tribute to Kandia, son album hommage & le documentaire de Laurent Chevallier intitulé «La trace de Kandia». Une possibilité pour vous de suivre en son et lumière la trace du griot de Manta.

Tracklist and more: https://www.bestdrumandbass.com/podcast568/Another week with epic DNB ahead! We just dropped an EPIC remix EP that includes some absolutely wicked remixes, including one by myself, on Abducted LTD. We also have TONTO back in the guest mix to rip it up, so lock it in and get your weekend moving! Subscribe to the podcast: bestdnb.com/podcast  Sindicate - Criminal Remixed ft Karpa & Raido, FauxRealx, Stonx, and Bad Syntax [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd131/Supported by: DJ Aphrodite, Mindscape, The Sect, Figure, BassDrive, Sinuous Recordings, Stonx, 5AH5H, Diode, DJ Odi, Jane Doe DNB, Direct Shift, Skamele Recordings, Critical Control Point, Johannes Soppa, Octane Amy, MYGR, Nox, Murmuration Events, The Smell of Males, Bad Ace, Semantics, fibednb, Inside Dnb, ZIONOV ND, Needlenose, Chief Jesta, Lennart Hoffmann, Manta, Nuvertal, Nightstalker, Korax, ESKR, 360 Degrees, Confusion, Bytecode, dela Moon, J. Augustus, Hijk, Metric, MV, ARI-ON, Scout 22, Drbblz, Stonerice, Dialective, X.morph, Subcat and More!Catch Bad Syntax alongside some of the largest names in the game in Atlanta for Jungle Bells 2025! Click the image for more info!

** VIDEO EN NUESTRO CANAL DE YOUTUBE **** https://youtube.com/live/KRWaFKfdS_A +++++ Hazte con nuestras camisetas en https://www.bhmshop.app +++++ #Actualidadmilitar #Geopolítica #GuerraEnUcrania Hoy nos vamos al frente más tenso de toda la guerra: el norte del Donbás y la línea de Kupiansk, donde Ucrania ha lanzado una serie de contraataques locales que están obligando al ejército ruso a redibujar su mapa operativo. En las últimas semanas, las tropas ucranianas han recuperado posiciones perdidas durante el verano, han frenado los asaltos rusos en Pokrovsk y están presionando los flancos del eje de Siversk y del valle del Oskil. Y eso nos deja una pregunta clave: ¿Está Rusia cubriendo demasiados frentes a la vez? ¿Es su ejército una manta demasiado corta que, al tapar el sur, deja el norte al descubierto? SUSCRÍBETE A @BELLUMARTISHISTORIAMILITAR Y @BELLUMARTISACTUALIDADMILITAR para no perderte ningún programa y únete a nuestra comunidad de apasionados por la historia militar, la geopolítica y los conflictos del mundo. Apóyanos para seguir creando contenido riguroso e independiente: Patreon: https://www.patreon.com/bellumartis PayPal: https://www.paypal.me/bellumartis Bizum: 656 778 825 Síguenos también en redes: Instagram: https://www.instagram.com/bellumartis Twitter / X: https://twitter.com/BellumartisHM Bellumartis Historia Militar — Porque entender el pasado es prepararse para el futuro.

Tracklist and more info: https://www.bestdrumandbass.com/podcast567/Welcome back my friends! Its Halloween and we are bringing the spooky sounds to get your weekend started. Stateside legend ODI is in this guest mix this week, along with your resident mix by Bad Syntax, so LOCK IT IN! Lets get the weekend started! Subscribe to the podcast: bestdnb.com/podcast  Direct Shift - Crazy Ivan / Bad Guy [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd130/Supported by: DJ Aphrodite, Future Signal, Diode, Psidream, DJ Odi, Metrik, dela Moon, Stonx, MYGR, Nox, 5AH5H/Eatbrain, Bytecode, Korax, Sindicate, MV, ARI-ON, Nightstalker, Autopsy, The Fi5th, Hijk, Manta, ZIONOV ND, 360 Degrees, Needlenose, Inside Dnb, Drum Pusher, Jane Doe DNB, Lennart Hoffmann, Akira DnB, ESKR and More!Catch Bad Syntax alongside some of the largest names in the game in Atlanta for Jungle Bells 2025! Click the image for more info!

(Día Internacional de la Libertad Religiosa) A partir de la conquista cristiana, en 1119, por parte de Alfonso I el Batallador, la convivencia entre cristianos y judíos en el Reino de Navarra fue de mal en peor hasta 1498, cuando los judíos fueron expulsados del Reino de Navarra —relata el historiador navarro Jaime Aznar—. En ese momento, los Reyes Católicos, habiendo ya expulsado a los judíos de la Monarquía Hispánica, presionaron a otros reinos a que siguieran su ejemplo, y eso dio como resultado que Catalina I y Juan III de Navarra determinaran así mismo obligar a los judíos a tomar la decisión de convertirse y quedarse allí, o de marcharse. «Muchos judíos optaron por quedarse, porque salir no era fácil. No tenían adónde ir, y viajar era entonces muy caro», explica el doctor Aznar. Desde el siglo nueve, Tudela había llegado a ser el territorio navarro con la población judía más numerosa. Pero desde el siglo dieciséis hasta el siglo diecinueve se expuso un lienzo en el que aparecían los nombres de los judíos acusados de ser falsos conversos a la religión cristiana, es decir, de los judíos que se habían convertido y que, para poder permanecer allí y evitar ser investigados por la Inquisición local, le habían pagado a la Corona de Navarra 650 ducados, hoy equivalentes a unos 150 mil dólares. Para colmo de males, a fin de que la difamación fuera perdurable, se hizo una manta que era como un gran lienzo, exhibida de tal manera que todo el mundo pudiera verla, en la que se reproducían los nombres de los judíos acusados de practicar su religión a escondidas, señalándolos como culpables no sólo a ellos de por vida sino también a su descendencia. «Esto era particularmente grave —concluye el profesor Aznar— porque no podía permitirse en modo alguno que se dijera que un familiar suyo estaba en la manta, es decir, que era judaizante, o que tenía un origen judío, por el desprestigio social y naturalmente económico que eso podía conllevar».1 De tal manta, siendo la más famosa la exhibida durante siglos en la catedral de Santa María de Tudela, procede la expresión «tirar de la manta», que el Diccionario de la Real Academia define como «descubrir un caso escandaloso que otro u otros tenían interés en mantener secreto».2 Si bien se sobreentiende que aquellas víctimas de discriminación y persecución religiosa no debieron haberse sentido forzadas a ocultar nada de las prepotentes y farisaicas autoridades eclesiásticas de esos tiempos, quiera Dios que entendamos que, en nuestro caso en particular, hoy más que nunca debemos vivir conscientes de la enseñanza de San Pablo de que cada uno de nosotros es una carta conocida y leída por todos, y acatar la advertencia de Jesucristo de que «todo lo que esté escondido se descubrirá, y todo lo que se mantenga en secreto llegará a conocerse».3 Carlos ReyUn Mensaje a la Concienciawww.conciencia.net 1 Jaime Aznar, «¿De dónde viene la expresión “tirar de la manta?” Entrevista Diario de Navarra En línea 17 abril 2025; Begoña Goitiandia y Javier Iborra, «Carlos Alsina recuerda el origen navarro de la expresión “tirar de la manta”», Diario de Navarra, 21 noviembre 2024 En línea 17 abril 2025. 2 Diccionario de la lengua española de la Real Academia Española En línea 17 abril 2025. 3 Lc 12:1-2 (TLA); 2Co 3:2

Tracklist and more info: https://www.bestdrumandbass.com/podcast566/We are back with another hard hitting podcast to get your weekend kicked off the right way! We are celebrating the brand new DIRECT SHIFT single that just dropped on Abducted LTD, and we have a special guest mix by BENNIT! Lock it in and lets get the weekend started!Subscribe to the podcast: bestdnb.com/podcast  Direct Shift - Crazy Ivan / Bad Guy [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd130/Supported by: DJ Aphrodite, Future Signal, Diode, Psidream, DJ Odi, Metrik, dela Moon, Stonx, MYGR, Nox, 5AH5H/Eatbrain, Bytecode, Korax, Sindicate, MV, ARI-ON, Nightstalker, Autopsy, The Fi5th, Hijk, Manta, ZIONOV ND, 360 Degrees, Needlenose, Inside Dnb, Drum Pusher, Jane Doe DNB, Lennart Hoffmann, Akira DnB, ESKR and More!Catch Bad Syntax alongside some of the largest names in the game in Atlanta for Jungle Bells 2025! Click the image for more info!

Send us a textIn this episode Matt talks to Mox all about Manta Rays. Mox has spent most of his life diving and snorkelling with these amazing animals and is able to share some very special insights. From cephalic lobes to theories on what Manta Rays eat, tune in to learn more about these gentle giants of the sea. Learn more and connect with Mox on his social media accounts https://www.instagram.com/mox_diveshttps://www.instagram.com/m.o.c.s_initiativeLearn more about Manta Rays by visitinghttps://www.maldivesmantaconservation.org/https://www.mantatrust.org/Visit the Seacreatures Podcast Patreon to support our showhttps://www.patreon.com/seacreaturespodcastCheck out Dan Musil (our theme composer)https://danmusilmusic.com/orhttps://www.facebook.com/dan.musil.musicVisit the Seacreatures Instagramhttps://www.instagram.com/seacreatures_podcast/Check out Matt Testoni's photography on Instagramhttps://www.instagram.com/matt_testoni_photography/or athttps://www.mtunderwatermedia.comVisit the Seacreatures Podcast buy me a coffee to support the showhttps://www.buymeacoffee.com/mattTestoniSupport the showhttps://www.instagram.com/seacreatures_podcast/

This week on Unchained, we've got a double-header. First, Zach Abrams, CEO of Bridge (acquired by Stripe), unveils Open Issuance, a platform designed to let any company launch its own stablecoin. He explains why the stablecoin duopoly is ending, why fragmentation won't slow adoption, and how stablecoins could pair with AI to reshape global money movement. Then, Kenny Li, co-founder of Manta Network, joins to reveal why Manta is pivoting away from being just another L2. He argues that the scaling wars are oversaturated, that mercenary users make infra battles a fight for crumbs, and that the real prize is at the application layer. Thank you to our sponsors! Mantle Aptos Guests: Zach Abrams, Co-Founder and CEO of Bridge Kenny Li, Co-Founder and Core Contributor of Manta Network Links: Unchained:  How New Stablecoin Startup Bridge Got Acquired by Stripe for $1.1B MetaMask Stablecoin mUSD Goes Live Why JPMorgan and Shopify Are Rolling Out New Products on Ethereum Layer 2 Base Tempo Launch Announcement: The Blockchain Designed for Payments Learn more about your ad choices. Visit megaphone.fm/adchoices

1. Wh0, Sam Frandisco, Marco Melissen - Let It In 2. VOLAC - Wannabe 3. Vanco, AYA.SYSTEM - Ma Tnsani (Yalla Habibi) (Tiesto Remix) 4. 22Bullets - Dope 5. Peter Brown - Ride The Rhythm 6. Pegassi - Get Up 7. Tobie bryant - Pica 8. Trace (UZ) - Bad & Boujee 9. Ziggy Ostas x Josh Christian - Get Me Hot 10. Ragie Ban - Habanera 11. James Hurr, Soleá Morente, STBAN - El Camino feat Josemi Carmona 12. Castion & Sergiodnine - Wanna Come 13. Vintage Culture feat. Noah Kulaga - Upon Your Skin 14. nimino - Better feat Manta

We present the fourteenth episode of Eatbrain Radio Season 2, your guide to the dark side of drum and bass! Grimey, dutty and disgusting all the way! Hosted by @5ha5h label// facebook.com/Eatbra1n twitter.com/eatbrain_now instagram.com/eatbrain eatbrain.net Tracklist // 1. Pandæmonium – ID [DUB] 2. Finalfix – S.O.L.D.I.E.R. [Blackout Music NL] 3. Zigi SC & Frannabik – Synapse Breaker [Eatbrain] 4. Blinded Theory & NERV3 – Hollow Ground [Paperfunk Recordings] 5. Ventex – ID [DUB] 6. Hackwaves & Wiguez – Lifeline [Eatbrain] 7. HIGHTHERE – Falling For You [Neurofuck] 8. Diode – Europa [Dirtbox Recordings] 9. Project Zeus & Volatile Cycle – Echelon [Murmuration Records] 10. State of Mind – Surreality Feat. Chris.SU [Shogun Audio] 11. Linkin Park – In The End (Audio Bootleg) [DUB] 12. Sindicate – Are You [Hanzom Music] 13. Entrop – Breaking Out of Trance [Neuropunk Records] 14. Bons – Stand Firm [Skamele Records] 15. PHACE – Fuego (SLWDWN Bootleg) [DUB] 16. Zombie Cats x Scout 22 – Kraken [Creatured] 17. Octavate & Killey – Party Time [Neuroheadz] 18. AKOV & REEBZ – Carry The Flame [Self Release] 19. Manta & Screamarts – Jupiter [DUB]

Thanks to Manta for sponsoring this episode! Get your sleep mask at https://tinyurl.com/yf6n5fvh and use code JONSOLO for 10% off!

Tracklist and more info: https://www.bestdrumandbass.com/podcast552/OH SHIT, its my birthday! Were going in with an extra heavy mix, and we have a top notch guest mix by the man FUTCH to round things out. Thank you to everyone whos reached out, and make sure to lock it in for this one. Your weekend soundtrack has arrived! Subscribe to the podcast: bestdnb.com/podcast  MoteXx ft Xyno & S.I.O.N – Amplifi / Breaking [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd124/Supported by: Bytecode, Aphrodite, Diode, Jane Doe DNB, ABELYN, Manta, MV, Sindicate, FauxRealz, 9thwave, Stonerice, Scout 22, Nightstalker, DJ Mag, Inside Dnb, Nox, Lee UHF and more

Tracklist and more info: https://www.bestdrumandbass.com/podcast551/Back at it with an extra jet fueled pack of goodness! We are celebrating the release of the newest Abducted LTD single by Motexx, and we have a wicked guest mix by AnnGree to get your weekend moving. Lock it in, its time to rock out!Subscribe to the podcast: bestdnb.com/podcast  MoteXx ft Xyno & S.I.O.N – Amplifi / Breaking [OUT NOW on Abducted LTD]Download / Stream: bestdrumandbass.com/altd124/Supported by: Bytecode, Aphrodite, Diode, Jane Doe DNB, ABELYN, Manta, MV, Sindicate, FauxRealz, 9thwave, Stonerice, Scout 22, Nightstalker, DJ Mag, Inside Dnb, Nox, Lee UHF and more

Tracklist and more info: https://www.bestdrumandbass.com/podcast550/It's that time of year again — fireworks in the sky and absolute fire in your speakers. The North American Producer Showcase (NAPS) is back for 2025, and we're coming in heavy! This year's edition is mixed by the powerhouse himself, Spiralus, who's stitched together a blazing lineup of tracks from some of the best and brightest across the continent.Packed with unreleased bangers, deep cuts, and relentless energy, this mix is a celebration of everything that makes the North American DnB scene so unstoppable. Lock in, crank it loud, and prepare for a ride — Your weekend has begun!Subscribe to the podcast: bestdnb.com/podcast MoteXx ft Xyno & S.I.O.N - Amplifi / Breaking [OUT NOW on Abducted LTD]Download / Stream: bestdnb.com/altd124Supported by: Bytecode, Aphrodite, Diode, Jane Doe DNB, ABELYN, Manta, MV, Sindicate, FauxRealz, 9thwave, Stonerice, Scout 22, Nightstalker, DJ Mag, Inside Dnb, Nox, Lee UHF and more