 have any puns to this talk, so I don't know what to do. So I figured instead of me just talking, we would watch Mad Max for the next 40 minutes. Not so good since I'm supposed to be speaking here. Anyway, I'm not going to talk about performance at all, which is what I normally talk about. And I was telling my wife I'm extremely nervous about this talk because it's probably the least technical talk I've given in quite a while. And she said, well, to calm yourself down, you should add some graphs or metaprogramming or something to it. So I just added a graph here. Just to calm me down. This is not a technical talk, really. And then I didn't know that, I actually didn't know that the hashtag was going to be hashtag. I just wanted to encourage everyone to tweet about my talk with hashtags. I really actually didn't know that. And I had this slide in here before then. Anyway, so thank you for having me. I'm really excited to be here. And thank you to the conference organizers. This is a picture of me with parents at the airport. It was really amazing. He picked me up in the south. And he actually had a sign that's cut off here at the bottom. I don't have it on this photo, but he had a sign for me, which I thought was great. Although it said Aaron Patterson on it when I think it should have said tender love. Thanks a lot. As Richard said, I work for Red Hat. Please buy some stuff from Red Hat. We're doing stuff with managing the cloud. So if you have a cloud that you need to manage. So I am assistant pharmacist, tender love. You may not be able to see it there, but I have tender love embroidered here on my outfit. You can come and see it later. I'm tender love on the internet. I'm also on the Ruby Core team and the Rails Core team. And I'm really excited to be here, but I was thinking about the name Keep Ruby Weird. And I started to think like, wow, this sounds exciting. Keep Ruby Weird. But why was I invited? I mean, I'm not weird. And then I realized this. All right. Now we know. So anyway, I am wearing a wig today so that you all take photos with him later. I have two cats. This one is, this is Gorbachev Huff Huff Fenderhorse. He's the more famous of my cats. This is my other cat, Chuchu. Her full name is SeaTac Airport YouTube Facebook. He's called her Chuchu though. She's more interested in programming. This is her and her natural habitat on top of my laptop. I sit next to the kitchen. I went into the kitchen and get a drink, come back out. There's a cat right on my laptop. And I look at it. I'm like, what are you doing? And the cat's just like, what? This is where I sit. Anyway, so she also has a red hat. This is what she's going to be for Halloween also. Gorbachev, he's a wrestler. This is a wrestling outfit. Anyway, so book sales time. So it's time for me to start selling my books, right? Because that's like trying to figure out what I'm going to do with my career. I figure, well, I'm going to start selling books. So like one thing you may or may not know about me is that I like to cure meats at home. And so the way that you do this, the way that you cure meats, like overall process is basically you put a bunch of meat into some casings and you hang it in a fridge for a while. And then after a while it turns into meat, into cured meat or a rot if you do it wrong. So don't do it wrong. Let's do it right, and you'll be fine. Anyway, you have to control the humidity inside of these, inside of these refrigerators, and the humidity has to be pretty high. About 70% humidity, 70 to 80% humidity, and most fridges aren't built to maintain that. So a lot of water will condense and then drip out the back of the fridge. And a lot more water drips, like this happens normally inside of everybody's refrigerators, it's just not very much water will drip out the back. But since I have to actually pump humidity into this fridge, a lot of water drips out the back. So I needed to have a place to run it, and I ran it to this, like I've stuck a tube into the back of the fridge, and I ran it out into this tray that collects all the water, right? And I mean, it collects maybe like, probably has like a gallon of water in it at a time, right? And I had it sitting out there, and it was uncovered and my cats were drinking it. And my wife says, my wife says like, she's like, you can't, don't let the cats drink that. They're not allowed to be drinking without water. And I'm like, who cares that like it condensed, it's got to be like super pure, right? Like it's going to be fine. It condensed on the back, comes out the back, it's got to be pure water. She's like, no, that's salami water. And I'm like, no, no, no, it's fine. It's probably like super pure. Don't worry about it. And she's like, no, it's the she insisted it was salami water. So I was like, you know what, fine, fine, I'm going to taste this sausage water. So I got a spoon, I got a spoon, dipped it in, took a taste of it. And I was like, oh, yeah, that is, that is awesome water. So we had to cover that up. But anyway, so this is the book I'm working on. I'll buy my book, please. So my top title is Keep Ruby Weird. I kept thinking about the title of this conference, and like, Oh, Ruby's weirdness and stuff. And I actually really like the title of this, I like the title of this conference. So I kept thinking about how do I keep Ruby weird. So I want to talk about that a bit. It's going to be most of my, most of the talk here. I'm going to talk about mistakes in public speaking. And I'm going to talk about is Ruby weird. And then I'm going to talk about homeopathic code optimizations. And then I'm going to talk about keeping Ruby weird. I said I wasn't going to talk about performance, but I will a little bit, just a very tiny bit in homeopathic code optimizations. But first I want to talk about things that I've been thinking about. So I think Ruby is amazing. Ruby is an amazing language. I love Ruby. We've made so much progress recently. I don't know if you've noticed this, but the garbage collector is getting better. Ruby 2.2 is going to have, going to have a, well, we have a generational garbage collector in 2.1, but 2.2, the generational garbage collector is going to be getting even better. 10 years ago we wouldn't have imagined having a garbage collector like this. 10 years ago our garbage collector was just a normal stop the world market sweep garbage collector. Nobody thought, oh, we're going to have an actual generational garbage collector. Today we do. I think it's amazing. Language is improving and we can see, we can see it coming along and getting better. But the thing is like people are still complaining about the language. People say, oh, Ruby slow, blah, blah, blah, they're complaining about it all the time. And I don't really like this. So what I was thinking about doing is I want to start a new language. I want, I want to implement a brand new language. And I'm going to call this language Poolang. This is a language is specifically engineered to be the worst language ever. And the reason I want to do this is so that whenever anybody complains about a particular language, whether it's Ruby or Python or PHP, you can say like, well, you know, if you think Ruby is bad, like, have you seen Poolang? I think it's terrible. That's the worst language ever. So that's like, that's what I want to strive for is build the worst language possible. And I think like, it'd be really good for making puns too, because you could say like in Poolang, everything is code spelled. There's a lot of potential in this language for bad stuff. So I was thinking what we'll do is we'll implement it in Excel. So, you know, Poolang, the worst language ever. We actually have a website now you can go to it. It's Poolang.org. Go to this website, but it has some it has some known issues. So this is what it looks like in Safari. This is what it looks like in Chrome. It just doesn't work on Windows. This website, if I have a project, I'll get on this public and go to my get up and find, you know, message the website. And like the first ticket that somebody files is like, it doesn't work in Windows. Why do you care? That is the internet people. So the internet is what happens. Anyway, so seriously, I want to make this, I actually want to make this, we should seriously make this language. But I don't think we should do it in Excel. I think we should do it in PostScript. We should. No, seriously. So look at this, like, I don't know if any of you have ever actually written PostScript straight. But PostScript is a stack based language, like it's just a stack. So this is an example of using PostScript. Well, GhostScript, like you just say, we actually have a stack here. So we say Tang, you hit enter with that puts 10 on the stack. And then you say five hit enter, and that puts five on the stack. And then you say add in it adds those two together puts a result back on the stack. So we have this stack based stack based programming language. And if you look at Ruby, you look at Ruby's virtual machine. So this is Ruby's virtual machine is also a stack based virtual machine. This is this is the instruction sequences for Ruby. So we say, like, put object five, that puts a five on the stack, put object 10, that puts a 10 on the stack, then we add, and then 15 is put back on the stack. So the Ruby VM is stack based. And the PostScript PostScript is also stack based. Therefore, the Ruby VM should equal the PostScript VM, right? Right? We can do this. We can do this. This might be a mistake. It might be a mistake. But I think mistakes are just fine. I think it's fine. Even if we did implement this thing, it would be fun because it would be fun, like something fun to learn, like we'd be able to learn about stack based programming languages and converting Ruby into a into a stack and actually how the virtual machine works under the hood. So anyway, now now on to the real the real talk, the real subject. I want to talk about some mistakes in public speaking, mistakes that I've made. The point of the section here is basically to tell you about like how I do, how I do public speaking, how I've made mistakes with public speaking, how you can be a better speaker and et cetera. Hopefully this will help out all the other speakers here today. And for those of you who want to speak, but maybe haven't done it yet. So hopefully you can get some pro tips from me here. And I want to tell you, I want to tell you about how I practice, I practice speaking and I actually practice a lot. I practice very, very frequently. And I mostly practice with my parents and my family and my wife actually call my parents all the time and tell them like about exactly what I do. I tell them that I'm, you know, I'm a programmer and I tell them what I do all day and explain all the different stuff. Like I even explained to them a weird thing, like, you know, rails, performance issues, things like that. I explain all the stuff to them. And the thing is like both of my parents are engineers, my mom's an electrical engineer, my dad's a mining engineer. Neither of them know, like they don't know programming very well, but they're both like capable people. They're both, you know, capable intelligent people. So it's not a big deal to explain to them like all this stuff. It's just that, you know, they might not have heard about these particular things. Right. Like if you think about any, if you think about it or the way I think about it is that any capable person can understand what I do or can do what I do. It's just, they don't have any experience doing it yet. So the way I approach it is I assume that people are capable. I assume that they can do, I assume anybody can do what I do. It's just that maybe they don't, they don't have the same experiences that I do. So what I try to do is say like, okay, well, they haven't heard about Ruby programming. Let's try to explain how this is like, they, anybody can understand it. It's just that they haven't heard about it yet. Right. So I try to think about it from their perspective, think about like their experiences and well, my experiences and know that they just haven't had the same experiences I have. And if they did, they could do what I do. So I try to explain to them from that perspective. And I think that helps with my explanations a lot. So I can, if I can explain it to my parents, I can explain it to anybody and I know that anybody, anybody can do what I do. So I should be able to explain to everyone. So if I understand their perspective, it makes it easier to explain to people. So now I want to talk about some actual mistakes. I said there wouldn't be any puns, maybe there are. Okay. So I'm going to talk about a few, a few different mistakes that I've made in public speaking. And hopefully you will not make those mistakes too. And this is the first one you may have heard about this one before. But if you haven't, I will tell you about it. I was going to give a talk at RailsConf, a keynote at RailsConf in front of about 2000 people. And every time I give a talk, I'm extremely nervous. I'm very, very nervous. And one of the things that I do before I give a talk, and this, this might be a little bit private, but I go to the bathroom. I always go to the bathroom first. And the reason I do that is because like, I don't want to be up on stage. And all of a sudden be like, that wouldn't be very good. You know, that wouldn't be very good for the top that you're giving. So, you know, I'm about like, I'm there. I'm going to give this talk. I'm insanely nervous. I can't like, I'm like, all right, well, I got to go do my thing. I go to the bathroom. I go to the bathroom. I'm like, okay, all I see is stalls. It's fine. I got to install. Let me tell you something about men's bathrooms, especially in large airports, as you go in and maybe you only, you only ever see stalls because urinals are somewhere else. Right. So I thought everything was normal. Go, go do my business. Like, leave the stall. I come out and I see like, I see a cleaning person in the bathroom and I'm like, oh, clean person's a woman. That's fine. I don't mind. I mean, I'm an adult. It's okay. It's okay. There's a woman in the men's bathroom. And then I look over and I see somebody washing her hands. And I'm like, oh no. And the cleaning lady says to me, she just points at me and she's like, get out of here. And I'm like, oh my God. What am I doing? Yeah. I think like, immediately I'm like, do I wash my hands? I wash my hands in the correct bathroom. But I ran out. So this is the very first mistake that I made. Like don't like pay attention to where you're going to the bathroom before you give a talk. Like I recommend you go to the bathroom first. Just please pay attention to where you're going. So anyway, this is one of my first mistakes. Second mistake, second one, I want to talk about is my tender parents. So I mentioned earlier that, you know, I tell all my parents, I tell my parents what I do. I tell them all about the programming stuff that I do and all the problems I'm solving and all this stuff. But there's one thing about my technical career that I have never told them. And that is that everybody knows me by the name tender above. I have omitted this fact from our relationship. So I was invited to give, I grew up in Salt Lake City. I was invited to give a talk in Salt Lake City. I live in Seattle. I used to work with a conference organizer and he kept inviting me year after year. He's like, please come get a talk at our conference. And I always say, no, I'm not going back to Utah. Mainly because like, I had not much against Utah since I grew up there. And, you know, I go home for a Christmas or Thanksgiving every year and that's enough for a year. I don't need that. I don't want the year. It's fine. So he's like, please come even talk. And I was thinking, I was like, you know what? I tell my parents what I do. I really like them to actually see me give a talk. So I said to the organizer, I was like, okay, yes, I will come give a talk at your conference. But under one condition, and that is that you reserve two, you have two tickets. I need two extra tickets for my parents. And of course the organizer was like, absolutely no problem. So I'm like, okay, great. Go to the conference, meet the organizer, you know, my parents are there. We all meet the organizer and he's like, oh, hey, we have three seats reserved for you down at the front, down at the front. And like, this is right before my thought. I'm like, okay, great. We all go in, go down to the front and there's three seats reserved. There's a sign on each of the seats. And the first one, the first one says tender love. The next one says tender mom. The next one says tender dad. And I'm just like, everyone here knows me by this name. People will ask you about that. Just don't worry about it. Just be cool, please. So he taught me it was fine and they haven't asked me about it since then, which I think is good. Anyway, so I guess I'm not sure exactly what this mistake was or that I probably should have told that it's told them that beforehand. I shouldn't have omitted this name for so long. But I did and I paid the price. So final mistake I want to talk about. So I was going to a conference and I'm not going to tell you what conference this was. I was going to a conference and my wife was coming along with me and she packed so much stuff. I don't even know why. Books, books, books on design, tons of books and stuff. Are you going to set up a library there? What are you doing? We're only going to be there for like two days. You're not going to read this. Just tell it. Anyway, so I'm giving her a hard time about how much stuff she's packing. And I'm like, yeah, I mean, check out my bag. It's super light. This is fine. Like, what, you know, why can't you pack this lightly? Anyway, so I'm giving her a hard time about this. When we get to the get to the conference, everything's fine. I arrived the day before. I was the first talk in the morning and we go to bed, get up in the morning, go to take a shower, take a shower, open up my clothes, time to get dressed. I am missing underwear, completely gone, none in the bag. And I was like, oh, this is why my bag is so light. I see. Wow. So, and I know the things that they tell you is you're supposed to imagine everybody else in your underwear, like to make yourself feel more, you know, feel more calm on stage. And like, I was, I was like, experiencing this in reverse and opposite, like, on stage without any underwear. I don't recommend this. Like, please don't do this. It's not like, make sure you pack everything. So this was a huge mistake on my part. Make sure you pack everything. There was actually a sports store nearby. My wife went out and bought a bunch of bought some underwear for me. Unfortunately, it was like, you know, she had it for me right after I was done. I was like, Oh, thank you. I appreciate that. And she was like, Oh, so I packed too much stuff. Anyway, so mistakes are just fine. Like, I made all these mistakes, public speaking. And I'm still alive. Like, it's okay. So you can come up and give a talk, make a mistake. It'll be fine. You'll approve. I know from now on, like, I'm not going to hide that my name is Cinderella for my parents. I will pay attention to the bathrooms that I attend conferences I attend. I will also pay attention to making sure that I pack everything. But I've learned from all these mistakes. Recently, I lost a passport. I can tell you about that later if that is horrible. Anyway, so I was thinking to myself this conference, you know, keep Ruby weird, keep Ruby weird. That means that means Ruby is already weird, right? Like, if we're keeping it that way, and I was thinking to myself, is Ruby weird? I'm not sure is it weird? Is it weird or not? So I started looking at the language. I was like, what does this mean? What does this mean by weird? So I started thinking about the language, like, you know, well, okay, let's compare this to other languages. So I started looking at other languages. This is a this is a language called anti. This is this prints out Hello World. It's all this is the code here. So you can run that prints out below the world. It's great. So Ruby doesn't seem too weird compared to that. Here's a here's another language called pi. I'm not sure how to pronounce it. This prints out the name of the language, but it's interpreted. So the interpreter reads this image and gets its instructions based on the image. So this is I mean, this is a pretty weird language. And of course, like, I have to mention this one, everybody knows everybody knows this one. This is this is also a programming language here Hello World example. Another one, another one, one of my favorites is white space, white space. My favorite one. I thought this is a Hello World program. Or is it? If you look at Ruby, like, here's like, here's a program in Ruby. And I look at this and I was like, I don't think Ruby is weird. It's not a very weird language. Ruby is pretty nice. And then I started thinking about other languages that I programmed in, like for example, Java. Here's a Hello World in Java. And then and then like C++. This is not not super exciting either. And what I think is interesting about this is if we look at, you know, I try to put this on a scale is like scale of weirdness. And, you know, Ruby is here in the middle of like our perspective is from, you know, if we look at Ruby, we all look at we look at this through Ruby eyes and we say like, Oh, man, those two languages, those languages are weird and white space in there, but well, it's there. So you know, those languages are weird. But if you think about Ruby from the perspective of like, these languages, I mean, I used to program Java every day. And when I was used to that programming language, or when I was used to those languages, looking at Ruby, Ruby was weird. It was weird coming from that perspective. Right. So it depends on how you look at it. It really depends on your perspective. Like, where are you coming from? Where, you know, where are you coming from comparing comparing something to where you are today? So coming at it from say a job or a C++ person, maybe this, maybe this language is weird. But you know, all those people who write white space for their day jobs, they don't think Ruby is weird at all. Tap have space only to keep it. What should make a white space keyboard? What was the language I had a special keyboard? There was one. APL, thank you. Yes, yes. We should do that before white space in two days. That's better. So then I was thinking, well, Ruby's not very weird. I don't think the language is weird. But what about the people? So let's think about, let's think about the people I was thinking about my past experiences as a programmer. When I started programming, this may be a surprise to you, but when I started programming, I was not a very good programmer. I suspect many people when they start programming are not very good programmers. So the first language that I was ever paid to do was Perl. I was a Perl programmer. I like doing Perl a lot. Ruby was kind of strange. I was on the Perl, what was it, the Perl five quarters list. I would mail there. People were not super nice to be there. I was new. And it was not exactly that great to be in. Although one, there was actually one speaker who or one person in the Perl community that I really, really looked up to. Damian Conway is one of my favorite, favorite Perl people. I take a lot of inspiration from him. But this, this community, I would not say it was very weird at all. It was just, you know, a group of people that were on mailing lists and, you know, nothing, nothing super exciting about it. And then after I, you know, I was a Perl programmer for maybe, I don't know, four years or so, and then I became a Java programmer. I was a Java programmer. Don't tell anybody this secret of mine. I don't think I've told my parents this either. Just kidding. I was, I didn't do that. They knew that. And so I was thinking about, what about, what about the Java community? What Java community? So I mean, when I was a Java programmer, like this, we're laughing about it now, but really there wasn't anything. I wasn't part of any mailing lists. I mean, what if you, as a Java programmer, like what, where would you go for community? What would you do? I mean, you go to Java one, I can't afford that. I can't afford Java one. I mean, back then this would be maybe, this is over 10 years ago when I was a Java programmer. Back then there wasn't really much, you know, there wasn't much of a community. This community thing wasn't really a thing. I don't think. So I was thinking about this. And I also thought about the Python community. I'm not, I was never a Python programmer thing. Like recently, maybe I don't remember how long ago one of the Django core team members said to me, Aaron, you should give a talk at PyCon. And I was like, me give a talk at PyCon. And he was like, yeah, you should give a talk at PyCon about, you know, comparative trust, Rails and Django. You could talk about why Rails is better than Django. And I was like, well, I don't actually know Django at all. So it seems like a bad move for me to get in front of a bunch of people and tell them why Rails is better. But I asked him, I was like, you know, PyCon, obviously many people must bring PyS to this conference, right? Like this seems like a thing. And he was like, no, nobody's ever done that before. I'm like, are you freaking kidding me? PyCon? How could you not? That's amazing. And I just, I thought it was a strange interaction that, I mean, doing something like that would be pretty common, I think, at a Ruby conference, but maybe not so much in other communities. Anyway, so I became, after being in Django program for a while as extremely depressing, I became a Ruby programmer who was less depressing. Everybody was doing it as a hobby. Everybody was doing this just as like their fun language. And what I really, really liked about the Ruby community is that it valued creativity very highly. I mean, back then, like I'd started doing Ruby, and then after a little while after I'd started doing that, why I came out with this point guide, and I was like, wow, this is amazing. I've never seen this type of stuff with other programming languages. This community really values creativity. The other thing that really struck a chord with me is how friendly people were on mailing lists and stuff, and mailing lists, IRCs, or IRC, like I could ask stupid questions and it was fine. Nobody cared. They would help me out. And I think this is really important because it turns out, it turns out, I will tell you this from personal experience, it turns out that helping people is fun. It's actually something fun to do. And it's fun because once you help people, those helped people help other people, and you can see it grow. It turns out if we help each other and the community gets better, it's actually a more fun place to be, interestingly. So what I really liked about this community, again, was that mistakes were just fine. It was fine for me to make mistakes. It was fine for me to screw up. People would help me out. They would tell me the right way to do something, tell me the better way or the good, correct way to do something. So that's one thing I really liked about this community. So again, I was thinking about this from community weirdness perspective, like maybe, you know, well, Java didn't really have communities per se, but again, it's about perspective, right? It depends on the community that you're part of. It's all about the perspective, where you're coming from. The, you know, obviously the white space community thinks that we are not a very weird community, right? You are all on the white space mailing list. It's hard to read mail. Anything, anyway, what I really liked is that we value creativity so much. They'd be very happy to be here. So now I want to talk about homeopathic code optimizations. This is a, this is a new technique that I've been pioneering. We all know about the facts of homeopathy and how they help people, right? We all know about these facts. So for those of you that don't know about it, I'm going to explain what it is so that you can know too. And what is homeopathic? It's about diluting stuff. It's about a diluting stuff. So very, very small, okay? So as any good researcher does, I went to the Wikipedia page and it was like way too long. So what I'd do instead is because homeopathic is about diluting stuff, I figured out, well the best way we could do this, we'll take this, highlight it. If you click on, if you right click and you go to services, there's this thing there, summarize. You do that. And then I just dragged that down into one liner and I was like, oh yeah, there we go. There we go. I'm not sure if this is dilution or compression, but I'll call it dilution. So this is dilution, right? So the important part to take away from this is we dilute stuff and also we dilute it in water. And water apparently has memory. It's pretty amazing. I know this water has memory and water will remember the substances it's mixed into. I love Wikipedia's editing. I love quotes like that. Anyway, so water has memory. And I was thinking to myself, you know what? If water can have memories, can white sprays have memories? White sprays have memories, do it. And I thought for sure, yes, absolutely white sprays have memories. The answer is yes. So what I would like to do for you today is I'm not sure until when I'm going, but I want to do a demo. I'm going to do a demo. So I wrote a homeopathic code optimizer and I want to demo it for you today. So we're going to do that. We're going to do that now. Okay. So let me shut off my display mirror in here. Okay. So Fibonacci sequence, because that's what I always test things with, it's the best way to get, the Fibonacci sequence is the best way to get the performance of any virtual machine measure of performance to do is the perfect benchmark. All right. So anyway, here, we all saw, is that big enough? Is it big enough? Okay. Everyone can read that. Cool. So here we have terminal two. So we'll say like, I have a script called dilutes. Is this everyone can read this too? We good? Okay. Cool. And then we have Fib. So we can run Fib and it'll give us the, it'll give us the value back. All right. So that's, that's the value of the Fibonacci sequence. So I can take and run the dilute program on the Fibonacci sequence. There's, so there's the diluted version. You can see, you can see some of my characters missing, right? Now, now the white space and the virtual machine together, they remember missing characters, they remember. Now this is running at a 10% dilution, right? And you'll remember, you'll remember from the slides, the maximum, what we want to do is from the summer, you want to dilute it by six times. But here, let me show you this. We'll pipe it to Ruby. Like it still runs, still runs, gives us that gives us the value. So we know, like the VM and the white space together, they remember these values. We can even pipe them together. So let's say like, all right, pipe, dilute. So it dilutes it even more. Each character, basically each character has a 10% chance of going away. So that's still runnable. We can still pipe that to Ruby and run it. So, yeah, we're still calculating the Fibonacci sequence. So we'll do it like, we can do it like, okay, let's do it six times. That's one, two, three, four, five, six. So this is the optimum one. This is the optimum dilution rate there. And we can still, okay, is it still runnable? Yeah, okay. So we can still run it. I want to prove I'm not messing with you at all here. This is true, true. There's no, there's no trick involved. Okay, this is just the science, the science of pulling all the things. So I'll change it up here. Let's change it up just to prove it's real. So we'll say like self.fib, all right. And we can say, oops, there's a dot there. And let's do, let's do like 35. So we can dilute that. We'll dilute it. So it's still, you know, I changed that. So we got, you can see the class there. And of course, the white space remembers as a class and just pipe that to Ruby. And we're still, this might take a little longer. All right. So we're still calculating, still calculating the Fibonacci sequence. So it works. And it's amazing, right? Okay. Oh, thank you. Anyway, so how does this work? Like, how, how are we doing this? Well, as I said, as I was mentioning earlier, the way that this program works, is that the virtual machine actually remembers the code. It remembers. So what we have there is not white space, it's memory. That's what we actually have. That's what we're actually producing here. What's interesting too about this language is that, or about doing homeopathic code optimizations is that actually, like, if you run it enough, it actually goes into the white space language. It actually turns into a white space language. I'm not going to do it, like, I'll just run the video here. So we run it. Okay, so I added a dilution ratio. So you can say D 50 C, I don't know if any of you know about homeopathic, but 50 C is like, that's the unit, extraordinary unit that is. You can do like 100 C. And I pipe it through it, it's all white. So that's a trend. It still runs. It still works. So the benefits of this, the benefits of homeopathic code optimizations is it's faster. And we know this. So we know this. The reason we know this is it's because of this axiom. No code is faster than no code. So if the code is going away, then it's got to be faster. It's not there anymore. This is, we know this. So the more diluted it is, the faster it gets. So I want to share, I want to share some benchmarks with you. So let's, you know, I'll just run the video. So just time it, simple time, we're on Ruby on our normal Fibonacci sequence. And then we'll do the same thing with the diluted version. Type that to root, well, okay, write it out to a file and then run the file. Because we don't want to get the dilution processing time, right? Okay, maybe it wasn't faster that time. It's usually faster. So the other, the other benefits are it's more maintenance. Obviously, I mean, there's no code to maintain, right? Less is more, less is more. Anyway, with that out of the way, I want to, I want to finish it off here quickly. Keeping Ruby weird. So I really want like, I'm really happy to be at this conference. The name, keeping Ruby word weird means so much to me. I love doing weird stuff with the language. I love doing, you know, different creative things or making mistakes. And I want to make sure that our community mistakes are okay, but that we can rely on the community to help us out, help us out and fix these mistakes anytime we do mess up. Or when we do do something creative, everybody long laughs about it or, you know, we all participate in this together. So I think one problem that we have is I want to talk about one problem that we have and then how we can deal with this. I was talking about Ruby of the past when I started to be a Ruby programmer. Back then nobody was paid to do Ruby and we were trying to help each other out and actually get paid to do this. We wanted to bring more people in. But today, the fact is Ruby is a popular language. Many people use it. Many people are paid to do Ruby, right? People are paid to do Ruby today. And some people are just here for the money. It's just a job. I mean, I'm sure you work with people like this. I do, for sure. They just program Ruby. It's their job. What's even more interesting is that our community is so big now that there are people who don't actually want to program Ruby during their day of job. They come to work and they're like, Oh, man, I don't want to program Ruby. I don't want to do it. I want to do something else, right? They want to program in some other language. And it's just that our community has gotten that big. The thing is, though, I think that the weird is still here. We still have this weird, we still have these attributes about our community, but I'm afraid that it could get diluted as in our earlier example. So what I really want us to do, what I really think that we need to do in order to keep this feeling of a weird community is we need to rally around the positive voices that we have in our community. And you're going to be seeing a lot of those today, a lot of the other speakers that are coming after me. We need to rally around these people. So in closing, maybe Ruby is weird, but I don't want to change that. I want to change everybody else. I want to make everybody else weird. So that is my talk. Thank you very much.