In this video, we provide the solution to question number five from practice exam number two from math 1050 In which case we have to solve the absolute value in the quality the absolute value of 5 minus 2x is greater than equal to 1 Some things to remember with absolute values absolute value is never negative It's always positive or zero Therefore if you have an absolute value that's greater than equal to a negative Then you'd get all real numbers that also be true if you had zero because again absolute value can't be smaller than zero So we could have all real numbers That's not happening in this situation. You should also be cautious that absolute value can never be less than or equal to a negative You'd get no solution Similar things happen there now. That's not the case on this exact exercise here We just want to be greater than or equal to one so what we can do is we can consider the two cases There's the positive case where five minus two x is greater than equal to one or There's the negative case where you have five minus two x is less than or equal to negative one We do have to flip the sign in the negative case like so and then we proceed to solve these these two inequalities They don't exactly overlap But nonetheless the process of solving it's gonna be the same and by the in either of the two cases You're gonna subtract five from both sides On the original positive case then you end up with negative 2x is greater than equal to negative 4 and then in the Original negative case you're then gonna get negative 2x is less than in this case negative 6 Now we're gonna divide both sides. We'll both inequalities on both sides by negative 2 What's good for the goose is good for the gander and which case in the end? We end up with x is because we divided by negative 2 the sign will switch around so we get x is less than in This case a positive 2 or in the other case We're gonna get x again. We divided by negative 2 so it flips the inequality round x is greater than 3 Negative 6 divided by negative 2 is a positive 3 So we want x is less than 2 or x is greater than 3 the first inequality here Does become an interval negative infinity to 2 inclusive because we do have We're allowed equal to 2 less than 2 or equal to equal to 2 the or symbol or I should say the or here means We're taking a union and then we want also x is greater than or equal to 3 so bracket 3 towards infinity That would be our solution in that situation For which then we can quickly see that the correct answer would that be choice a


So a month ago, I made myself a challenge and I challenged others to use nano for a month. And for those of you who use nano, I challenged you to use Vim for a month. And it has been a month. So I want to make a video about my experiences with nano. And I want to be very, I should say, I want to be as fair as possible with this because I could get all ranty as I usually do. Vim is definitely a word.  And I'm sure that the title that I'm going to use and the thumbnail that I'm going to use is going to spawn some outrage because it's YouTube. You kind of have to do that kind of stuff in order to get people to click on your stuff. So I apologize in advance for that. But the point is, is that I've used nano for a month and I have some thoughts. So let's go ahead and talk about that today. Before I do, if you would be so kind as to leave a thumbs up on the video, it would really help the channel. So let's talk about nano and my experiences with it. So first off, let's start off with positive things about nano. I want to start off very positive because I think that it will be better overall. So here I'm just going to, instead of you guys looking at my lovely face, I'm going to show you my nano setup. So I have spent the entire month making nano the way it is. And so I've turned on syntax highlighting, I've added numbers, I've removed the stupid bar at the top, I've changed some of the key bindings. I've made it as much my own as possible. So I have completely used nano the entire month. I will admit to have using them three times when I wanted to use some of my key bindings over there that I really needed to do some like really fast edits that just wouldn't have been nearly as easy in nano. So there were three times that I cheated. So I'm going to be completely honest that, but other than that, I've used nano the entire month and there are some good things that I like about nano. First off, it is very, very simple. I think that that is the best thing that I can say about it is that it's very, very simple, very, very easy to use. And once you get used to it, it makes it very easy to hop into a document or a file or whatever, make your edits and then get about your day. I will say that for nano. It is very, very simple, very, very easy to use. If you are brand new to the text editor space, it is way easier, way easier to use nano than it is to use them. If you've never used a text editor in the terminal before, nano is by far the easiest to get a hold of because it's for the most part intuitive. And if you can't think of what one of the key bindings are by default, there's a little help strip that I've gotten rid of along the bottom that tells you exactly what the key bindings are that you'll need to know. It's very easy to use. I will also say that it is very easy to configure. The configuration file, which I'll show you here. This is the configuration file. It is very easy to configure. So if you want to make it your own, you can very, very easily. And it's not a syntax that you have to learn. If you were to configure VIM, you have to learn VIM script or you have to learn Lua if you're going to use new of them, right? You have to learn some kind of, but is basically a programming language in order to do things inside of the VIM configuration files. Whereas with nano, you don't have to learn any of that stuff. All the stuff is not only very well commented, but it's easy to understand. So if you didn't have the comment here for auto indent, you would know what set auto indent basically meant, right? You wouldn't need the comment. Same thing with set backup. You can have an idea of what that is. Whereas with VIM, not only in VIM is there a language that you have to learn a lot of times and I'd say all the time VIM has 12 different ways of doing something. There are, you know, multiple ways of setting a key binding. There's multiple ways of setting VIM options and all of the stuff. And while that is good for Tinkers, it's not good for people who just want to get in here, make one change and then leave. Nano is much better at being a configuration file that is easy to look at, easy to change, easy to learn, and then easy just to leave behind once you've set it. There's not a lot of tinkering here that you can do. So you don't have to worry about plugins or any of that kind of stuff. You don't have to worry about plugin compatibility. You don't have to worry about any of the other nonsense that VIM brings along with the table. Now there are outside things that you can add to nano. So I don't want to say that there are no plugins. There are technically things that you can use inside of nano that are kind of plugins. Most of them are like quasi forks of nano. It's a complicated mess because nano is not really meant to be extended unlike them, which is actually meant to be extended. But the configuration file, like I said, is very, very simple, very easy to use. And I think that that is a very good thing. Another thing that I will say about nano is that it does a really good job of inheriting colors from your terminal. It doesn't always do this. I've found in some configuration files that come with some distros. The colors are pretty much set to whatever the distro wants. But if you use the default configuration file, which is basically what I have here other than a few tweaks, it does a good job of inheriting the colors from your terminal, which is good if you change themes as much as I do. So I just changed colors and you can see the color scheme was inherited automatically. I didn't even have to leave nano and come back, which is not something that VIM does as well. And but it takes some setup in order to get there. So that's another thing that I really enjoyed about nano. So those are the three things that I have to say would are positive. Then I have some things to say that are negative. And I want to put some provisos on the things that I'm about to say. So really, all of my complaints come down to this one simple fact, nano is not VIM. Okay. Now, I know what you're thinking, man, of course, nano is not VIM. If nano was VIM, it would be VIM. It wouldn't be called nano.  And I don't, I didn't think that nano was VIM, I'm dumb, but I'm not that dumb. So I knew going in that nano was different. I've used nano before this challenge. I'll probably use nano after this challenge, you know, for various things. But as a VIM user, I was able to get so used to doing certain things in a certain way. And more specifically, I got used to doing things in the VIM way. And all of my complaints with nano stem from the fact that it does things significantly different than VIM does. All of them. Like there is not a single thing inside of nano that is the same as the way it is done in VIM. There are no modes. So the first thing I always do, and even a month later, if I'm in a document, the first thing I always do, and I want to start typing, I usually hit I. If I don't want to start typing on that line, you'll see me, you've probably seen me in videos do this a couple of times, you know, I'm, and I'm so set in my ways that half the time I'm not even looking up there at the top line where it's making the changes.  And I'm wondering, especially the first few days, I was like, why isn't this thing moving? I mean, because I had, at that point, I had managed to make it look like if you looked at this right now, you'd think that this could be VIM, right? And I'm sure some people actually thought, Matt, you're just using VIM and calling it nano. No, no, this is actually nano. But the thing is, is that I, after a few days after I made it look like this, I kind of forgot that I wasn't using VIM and I constantly forgot kind of, and that kept me doing this nonsense. And to this day, a whole month later, I still, still do that every single time I open up a document. So that's my biggest complaint is that it's not VIM. And honestly, it seems unfair to criticize nano because of it not being VIM. It's not big. It was never said to be VIM. It's never said to compete with VIM. It's not meant to be VIM. Any way you want to put that sentence, nano is not VIM and it wasn't supposed to be VIM. So criticizing it feels wrong, right? I shouldn't say, well, you know, it's really hard to make multiple changes per line because it, you know, it doesn't have a visual edit, you know, visual block mode. It doesn't have really good macro support. It does have macro support, by the way, it does. It's just not as good as VIM. So, you know, it, it feels unfair to say negative things about nano because, like I said, all the negative things that I have to say are because it's not VIM. That being said, I'm still going to say them. Of course I am. So the first one that I want to talk about the negative is that visual mode does not exist. And yes, there is a way. So if you hit shift and then go down, this is obnoxiously simple, right? If I wanted just to delete those things, I could do shift and arrow keys and then if I wanted to delete those, control K gets rid of those, right? And that's fine. It is obnoxiously simple, right? And if you have used a word processor ever in your life, you know, that shift and arrow keys highlights multiple lines. But I didn't figure that out for like a week. In fact, I didn't figure it out at all. Someone pointed it out to me after I made my configuring nano video. And you have no idea how embarrassing it is because that is very, very simple and it's very, very obvious. But I didn't get it through my head thinking I thought that there was some, you know, special, ultra complex way of basically doing visual mode, which is this is basically visual mode, right? I thought that there was some complex way to do that, but there's not. It's just shifting the arrow keys. That's all it is. It's very, very simple, just like a word processor. So that's my first and honestly, probably my biggest complaint is that the thing that I missed most about them was visual mode, because I can't tell you how often I during the day have to select multiple lines to either make changes or delete or paste or yank or whatever. And the way you do that in nano just feels wrong to me. I tried to make it better by changing some of the key binding. So if I wanted to get rid of these few lines here, you know, the shift in the arrow keys, I got used to that. That was fine. But if I wanted to cut these and then paste them in another, you know, another place, it's not as it doesn't feel as fluid to me as them. But again, go back to what I said before when I got into this negative aspect of nano, the reason why it doesn't feel like it doesn't them is because and say it with me, nano is not them. Okay. And it's taken a month for me to, I mean, again, I know that nano was not them. So, you know, I just, my brain seems to forget that nano is not them for some reason, and that's the reason why that this part here has bothered me so much because it just, they do things in a different way. The cursor, you know, you can change where the cursor paste things when you use the paste key lining, just like you can in them. It just still feels different to me. And I don't, I really can't even explain it more than that. So visual mode is one of the negative or lack of visual mode. And the ease of use of that visual mode offers is the first negative of of nano, which again, I will reiterate the fact that it is unfair to criticize a piece of program because it doesn't have features of another program, especially when they're not trying to be the other program. I understand that it's not fair. And I'm not saying that nano is bad because of these things. Okay.  So just understand where I'm coming from when I talk about the negative things of nano aren't really negative things of nano, but, you know, because it's not them. So the second thing that I want to talk about in terms of negative things is that it doesn't do a good job of syntax highlighting. Now, it's possible that I messed up the syntax highlighting because it does have it and you can add it. It's actually natively built in now as far as I can tell. Because you can there's a setting here for syntax highlighting. And there is, I think, something else that you can add to make it better. But I never looked into that I should have. But by default, the syntax highlighting looks like this. And as you can see, it's two toned. OK, there are some some of this is just because of the color scheme of that that firewall has chosen this time. But even if I choose another color scheme, you can see it's kind of two toned. There are three different colors here that it will use. And again, a lot of this is because of the color scheme that I'm using through firewall. Some of the firewall colors do OK and are more contrasty. But when you have syntax highlighting in them, it seems to be somewhat consistent, right? And it is in nano two sometimes. But because it only uses the three colors, three of the eight colors that are on offer, at least, it gets really samey, right? And they're they're not varying colors. All these are varying shades of red. And sometimes you do get some more contrasty, depending on what color scheme you're using. So I'm not completely criticizing it. But I've noticed more often than not, no matter what color scheme I'm using, they do tend to be kind of samey. And if you're going to make a syntax highlight, you know, functionality in your program, differentiating with contrast makes it easier for things to stand out, right? I don't think that that's a nano problem specifically. I really, really don't. I think, again, this is mostly because of my crazy color schemes coming through firewall because I get it sometimes. Well, that one's actually kind of worse. Sometimes I'm basically switching between color schemes to try to see if I can find one that is actually a good. Option for showing when it does do contrasting, right? But this one's actually about the closest that it actually does show some contrast. So apparently the wallpaper that it's basing on has some more contrast, which is actually a better thing. But as you can see, it does.  So again, I'm thinking that this is more of a pile of problem than a Nana problem, but it is something that I noticed. Another thing that I really missed, and I'm going to call this a bad thing, but it's again, mostly down to the fact that it's not them, is that I missed splits. So I didn't think I actually used them splits all that often. But because Nana doesn't have those, I realized that I actually do use them quite often and I missed them. So obviously you could use micro micro is a more advanced version of Nana, kind of it has a lot more features and that has splits. I could use a multiplexer if I wanted to do that, or I could just, you know, open up another terminal and that'd be, you know, Hunky Dory. But, you know, I do tend to use splits because the buffers, especially the clipboard buffers, usually go between both splits and it's much easier to copy and paste or yank and paste or whatever things from one document to another when they're in a split. And that is something that I really mightily struggled with when it comes to Nana. So another thing that I found annoying and I talked about this in my configuring Nana video is that the default key bindings are bad. So one is what I'm specifically talking about are the copy and paste functionality. So by default, the cut is control K and then the pay the paste, I think is control you. I don't actually remember because I had to change it. The default key bindings were bad. And then you come down to this section here in the configuration file and the options that they give you by default. So they're the first one here and you won't see it because I've already changed it. Is this one here bind and then by default, this is control X and then that cuts and goes into the main buffer. The problem with control X is that control X is also the easiest way to actually exit nano.  And so I did this the first time I changed this. I just decided to leave it as, you know, control X because control X is control cut system wide and it makes sense to have it be control X. But control X is also, like I said, the best way to exit nano. So I ended up coming up with a different key binding. I use control B and that's worked. But it's also feels weird because control X is supposed to be cut. And honestly, I could have I should have made it control D now that I think about it because that would be more Vim like. But I didn't think about that till right now, which is weird. But anyways, that the default key bindings are kind of a mess all over the place. And the ones that they suggest you change them to in the configuration file, you know, because they're supposed to be more, you know, word processor like are very they conflict with some of the things that you would normally see along the bottom and the help section, which you'd expect them to.  It was not easy to get used to. So that is not necessarily a nano problem, but it's something that I really, really stumble over over the course of the month is trying to perfect the key bindings as much as possible. And some of them I've left the same. Some of them I've just commented here so that they're different than what the defaults are, you know, like I've changed the search binding, I've changed it so that the undo and redo or typical Z and Y I've changed the cuts and the exit and all that stuff. You know, it's just I've tried to make it my own as much as possible. And even a month later, I'm still having a hard time remembering these key bindings. I probably should have left the help on because I'm assuming that if I leave the help on, my altered key bindings will show up in the help. I never actually tested that out. I probably should have. It might have been easier for me to leave the help on, but asking for help is not apparently all that easy. So those are my main kind of qualms with nano. And like I said at the beginning, all of them, every single one of them have more to do with the fact that nano is not VIM than anything wrong with nano. Overall, nano is a fantastic text editor. Those of you who use it, I have all the respect for in the world. It's a very good text editor and it does the vast majority of things that VIM does just in a different way, right? It doesn't like if you take just stock VIM and you take just stock nano and you compared the features of the two, they're somewhat similar. I won't say, you know, feature for feature because obviously them can do more and can be extended and configured to do more. But out of the box, they're very similar. Obviously, one is more complex than the other, but and this is going to be my overwhelming point for this entire review. Nano was just as complicated for me as VIM is for people who go from nano to VIM. So what I mean by that is that if you have been a nano user for 30 years and you're going to go use VIM for the first time or, you know, whatever, you're going to have the same experiences that I had going to nano from VIM because they're different things. And I think that one of so in my many years of criticizing nano users for it being too simple, too noob friendly, and I have made sniping comments to those effects before, mostly tongue in cheek. I really don't care what you use as long as it works for you. That's really all that matters. But in fun, I always make fun of nano users for what I thought was good reasons because nano is simple, nano is not VIM. Nano doesn't have all these really cool, nifty features that VIM has. But in all honesty, the biggest issue that I think a lot of people face going from one to the other, no matter which way they're going is that they're just different things. Masquerading is the same thing. So they're both text editors at their heart, but they're not the same. They don't have the same workflow. And honestly, it's hard to move between them, right? It's hard to be a nano user and go to VIM because the workflow is different. It's hard to move from VIM to go to nano because the workflow is different. I'm assuming if I were to give nano or Emax a real try, like actual vanilla Emax without turning on evil mode or any of that kind of stuff. If I were to do that process, I'd have the exact same experience that because the workflow is different. So your experience with a text editor is going to very much depend on which one you started off with. If you started off with them, if you decided you're going to jump right into them, you're going to get entrenched in that ecosystem if you find that you like it. Once you're there and you're entrenched, it's really, really hard to leave. And I think that if I were to have started with nano and was used to nano, I had it all configured the way I wanted to. I had all the keybondings memorized and it did the things that I needed it to do. I think that I would have as much a hard time leaving nano as I had leaving them. I think that that is absolutely true. And I just think that overall, the whole editor wars thing would be much easier if everyone tried all of them and gave them a good college try because it's much easier for me now to empathize with people who use nano than it was before. And I think that I have grown from using nano for the last month. And I think it's going to be harder for me to make the comments that I used to make with regards to people who use nano now that I've used it for a month. Now, a month is not a long time. It's not as if I dedicated myself to a whole year of using nano. But I do feel that I have developed a regard for nano that I didn't have before, which can only be a positive thing, I think. So the last question I have to answer is, Matt, are you going to continue using nano? And the answer that is hell, no, hell, no.  I know all that stuff that I just said, and that has no impact on me saying that nano people are fine to use nano. And I understand now why they use it. It's just is definitely not for me. I miss them immediately after I stop recording this, I'm changing my aliases back to them. I'm making sure my end Vim setup is all the way it needs to be. I'm changing the theme so it matches my pie wall. It's going to be glorious. It's I'm going to go write some bash scripts or something just to get in there.  And I'm going to do all of the things it's going to be wonderful. And I'm never ever going to want to use nano for any stretch of time again. But again, not because nano is bad, but just because nano is not them. And Vim is my thing, apparently, it's where I was meant to be. So that is it for my month long experience with nano. I hope that you've enjoyed this video because it takes some self reflection to know, you know, that you have certain preferences and you want to speak objectively about certain things. I think that I try that I've tried to do that in this video and throughout this entire experience is to go into this with open and open mind, trying not to think that everything that Vim or that nano does because it's not Vim, that everything that does differently is bad. So I've tried to keep that open mind. I hope that I was as successful as I think I was. I probably wasn't, but we'll see. Anyways, if you have thoughts on this entire challenge, leave those in the comment section below. Please, please don't recommend any more challenges to me right now. I don't want any more. Please don't challenge me to use Emacs. Don't challenge me to use Micro. I want to go be very happy with them for a while. Maybe I'll go challenge myself to one of those other editors some of the time. For now, just leave me and Vim alone. We have some things to talk about. Anyways, if you have, don't take that the wrong way. I just realized how that sounded that was not that that didn't. Anyways, if you like this video, give it a thumbs up. I would really appreciate it if you did. It would really help the channel. You can follow me on masses on our Odyssey. Those links will be in the video description. You can support me on Patreon at patreon.com slash the Linux cast. You can support me on YouTube and Liberapay as well. Those links will be in the video description. Thanks to everybody who does support me on Patreon and YouTube.  Without you, the channel just would not be anywhere near where it is right now. So thank you so very, very much for your support. Seriously guys, every single day, I thank you. And it's just, it never seems to be enough. So just as much as I can, thank you. Thanks everybody for watching. I'll see you next time.


Stevenson gets the 11-8 win the night over York College here at Mustang Stadium, Glenn Clark with head coach Paul Cantabene. Coach please tell me that you were filming your halftime speech and that we will be able to replay it forever. What changed from half number one to half number two? I really didn't think we played that bad in the first half, you know, I think defensively we had a really good game plan. Coach Paul did a great job and I thought we can guard them, you know what I mean? So I thought we did a good job and Mark was really on tonight. You played well. I thought both keepers played really well and made some good saves. Excuse me there. And Hanson in the big game gets you kind of going a little bit. But I thought our offense was struggling a tad, you know, just because they were really physical. You know they get out in, they weren't really calling anything and they're sort of really physical in doing that. But I got kind of on them at halftime a little bit and I think they're a prideful group. You know they really do a good job offensively prideful and they made some really tough plays in the second half and then that third, start that third quarter. So once we got, they got a little life and going there and I mean like just look at the goal that Dylan Linhart scored there in the man up. He gets crushed by a kid, turns around and sticks it. So those are the kind of plays that win big games against nationally ranked teams because you got to make tough plays to do that. So I thought we made a lot of tough plays in the second half and it really paid off and we made them follow us and I think, you know, that's the difference between winning and losing. We don't make some of those tough plays. We probably don't pull this one out.  And I think we cleared the ball a little bit better. You know, we had a couple of issues Tyler threw to the other team one time and we cleared it a couple of times a little bit better, you know, we might get out even more. So but that's a really, really good team because childs and them, they're great, you know, 15 and 44 are excellent and 28 and four, you know, they're good, you know, they got some guys and so, but we're happy to get the W and we'll see them in two weeks again right here most likely and so, but I'm just proud of what they did. I didn't really say much. I think they themselves understood that they had to play better and they're a prideful group. So we're calling Dylan Linhart Lionheart because he was getting his butt kicked all night, but he showed a lot of heart throughout the course of this one. So let's talk about a couple of things. You mentioned Mark Paust. I think we talked the last time about what Mark's been through this season and the emotions night of it being senior night and for him to step up when you needed it badly in the first half for him to make those saves and keep you guys in this one, what else can you say about him? Well, Mark, you know, he's just such a great person, you know, and going through his father passing away and us trying to rush together because in Messiah cancelling the season and put some senior day together and get his brother down here was great and wish we could have got his mother, but it's just too much of a turnaround for that.  His dad is such a tremendous, tremendous person.  And, you know, he's just living the moment, living in the dream now. He's going to do everything he can to help this team. He loves Stevenson. He loves his teammates and I think he's really appreciative of everything we've done for his family and and, you know, he's just a special kid. Sometimes guys try behind the back goals because they want to get the sports center. Sometimes guys do it because they have to in order to score. And you got two of them tonight that were necessary. You got the one from Tatum earlier in the third quarter and then the closing seconds from Coleman there at the end of the third quarter. You know, other than they're awesome and they're fun and we can look at him and watch him forever. How important is it in that situation for an attacking player to know what they have to do? Well, I just think that, you know, both goals are really important. You know, they got an incredible behind the back goal at the end of the first quarter. And we're playing one should have been one, nothing. They get to grab the shot and puts it behind the back and scores. And he scores a one-hander later, you know, so there's like four goals here that were Sports Center top 10 highlight type things. And but, you know, I think it was a big goal at the end of the third quarter, Coleman getting that behind the back goal right there to get us going there because, you know, they're kind of pushing us a little bit. And to hit that goal to go up by two, I think at that moment was pretty big. And so I think that's it just happens. Those guys are talented as they have talented guys. And Coleman's the kind of kid that can do that stuff as is Tatum. No Tatum's behind the back to give us a second goal. That's a great shot. You know, I think and we're pretty good at, you know, time, place, situation for those. We just don't do them for the hell of them. You know, they had the freedom to do them, but those are both very critical. But how you end quarters, I think is very vastly important and to get one at the end of the third quarter there to kind of keep our momentum going. I thought it was a big one for us. Coach, I don't know what else to say. This was this felt like it meant more than just one win. This felt like an emotional big time game, ranked opponent. The whole deal. Congratulations on a massive win. And we'll see as we get ready for the postseason. No doubt. Thanks a lot. Have a great one. Coach Paul Cantabane, I'm Glenn Clark. Go Mustang Sports.TV.


I was terrified Hi everyone Welcome to the deaf core 101 session. I hope you all came for that for that session specifically if not, please stay don't leave No, that was a little while ago you were supposed to bring Yeah My name is Zagli Sigler. I work for Rackspace. I am also co-chairing the deaf core committee with Rob Hello, and I'm Rob Hirschfeld and I work for Rackend to start up doing physical provisioning I used to be the old crowbar stuff So today what we're going to do is we're going to give a quick intro to deaf core And then we'll have some really hard questions for you all or you can ask us and we'll have Sam answer them Tomorrow tomorrow we have two working sessions back to back. This is how Deaf core works It's all about the community and the work gets done in our meetings or if we meet in person We get them done in working group sessions in person so What is deaf core really about it's a Hopefully it's about user experience And we're here to represent them because if you if if I implement a version of open stack and Rob implements a version of open stack that you may not look exactly the same and The applications that Sam writes may not be able to work the same way on both of them So make some cry You could be speaker of the house With open stack being so huge How do we control and make sure that? One open stack is interoperable with another and I guess yeah, someone has to decide what's going to win and what's going to lose and Who's going to pick the winners and losers? Anyone anyone want to pick them? Anyone wants to decide which APIs will be required? Yeah, so That's the fun part and this is what deaf core committee tries to do and What we do is we try to get feedback from everybody we try to get feedback from everybody that speaks up Either in person email IRC or any other format that you can think of if you don't speak up We will not listen to you It's just the way it is you have to make sure that we know what it is That you have issues with or if you disagree with a particular API being required for interoperability then Someone has to tell us about it We're very anti-star chamber Right, we don't want you know a select group of people deciding how everybody's cloud should look right that's not open stack Right, which means that we might be hearing conflicting opinions Someone might say no. No, I really want this API owners like well, it's really an extension It should not be part of deaf core. It should not be required for every single cloud out there Even though it is someone's baby Just not going to be in the main core group of APIs So are we being fair about these APIs? Hopefully you can tell us All right, how many people know what deaf core is almost unanimous I'm I my job here is to spend as little time as possible educating the people who didn't raise their hand Okay, which is not very many people so This is the obligatory what is deaf core slide It's a process right that sets the base requirements for all open stack products, right so products With two pieces must pass tests and designated code Okay, and the definitions use community resources So this isn't external it's within the community and it drives interoperability for minimum standards And it's about products labeled open stack. So it's a branding component which one's forward All right So the things to parse that out a little bit deaf core is about commercial use Right, this isn't about I created a new project and I brought new code into open stack. This is about I'm selling Something using open stack. Okay, that's what we control. That's what deaf course for now It obviously echoes backwards, but that's what that's where where our jurisdiction is You just want to have your own great flavored open stack But not call it open second I have the logo for it and not sell it as open stack product Then you can do whatever you like Now if you're selling it open stack code and you don't want to use the brand That's actually problem for the board to deal with Because that means that people are using the code, but not actually claiming to use the code. It's perfect. It's Apache. That's okay But that means that there's something that says open stack as a brand is not valuable enough for you to feel like you Needed to use it. Does that make sense so? So there's a very virtuous cycle in here. So what does deaf core deliver? We have a process. We have artifacts the artifacts look like these guidelines This is the text version. We have a Jason version of these guidelines and the guidelines Basically give you a definition of all the things that you have to have and what that looks like Is not that? Thank you. What that looks like is a serious stack up of Platform capabilities components, so I'm gonna I have a slide in a minute that'll talk about this So we're just a little out of order But what happens is we publish these guidelines every six months. We give them very clever names like 2015.07 which is the month we passed them. So things are very clear. They're not about releases They are about point in time So if you think about the this graph shows you the release building up code and we're adding more and more Capabilities into the release we pick a subset of the overall capabilities and then we add those into these guidelines So the guidelines aren't the whole of open stack. That would be impressive. We'll talk about that. That's one of our questions It's a subset that we think is the required minimum and then those build on themselves on on each other over time So it's it's literally time snapshots. That's what a guideline is about and Then the guideline internally has At the top this platform concept the platform is to decompose into components. So compute and storage components and Inside the component there are capabilities which you might call a feature We call capabilities consider API based and then those capabilities are validated using tests the tests come out of Tempest and So it's sort of this upward stack the community builds tests and we lump those tests into capabilities and then components and platforms Okay, it is possible though. We don't have any examples yet of having a Component that was not part of the platform Like heat is one of things that's coming up through as a potential new component and That component may or may not be licensed as a standalone thing We have mechanisms to deal with that Well, and that's so I'm going to pause for a second before we jump into the bulk of the kinds of people Does that help people understand Defcore a little bit? Any questions did we lose anyone yet? It's okay. If we did because yes This Defcore cover so there's only two right now. There's object which is basically swift and Compute which is Nova? Glance keystone. We're adding neutron and cinder So when you see products open stack powered compute Then it will be just focused on the compute aspect Which is no one the related like that you need to have in there when you have a platform That means they have both compute and storage or you can just have just a swift based product and it will be called Open stack powered object storage So the thing that's confusing sometimes when we talk about a component it really is about licensing So you have to take off your technical hat and put on a vendor hat So when when the components are all about somebody being able to license Parts of open stack and and certify them as a product like swift So that would be open stack powered storage or if somebody wants to run compute without swift Then that would be open stack powered compute dream host who uses stuff instead of swift So they each have a licensed mechanism and then a lot most people do both and they're the platform And so you know what you're getting with that That's actually I think a good segue to the lessons learned right so one of the lessons we learned was that There are never enough tests and I think I'm going out of sorry out of yeah, it's it's number two on my list Because these tests were not written Thinking about deaf core deaf core came way after most of those tests were written and When we started thinking okay, how do we look at it? Do we write a whole new set of tests that has just deaf core specific stuff? Nobody really jumped up and said yes, we want to do that so we went with what's already in place which is tempest test and We go when we look at the test I think for main things It's pretty good coverage. Like can you spin up an instance? That's pretty well tested, right? and things like that so we do Look at things and make sure that it's there. We're we're really considering of Making sure that there's more than one test for the capability. It's just one test Also, we have a process calling test flagging. So for example if We have something in our guideline that says you must pass These tests and someone comes up to us and says, you know what this test is great, and it does I don't know Create VM, but it's actually calling. I don't know heat for example terrible example Not a we actually had something similar where it was calling There was a requirement in one test for a a guy that wasn't required in the platform And so that test would break if you in certain cases, right? and says hey, I would like this test to be flagged and Making it not necessarily required for that particular set of tests to pass and We have a list of acceptable reasons why a test could be flagged. You can't just flag test arbitrarily So it has to be like either a test is broken. It's calling something. That's not required and a few other things that I don't We actually use Garrett as part of this process And so we use it looks like a development project, right? We have a hacking rules That's what that was referring to we have you know Garrett reviews and all our files go through those processes So it's very community oriented from an open-stack perspective That number three Great question So, yes API and implementation matters If a test fails 90% of the time because of the performance. It's probably not a very good test So yes, right now we don't have just performance specific tests in deaf core But if someone comes up to us and says Hey, this test is really terrible because it almost never passes. That is probably a good reason for flagging it So It's whatever the test is testing So I and there we only pick a percentage of the test so if the test is not You're usable as an API test Ideally we would bring in as many tests as possible and this is why the flagging exists So sometimes we scoop up a test and a vendor comes along and I can't pass this test because it's not fair We actually go through a process scoring and evaluate and Look at the test and see What tests test which capability so it's actually tied and We have some great people doing a lot of work on scoring and actual actually looking at these tests and telling us now This is a terrible test for this capability or yes, this is a great test for that capability For those of you don't know this is Catherine She's the ptl of the ref stack project which and the ref stack was written just so it is easier to run these deaf core tests and It has rules and checks everything It's Garrett actually so what what happens is if you have if we have a test in the system There's a you a vendor would actually add a patch that would flag that test and then we would review that It was part of our normal review process So everything's very public when people ask for things they have to provide justification and so it's a we've made the process incredibly transparent By conforming to open stack process correct Excellent question so the guidelines themselves go through a six month scoring process and we actually have a What we call next file where we we build up this review And so we're constantly adding at the next file We do patches and reviews and things like that and then at the summits We we clone that file into a Prove a proposed guideline or review guideline and then that has three months of time for the community to review it Which we did just last week the board actually approved or you know We showed it to the board which kicks off this review cycle And then people would submit patches against that They're there for Process-wise and we have actually a long process document Things just don't get pulled out of guidelines because that ends up not being fair for the community What we don't want to change the rules on vendors so when we create a guideline We've we've gone through a slow process to get there Doesn't change very quickly and so we don't just take things out now if we find an error Or usually it's a test error and flat we flagged the test so we wouldn't remove a capability would remove the tests We had one capability all the tests were flagged For valid reasons and we removed that capability because there was no test for it So there are two different phases like one in the guideline when the test is already required required status now at this moment we also have a lot of tests that are going to review and They're going to become advisory next time unless someone submits a batch and says hey, can you remove this? I disagree with this test So now is the time to review all of the upcoming changes the the ones that are not advisory yet and are in the next is for Everyone in the community to review submit patches submit comments and say hey I think this test is terrible and Like right now. I don't know how many tests we have in the dot-next guideline That are not advisory or required yet And we will they will not be going into the next guideline because we had a lot of conversations In the last three months about the process about those tests today The dot-next the next file and the guideline the the next guideline are the same So what we were actually about to start taking patches to pull things out of the What we call 2016-01 because that's when it's supposed to be approved the 2016-01 guideline will start removing capabilities from based on the community process so you The action for people out of this this meeting is to go this session is to go to that file Look at that file 2016-01.json and say and if there's something in there that looks bad submit a patch Removing that that entry and we'll start a discussion on it Required the advisory will take will take patches on yes, so if it's already required that's a different process Also get a process you flag it to make it either deprecate it or have a good reason where it's like hey This test is terrible It no longer exists or something like that and yeah, we'll look at all of those that come in but yes Capabilities that are not yet required This is the time now is the time until January Afterwards it'll be a lot more complicated. I think I saw getting great great questions We can so we're getting a lot of sort of 101 questions, which is fine So we'll slow down and we'll go back through because by by deaf core review was super fast And so I love these questions and we'll make sure we explain it We you know we The only one that really Catches people's eye is keystone which has not not that much testing. There's all we always need more tests Right, so it really would be look at you look at a capability and say oh I'd like to have more tests on that and you could write them and we'd encourage that There's no capability. There's no capability that couldn't use more tests Every test every capability so every capability needs more tests I mean it we could flag out individual ones, but at the end of the day if if You have the capability to write a test for something Just write that write the tests on whatever capability and we'll start pulling them in There's I don't want a single one out because I wouldn't you know except for keystone Which we could always more tests on because we added the keystone test to give it coverage The and the reason we had to do that is because people felt the keystone was getting covered because it's it's a Has to be tested by everything else So people were like well, we don't actually have to test keystone because it's already thoroughly tested and So but we actually needed it as a test, but yeah I don't want to it's a it's a fine suggestion But it would only sort of bias people to go do that work anytime if you want to write tests just write tests We'll pick them up So it depends on what your objective is So this is actually one of the items. This is actually the number one item on this list as a lessons learned Right So right now technically what you're supposed to do For the logo you have to certify once a year now. How many products are you certifying? if you were and That this is this is a hard question, right if it's just slightly different Version of what of one product is that really a new product? I don't know So So there there's a couple of answers to this so I don't want to be squishy I actually want to try and be specific for you So the the foundation has rules that apply these guidelines to your certification as a vendor and And they are very specific This is what I need to do to keep my license compliance to use the brand and that that will require you to Submit a result once a year against one of the most two recent versions of open stack And they have all sorts of logo requirements and things like that But I what we'd love to see is for every cloud deployment you do in the field You run your test and so canonicals, you know already certified you got your brand Pressures off every time you do a deployment. I would love to see everybody in the room doing this Every time you do a deployment you run the test suite against it You take those results you upload them to ref stack and even if they don't pass everything They give us data about what you've implemented so logo aside You can get that by doing a generic deployment but what we really want to accomplish as a community is we want to know if you've turned things off and It's no longer in compliance or you've you've added things that are that aren't required in compliance But still pass the test if you upload that data to ref stack then we actually start collecting data about things that are in use Or not in use passing or not passing and that turns into things that we think in action So ref stacks designed to be able to take whatever results you want and so just upload them So so the more data we collect the better and then you're the vendor gets to choose which ones of those are representative of your product But the more the more data we get the better We're going to be able to do it and so we and if you took the same cloud and did it 20 times We have we also contract that it's the same cloud over and over again And so we won't we don't get that doesn't create false positive results Yeah Question so right now all of the tests are in tempest but runnable by tempest Yeah, but going forward. I think they're working on tempest plugins where the other tests are not tempest test can be run by tempest So they they do not have to be in tempest repo. They do have to be open stack controlled Okay, and they they do have to be runnable by tempest or its plugins So if you wrote some you know rack space had a list of tests that were completely outside of tempest Those tests we wouldn't consider we might one day today. We made the decision. It was too confusing to take multiple sources There's nothing inherent in what we do that limits us to only using tempest It is a policy decision for the present to keep people's heads from exploding If they could be run by the tempest framework So it's that is actually one of the questions we have for for the audience to discuss because There are pros and cons to how fast we absorb new capabilities into the system and then what the the repercussions are And so actually we want to I don't want to shortchange these questions because they're really good But we want to do a little bit of show of hands about some of these issues because what you're describing is a non trivial Question, right? It's shades of gray on that one other question, so that is also one of our audience questions Generally historically we have been small core trailing indicator Meaning right we need to be trying to identify a small set The minimum set needed to run a workable cloud sort of the definite the the concept and then Things that are established in market not things that we think are coming and we want to force people to adopt however That is there there are elements where in that where people want to expand what we do For good reason and people want to be more forward forward looking on API conformance not this trailing And so part of what we're trying to do part of the reason for this session is to have people think through the implications of Forcing a API adoption keystone v3 adoption If deafcore makes a requirement then vendors are going to have to implement it rock on that Might be awesome, but it's also going to hurt users because now users are going to find that they're not compatible with Rackspace implements keystone v3 to be compliant with the new guideline Now everybody who's running an older cloud is going to have compatibility issues because v2 and v3 aren't compatible And so we have to shred sort of thread the needle of how those things work What's the future technical direction and our other tools using it? So if all of the tools are using one version we it would be really hard for us to go forward. Yes so So technically that's it. That's it. Have a like I Would I would so there's a technical issue that keeps them from being I would love for the the the technical Deliveries to always be backwards compatible multiple versions and then we wouldn't have to have this conversation, but we So we had this discussion no We had a long discussion about it and and that the simple answer is no it it causes all sorts of challenges and Problems and things like that and here we're thinking about interoperability, right? So from a user's perspective If they're What are they going to code to and How are they making sure or they don't we don't want them doing extra work From going from one cloud to another They expect it open stack to behave the same way and this is what it's all about, right? It's interoperability It's this that now you see why we put we start the slide with are we picking winners and losers? We we we take that very seriously We are very contemplative about what we're doing and here's the dilemma We have to pick something Right. It is a bigger harm for us to say we're not picking and Just let it ride because then everybody just does whatever they want We have to make a choice to create an interoperative. I Strongly agree with that statement, which is why def core was designed as a trailing indicator So that we wouldn't hurt users, right? This is why the Tron reference, right? We fight for the users that the challenge is that You we have a significant amount of pressure to adopt leading APIs that would cause that problem and so part of our ongoing discussion is to Basically, we have this tension within the spec to say which API are we going to pick? Are we going to hurt users who are using the product? But and but then make it harder for migration to future APIs because now we've basically told users They have a two-year window to keep using Keystone v2 The windows are exactly it any current Moment in time you can use the last two guidelines, which hopefully would be like a year and That could even cover like the previous releases So you don't necessarily have to be on the latest guideline on the latest release You can be a you you will be able to certify if you are not running the newest version of trunk Right, and that's why when we do the scoring we we ask the users. What is it that you're using? We're we're not just Deciding this in our clothes little chamber and saying hey Rob. Do you think we do or v3 is better in this case? So If we saw a lot of Keystone v3, then we could have and we're just picking on v3 we have for this issue on multiple APIs But but if we have a whole bunch of data showing people adopting Keystone v3 Then it makes us more it makes it easier for us to say you know what there's actually a Tipping forward adoption right and one of the things that that helps us do is actually make the user surveys Which are based on 350 you know people volunteering information We could actually be getting much more comprehensive data. They actually told us not just hey you're using Keystone or not Are you using Keystone v2 or using Keystone v3 or using you know the token or using the catalog or using and we'd actually Know down to the capability what people are doing And then we can make very fine-grained answers. I I sympathize with your you know the angst We have this problem all the time. We have to make the decision right somebody has to say this is the required API and this This isn't So that the extent to which that that is technically feasible We we strongly encourage people to adopt as much of the API as they can and as they want is to provide utility for them We're just trying to say what minimum set that you have to do if you want to be a product Companies that want to certify to have the open-stack logo on their product if someone is running sx open-stack They will not be able to Get the new logo for it right that doesn't mean they can't run it or can't provide it to their customers I mean the can't part is optional, but I Mean it's going to be there. We're not We're not forcing users to implement the newest feature in throw or Nova or whatever It's it's actually established feature set Yeah, totally right and And and so one of one of things I want to I'm gonna extract this for a second and then we'll keep going back to questions How much time do we have? So so actually so we have a couple I want to actually do the slides This Intentionally creates pressure to have these conversations. So the conversation please come to the working sessions but the questions you are asking are exactly the questions we want people to ask and We did this knowing it would put backwards pressure on the technical community to create migration paths and things like that Because at the end of the day somebody does have to say this is the API that we're going to require for interoperability And it's going to flow backwards Could you jump to? I don't think we have time we'll upload these slides and we can do this but I would ask you to think about what a success for OpenStack look like and The short version of this is we don't know My my thought is if we have an ecosystem of people building products that require OpenStack, then that's success right counting installations is nice but If vendors are building products for OpenStack Then that is actually an indication that we have a market right that was one of the that was the fourth question on this We're beginning to talk about it. It's a it is a challenge. Yes Yeah, I we're they're much less equal than we thought Remember Defqord became official This year in March right so it's we're still refining the process and we're trying to figure out what works and what doesn't work and These are these are the lessons that came came up through the last half a year When we actually started when OpenStack foundation started requiring these tests Being passed and this is what we saw. This is these are the issues we heard people bring to us Yes There's a patch right now and we have started talking about it the the actual process for the foundation is right now once a year and We're looking to see if it's going to be required more than that so I want this is this is actually a nice segue to me and this is what I like about the besides the Tron reference Right Defqord is not going to win Foundation is not coming communities not going to win if it's the foundation with a bat hitting vendors on the knees to make them comply The users have the power if the users are demanding that vendors comply with the latest guideline or the advisory guideline That is where we'll start getting a you know of hosts keeping a you know showing their score on a daily basis I'm compliant. I'm compliant. I'm compliant. I'm compliant with the latest. I'm compliant with the next That if the users are asking that question That's where the power of these guidelines comes in it is absolutely not from the foundation enforcing on brand Right, that's the that that's the weakest way to do it It's the users who are saying use these guidelines if you're not passing the guidelines. We're gonna get mad That's where the power is gonna come in.  Thank you for providing a lot of interaction. Thank you. That's that's what we want Yes, join us tomorrow


The protection team of Kandahar received the information that the boy was alone with all his family and that he was coming from Helmand. So we feel what we call a tracing request to try to identify his family. In the early days of the war, we had to go to the government office. We had to go to the Palestinian state and we had to go to the Palestinian state. We had to go to the Palestinian state to find out what happened to us. We had to find out what happened to the boy. We were told that he was alone with all his family. We had to go to Kandahar to find out what happened to him. If he was alone with all his family, we had to go to the government office. We had to go to Kandahar to find out what happened, but we found out he was alone with all his family. We were told that he was alone with all his family, and he was always alone with all his family. We knew that he wasn't alone with all his family, It's incredible about the story, is that the information that we were receiving initially from the father and the boy, who was so incomplete and different, their accounts were like night and day. But when we showed the photo of the boy to the father, he was immediately convinced that this was his son. Thanks to the intuitive reaction of our colleague Abdul Baki, and thanks to these efforts we were able to reunify a father with his son.


You know, true friendship isn't about being inseparable. It's more about being separable and yet nothing changes in the quality of your friendship. Who are those people in your life? Tag them in this post, let them know how much you appreciate their true friendship. Cheers.


Over 400 experts from around the world are at the IAEA headquarters to take part in the International Symposium on Plant Mutation, Breathing and Biotechnology. Nuclear techniques can be used to generate changes in the plant's DNA and produce varieties that improve their yield and quality. The scientific conference is a unique opportunity to network, exchange ideas, information and make the technology even more effective, more productive. Plant Mutation Breeding has made a significant contribution to food security across the globe. A large fraction of the population in the world is using products that have been derived from mutation breeding. The example I'd like to give is Centenario, which was a barley variety that was released and produced using mutation breeding in Peru. They use barley in the mountainous regions for food, so actually mutation breeding was capable to breed the right variety that could grow in high altitudes. From Vienna, Austria, this is Alejandra Silva reporting for the IAEA.


Valve recently announced that they're getting into the handheld gaming business. They're designing a device that really is meant to compete against the Nintendo Switch, but not really. It's it's really more than what the Nintendo Switch is because the Nintendo Switch is a handheld gaming device. But the Valve Steam Deck is actually going to be a portable computer. It's actually going to be a PC and it's gonna run a desktop operating system on that handheld device. It's going to run Arch Linux, which is a fantastic GNU slash Linux operating system, one of my favorites. And I really think this is an important time in history because I think with this new device that's going to ship and it's going to be very popular because when Valve announced the Steam Deck, you know, their servers basically melted down from people trying to pay them a deposit to get, you know, in front of the line for when these devices are finally released. So there is a ton of interest in this device. And one of the cool things about this is you're going to see millions of people buy this device that have no idea what Linux is. But they're going to have a computer that is actually a full computer that runs Linux. You know, it's not running Windows. It's not running Mac OS. It's not running Chrome OS. It's running a completely free operating system, GNU slash Linux. In this case, it's going to run the distribution Arch Linux. Since I've been using Linux as a desktop operating system, I've seen really two major events that I think really helped us gain popularity where we had really huge spurts of growth. The first one was around 2006 to 2008. And that was the rise of Ubuntu. Ubuntu became the desktop Linux operating system really for most of Linux's early life. You know, the first 15 years of Linux as a desktop operating system, most people just kind of assumed it was a server operating system because that's what Linux really is, right? It runs millions and millions and millions of servers all around the world. The internet, basically, all the websites you visit, they're all running on Linux servers. And, you know, Ubuntu kind of changed the game a little bit because now all of a sudden you had a desktop Linux operating system. That's what Ubuntu was designed to be. And it got people to actually take Linux seriously. It got me to take Linux seriously as a desktop operating system. And that's how I got into Linux and millions of others. Around 2006 to 2008, you know, that really was a good time period for us to gain adoption. And then the next big event that I think really got people to take Linux seriously as a desktop operating system was late 2015, Valve announced Steam on Linux. Because before Valve had Steam on Linux, we really didn't have that many games on Linux. There were a few free and open source games that people, you know, designed specifically to run on Linux. But most of your big AAA games are all proprietary software and by proprietary software companies. And they only write these games most of the time to run on Windows. That's the only operating system they write their games for. Sometimes they write them for console devices as well. But you're never going to get a game that runs on Windows to run on Linux. At least we didn't think that would ever be the case. But Valve made it happen. They had Steam on Linux announced late 2015. And then very quickly, all of a sudden, they started working with the Wine team. Wine is kind of a Windows emulator as technically not an emulator. But it allows you to run Windows software sometimes on Linux. And Valve paired up with the Wine team and they eventually got thousands of Windows only games that could actually be played on Linux. So now, like 90% of the games that you play on Steam on Windows, you can also play on Steam on Linux. And for a lot of people that were holding out, I have to keep my Windows machine around for gaming. Steam on Linux really was the last thing that was the missing piece. That was the missing piece of the puzzle. But there's still a few holdouts out there because there's still 10% of the games out there that you play on Windows still just don't work even on Steam on Linux with Wine and Proton. But Valve is working very hard to get those last few games working. And now with the Steam Deck being announced, I think this is the last piece of the puzzle because they want to make sure 100% of their library, the Steam library plays on that device, which runs Linux. So this is it, right? All the games, all the games on Steam will eventually run on Linux.  Wouldn't it be great if your desktop computer also ran Linux or your laptop? Because I think you know that Windows is not privacy-respecting operating system. Windows is constantly spying on you. It has a key logger built in. It's tracking every key press. It's scanning all the files on your system. It's doing all kinds of nasty stuff to you because there's a company behind it that makes money from data mining you. Data mines you so it can sell that information, usually to companies that want to advertise to you, send you targeted ads and things like that. It's just not a good experience, not to mention the fact that Windows is not fun to use. It's not a great operating system. It's really, compared to all the other modern desktop operating systems, Windows really does lag behind. Really, the only reason people stay on Windows is because they feel like they have to because the software that they have to run only runs on Windows. Well, you know what? There's thousands and thousands and thousands of pieces of software that run on Linux. You just run Linux software when you moved to Linux instead of running Windows software. It's like I've been a Linux user now, strictly a Linux user, for about 14 years. And most of the programs I use on a daily basis, most of them I couldn't run on Windows because they're designed to run on Linux, right? The software developer wrote that program to run on the Linux operating system. Linux software doesn't run on Windows, but I don't complain about it, right? If I had to use a Windows computer, I'm not going to complain, oh my goodness, all my Linux software doesn't run on Windows. I'm going to go find some Windows software that would do the job for me. And that's the same thing you guys have to do. If you want to make the switch to Linux, find Linux software that does what you want to do because I promise you, like the artwork for the channel, audio editing, video editing, everything I do to make these videos is all done with free and open source software that is designed to run on Linux. And really, when I hear from people saying they can't move to Linux from Windows, it's because of software reasons. There's really three things. The first one is games. We've got that taken care of, right? Within the next year, the Steam Deck will ship and Steam on Linux will be able to play 100% of the Steam library. So that, scratch that off the list. That doesn't matter anymore. The second one, most common when I hear is Microsoft Office. Now I understand most people, if you work in an office environment, typically you're required to use Microsoft Office, but with the rise of web-based clients, Office 365, you just run it in a browser, which means you can run it on any operating system on the planet, right? So unless there's a real need for you to have a desktop-based Microsoft Office suite, which of course you need Windows to run, you can run Microsoft Office 365 on Linux. So if that works for you, you've got that covered. The third most common thing I hear people say is they can't switch to Linux because of the Adobe Creative Suite. There's nothing we can do about that. Unfortunately, Adobe has no interest in ever porting their software to Linux, right? And if Adobe doesn't want to write a Linux desktop client for Photoshop and Premiere Pro and things like that, it's never going to happen. It would be very difficult for Linux people to make that happen, right? As the creator of the software has to make that happen and Adobe is very anti-Linux. They don't really see Linux as being something that they can make money off of. As for it, maybe there's just not enough of us yet. Maybe one day we'll eventually get there. But for right now, if you really had to use the Adobe products on a daily basis for work, then you probably would have to keep Windows around, at least dual boot, keep a Windows partition to do your work for the Adobe stuff and then maybe move over to Linux when you actually want to do your standard desktop computing stuff, web browsing and things like that. I would definitely rather do things like online baking, for example. I would rather do that on a Linux operating system than Windows because just the security of the Linux operating system. Now, as far as the Steam Deck goes, I'm not much of a gamer. So I don't know if I would purchase one for myself, because these are not cheap devices. They're range and price, I think, from like $350 to about $600, depending on what kind of storage you get in it. But even though I'm not a gamer, and probably a lot of you Linux users, especially many of you are not hardcore gamers, that doesn't matter. We should support Valve in this way. We need to make this a success, because if this is a success and they can get every single game that runs on Windows to also run on Linux, that's a win. And maybe they could also keep working on Wine and Proton and eventually get things like, I don't know, Microsoft Office, the desktop client to run in Wine or some of the Adobe products to work in Wine. I think that's eventually where we're hitting. I think eventually Valve is gonna sell stuff other than just games in their store, right? They want some of this other software that used to only run on Windows or Mac now to run on Linux. So what I'm thinking about doing is I may purchase one or two of these devices for gifts. I've got young nieces and nephews. Give them to your nieces or nephews if you've got young children or grandchildren. Give it as gifts, birthday gifts, Christmas gifts. Help this product succeed, because I think really this is gonna be a game changer. This is gonna be one of those major events that all of a sudden we see a massive spurt and growth again as far as new users coming from Windows over to Linux. I see too many journalists out there. All these articles about the Steam Deck and none of them mention how damaging the Steam Deck is gonna be to Windows. Every single article that talks about the Steam Deck running Linux, you know, that's great and all, but they leave it at that. They don't ever talk about how millions and millions of people are now going to be running a good new slash Linux device, a computer. And they talk about how the Steam Deck, you know, could really pose problems for Nintendo because it's a competitor to the Nintendo Switch. I don't think the Steam Deck and the Nintendo Switch are really competing because the Steam Deck is gonna be a proper computer where the Switch isn't. Plus, if you're a Nintendo fan, you like the Nintendo games, you know, the catalog of games that Nintendo has, you're gonna keep buying Nintendo products, right? I don't think the Steam Deck is gonna run Nintendo out of business. That's not gonna happen. I do think, though, the Steam Deck is gonna cause serious problems for Microsoft as far as the adoption of Windows 11. I think a lot of people are gonna give Linux a serious look now. Now before I go, I need to thank a few special people. I need to thank the producers of this episode. And of course, I'm talking about Absie Games James, Mitchell, Paul, Wes, Akami Allen, Chuck, Kurt, David, Dylan, Gregory, Heiko, Erion, Alexander, Peace, Arch, Infador, Polytech, Raver, Scott, Steven, and Willie. These guys. They're my high-steered patrons over on Patreon. Without these guys, this episode you just watched wouldn't have been possible. The show is also brought to you by each and every one of these ladies and gentlemen as well. All these names you're seeing on the screen right now. These are all my supporters over on Patreon because I don't have any corporate sponsors. It's just me and you guys, the community. If you like what I do and want to support my work, please consider subscribing to Distro Tube over on Patreon. All right, guys, peace. Now gamers can say I run Arch, by the way.


We had another cool catching cricket, a little bit different. This ball is shot way up in the air. I promise you, you've never seen a catch like this. I promise you, watch this. Okay, thumbs up. It went through his hands into his pants that are so stretchy, it disappeared for a little bit and then popped up on top of his leg and then he caught it. Then he grabbed it with his hands.