Bro you literally have no proof aside from the fact that he said it was definitely me go Rob And they don't even know where she is. Oh Yep, she's calling to him Oh, he doesn't know where she is Cook row and shimney bro. She always got a bottle of wine. My goodness gracious That hat man. Oh like all the train conductors have that bring a mask is prohibited Oh, make sure they're not escaping You don't have to catch up on say the straw hats. I met them He's jumping up. No, Luffy's trying way too hard to take out their conco. Man. It's getting dangerous He really wants to be like him so much verticality of water seven. I like it a lot easy landing Elevators too dangerous. Ah, you're fine He's been inspired It's pretty bad timing with this terrible storm coming out. Oh Typhoon wait, isn't that oh, I guess it's not what coming but it's more like a flood coming but That's what I'm saying like if this happens often like this city is pretty vulnerable. It's so close to the water It's all in the water Water runs to the entire thing. It's water seven way knows bar There's Frankie. What was that? Louie no What Wait what this is how he operates is it soda he's powered off of cola They still have a million that's not much what they buy like what all did they spend it on? How? Dang Frankie really doesn't like hanging on the money. It's weird That's our Franky Water seven underworld then he would know what's going on with Robin if he's the face of the water seven underworld Oh wait, there's Kokoro. Oh Wait, yeah, she said that they were drinking buddies didn't she? Oh, you know, she said her and iceberg were drinking buddies Statue of a monster Kokoro to everybody They got juice here But from the fight oh just from the house being destroyed yet all his men So that's what gives them energy. That is so funny He's back in action So wait his hair actually does correlate to how tired he is like in terms of energy It's all it's like standing up now I've revived then he ran out of energy fast, too.  Oh, yeah, they don't have anything to get ready Yeah, he's so not worried about it. It's so bizarre Okay, I was right. Yeah, they were drinking buddies her and iceberg. Oh She doesn't believe it Yeah, oh Base Kokoro base. Yeah. Well actually Robin might be involved. I wouldn't be shocked. I think she is I just don't know why CP 9 Gonna get some actual information on it Organization the king of the underground so you call yourself The CP 9 is a group. Well, I broke works sort of underground What are the odds that they're also led by a warlord? I think that's like the masks And Robin got mixed up with them, so it's not an activation code. He was just saying like CP 9 that's us for here Why is she so fine with doing this did she owe them something finish the job No Tom guy CP 9 Mission for justice Assassination, I don't know man. I can try to say like unbiased me. Oh, maybe iceberg is a bad dude But I don't know he seems just as confused as to why they're doing this we get his inside perspective He's not like faking it from what I see. It's weird. That was a weird perspective We got from Robin though like they see themselves is doing the right thing Can they turn off the fountain? Well, they all got weapons looking for Zora Lubey and all them. It's kind of sucks man. Everybody just after them I have to remember that not everybody's in the loop all the time Oh, and he's gonna see it in the paper. Oh, no, do you guys want to perish? Oh My they're paying you good money man left stuff buying surprise. Nobody's gone after Mary They know I mean, I would assume they know the ship they came in on or someone would know I guess cuz they're in town They're in town. Oh Never mind. There you go Except you stop Pursues up Man, nobody's there to defend Mary. I was gonna say he's gonna he's gonna make a comment about how it's all right You stop don't do it. There's way too many of them Well, they already emptied the ship all their stuff is at the end You can run forward or stop. Oh, that's true. Yeah, they don't know exactly what they look like and Zoro can handle himself for now Chopper's long face Why would one leave at 11 wouldn't they cancel it? They maybe that the train that leaves in 11 has to do with CP 9 What does he think he made like a bad book recommendation Pretty rough situation, it's like I keep comparing my head to alabasta, but still feel it's like it's like it's like a Light rumbling as such as like a literal calm before a storm. It feels so unsettling There's a lot more going on than in their control right now Could it be what? Robin's smell Robin. Who's he running? He's on the sense. You can't lose the sense It is Robinson I Didn't say it's probably like underground somewhere something like that. Oh wait, that's not on the ground. Never mind. What does he see? This is gonna be Robin standing there.  Okay, but why Wow, Kiji said yeah, but every group associated with her always perishes They're already reaping what they've sewn I mean it's kind of there to tell them It's gonna try to follow her she's gonna pin it on them. Oh, there they go That'd be a bad joke The waves are too strong Why does that sound so haunting? Our crew is falling apart Usa Robin, who's next bro? There's like a part of me that thinks like there's some unbearable weight that she feels that she'd like just straight There's sort of cannot escape from whether that just be her past or not But I feel like it still has to do it I mean I was gonna say Al Kiji But I think she was more just scared of him because he was an admiral But this this feels like especially from the interaction we saw with whoever she was talking to from CB9 that this is just another Organization organization that she owes something to or is indebted to and that's why she's following through with whatever they're having her do But again, we haven't seen the whole underlying story. So maybe it's more than that That's just kind of how it's been perceived so far So in these two episodes it is confirmed it was one million percent Robin and she said she's also leaving the crew We're down two people now. Are we gonna get an explanation after all this time? You're just gonna leave without an explanation at least usa like we know why what's going on He can't part with Mary but Robin it just feels like she's just jumping ship to another group to just kind of leech off them for a while But again, we just don't know enough about her I think that was like kind of the significance of the conversation with Sanji and Usa Sanji and Chopper like two episodes ago where they really they both realized they'd know absolutely nothing about her I think they really brought up her favorite food or something, right? They were trying to guess it I don't know man Like I said all the this like swirling storm that's slowly coming how Nami said it could be in that a typhoon It feels like it like I'm like tense the whole time I stopped breathing at times because I'm just holding my breath waiting for just something to pop off because I'm scared Maybe it's because iceberg it is bedridden that it feels like there's sort of like a wound on the town that cannot be helped It's all so bizarre man, but it has me so intrigued guys That's been it for episodes 239 240 for one piece watch who do drop us up on the channel if you are new And I catch you guys in the next one Peace


Bob sees the ball flying to the left at 100 meters per second, but Alice is also moving to the left at 90 meters per second. The speed that Bob sees the ball hit Alice's hands at will be the difference between these two, or 10 meters per second. So was Alice moving or not? See, if you asked Bob, Bob would have said I'm standing on the platform and I feel stationary, I know I'm stationary, and I can see Alice whizzing past at 90 meters per second. But if you asked Alice, Alice would have said I am stationary, I feel stationary.  See, the reason for that is because there's no such thing as absolute velocity.  I am stationary with regards to the platform, or I am stationary with regards to the train, or the ball is moving at 10 meters per second with regards to Alice. Now you may think this sounds a bit contrived, I mean surely we can all agree that the platform isn't moving and the train is, but the platform is on the earth, which is going around the sun at 30 kilometers per second. Claiming that Alice on the train is stationary is just as valid as claiming that Bob on the platform is stationary.


We're surrounding this guy from the local channel. It's a local press. It's so terrible. I'm not coverage. I did this one video. We are supporting the people, brother. So I would like you to inform me, please. We are the fascists of the week. I would like you to inform me, please. How is it possible to say that we are the fascists?  We want to kill them in the car. We want to kill them in the car. And he is from the press. He doesn't show the truth. He doesn't show the truth. He tells us that we have weapons. We don't have weapons. He has told us that we are the fascists. We came out of the car without anything. He told us that we are the fascists. And he has told us that we have weapons. That's not true, brother. That's not true. Thank you. Saying how bad the press is. I did it on my own. So they're telling the press not to lie, because this is the local guy in the press, she took a long ferry. They're asking why don't you go up to San Cata and see how many deaths there were, because the local press is not reporting that. And it says we are not delinquents. We are a country that asks for democracy and justice, because the local press is calling them delinquents, saying that they're paid, saying that they're drunk, saying that they're terrorists. They're very angry at the local press. They say, wow, all this time in the press. She's afraid. She said, don't film me, because I don't want to go to jail. They're very angry at the press, because they saw me talking. They want you to talk to them. They're from the rich class. They want to go to the national press, but it's only been lying to the people. She says, why is your government involved in making problems for us here? It's not true. We'll keep it for a while. Do the coverage. We have to let him do the work. How has the local press been? Well, it's been very efficient. We've seen a lot of things. We've heard the news about the death and the repression of the army. We'll hear what they say. If it's that they're exaggerating 100, we'll hear it well. We'll hear a lot. We have to let them do the coverage. I want to see what he's going to say. I want to see what he's going to say. I want to see what he says. I want to see what he says. I want to see what he says. We have to let him do the interview. I hope he comes out. We have to do that, brother. We'll keep calm so he can hear us. So he can do the interview. We'll show you right now. We're trying to ask people to be quiet so they can hear what he says and see if he's going to interview this woman. And whether that's going to come out on the television or not. Because so far it's been all propaganda. I just don't know when they're going to start and if it's live. But anyway, this woman wants to be interviewed by him. And I've seen him on television. It's been terrible. I want to take him out. Now we're going to talk to him? He's not here. He's not here. They're coming, they're coming. You can't go there. This might be taking a little too long, I wanted to show you how angry the people are with the local press, but I think I'll sign out and sign back in when the big march gets here. Okay, so watch, I would say in about 15 minutes they're about to arrive with the caskets and the families of people who lost their loved ones two days ago in San Pato. Be right back.


Disney has recently been celebrating its 100 years of magic in the entertainment industry. What better way, though, to really put a feather in the cap than to release a new big film for the whole family that's incredibly mediocre across the board? I saw Wish. You probably shouldn't. Here's my problem with Wish. It doesn't suck, and it's not good.   You can have fun with that, like a Fast and the Furious. There's still at least entertainment to be had by how ridiculously dumb it is, and of course there's entertainment if the movie's well done. The worst kind of movie to watch is a movie like Wish.


Welcome to Toffy TV, it's the Match Preview Huddersfield Town versus Everton in the Carabao Cup on John by Kane and Dan, they are regulars on hands tours, you know, they know what they're talking about, Dan sells stickers, so that makes it even better, didn't bring any in though, didn't bring any stickers in, got to it about that, nice one mate, big parcel, the last you've seen mate. I'm not used to get away games in the Carabao Cup this early, I know we had one a couple of years ago, and actually we had them last season, but because it was on telly it didn't really feel... Oh, I was gutted, I missed them. No, Fleetwood would have been a boss, wouldn't it? Fleetwood would have been a boss, wouldn't it? I was over that because I loved ticking off new grounds, and that was that one that we made before. Fleetwood would have been a really good one for us. No, what it is, it's not that you love ticking off new grounds, you love leaving stickers all over new grounds, there's a difference. I don't know what you're talking about. No, no, no, no. I'm innocent. Yeah, it seems like an orchard won this on paper, just because we used to, well, put us through it in the Premier League a couple of seasons ago, and it just seems like, it just feels like it could have been done with a nice league one team, and I could have some path with full outs, and they're always the best games, but it's going to be a little tricky one this, because we know he'll probably mix the team up a little bit, he'll bring in a few from outside, and that just makes it a little bit tricky, especially with fans there. They've obviously limited our allocation, which is mad, which is mad, and they're trying to get as many of their fans in and stuff, so it will be a tricky one this one, I think. Yeah, maybe, but on paper, we really should be beating them, no matter who plays on our squad. Yeah, it's not strong enough to beat them, I think. Yeah, the thing is, players coming in, likes a good ban on, Godfrew, the fingers crossed. Hopefully, yeah. The fingers crossed, they'll be back. Players coming in with a point of proof trying to get them to the team now, because there weren't many changes from Southampton's leads. No, no. You want to be getting into the south of Saudi against Brighton, so let's hope that these players come in with a point of proof and we get something going, get a little bit of a cut run going this season. I'd like to see Anton Gordon get a minute, I wouldn't mind him starting to be honest, I think obviously he played at that level in the second half of a season, and I think he needs game time, he needs, if he's not, whether he's going to go out on loan. Yeah, but I'd like him to start because I think he's got a lot of potential there, I think he needs minutes to either show he's good enough to stay with us for the season, or whether he's going to go out on loan or not. Yeah, it's a difficult one, isn't it? Because there will be players playing their first games this season in this game. John Joe will probably play, I'd write back. Probably, he might get minutes as well. Yeah, you might have a different partnership at the centre back, then you've got the likes of Tom Davis, Delth, Gabbaman, you've got the likes of Anthony Gordon, Tarnton didn't start sadly, so we might come in, Moise Keane. So there are plays you can definitely come in for this game, but if you get too many of them and it's their first game of the season, and you're playing against Huddersfield, you might keep a set. See, I think it would be interesting what Huddersfield do. See, they've set it up as like, oh, we want to win this, we want to fall out and all that. And I wonder whether they'll do that when they pick their side, whether they'll go strong, will they seize a big opportunity, or will they manage to go, no, we're going to make 11 changes as well. So don't get me wrong, that shouldn't make any difference. It's always a tricky one this first one because you know you're going to get five or six plays, you haven't played a game so far this season. And they all should be chomping at the bit, just that it doesn't always work out like that. See, I have that mentality for you because we've been here so many times where, I've had an example when we went to Lincoln the other year and won down, and then it was two, two, yeah. So it's just like the rollercoaster, the kind of back up I think for us, the fleet won last year too, you know, we went a day, but so let's just hope we get a comfortable game and just win three or four and help please. Do you know what I mean? No, it is about, it's about the start I was thinking these games, getting off to a good start, just keeping the, you know, we went to about the one couple of years ago, we won them down in the first minute, you know, and that's a full house, and that's what they're trying to create. I think it's about the mentality going there, keeping them quiet for 15 minutes, getting in front, quieting them down again, and then just, and then starting to play your own football. So when you're on the back foot, if you start poorly, and you have got plays, you're trying to force the way he's in the squad, it's always, I hate these away games, I always do, it doesn't matter who did it again. But it's because at the time of the year, it always feels like an afterthought, like it almost feels like for fans, everyone's focusing on the bright game, but you've got to think about this game. It's very important for us to get on a cut run. I've been desperate all my life to see Everton win a trophy, so this is a massive game for me, and I was the second round of the Carrival Cup, my team a bit more time for people, and not bothered. I just want to see Everton win a trophy rather than finish sixth or seventh in the league for me.  You've got the opposition straight away on the back foot then, haven't you? So that's what we need to do, just start the game bright, get a photo of the ball and then hopefully make a goal, and then if we get the first goal in the game, I think we'll just run away with it. Dan's mentioned at the goal, is there anyone that you'd really want to see that we haven't seen so far? Gwbamwm. Gwbamwm, for me, yes, because in pre-season it's really good to watch the bit of the Blackburn game, and you took us all well, and that you can carry the ball up really well for us, and I know it's only pre-season, we haven't really had a true reflection of me yet. So it'd be good for him to maybe get a good 55-60 minutes under a spell, so we're going to play him for the full 90, but just to build his fit. If he's fit, then I want to see him start. I want to see him start competing, and I know a lot of people are like, you know, why hasn't he had more games? Well, obviously he's been in isolation, he don't want to risk him, and why should he risk him? You know, we've waited two years for him, I'm prepared to wait a little bit extra for him. If he's on the bench, starting to feel on the bench regularly, then that's good, that means he's ready to go, but I've got no problem with the manager not using him. But this is a really good opportunity for him to get a game under his belt, so because you want to get that tag as well of everyone, like, will we ever see this player by a bright injury? This is a lad who's had two of the worst injuries you can have in football consecutively, so I really want to see him play and just dominate a game off of him, and everyone go, yeah, that's the lad we bought. He's perfect, so he's probably a perfect compositional for him to do that, because you'd like to think that he would be able to dominate him, he'd feel the size and the speed that he's got. And he did look good in pre-season, like the games, the opportunities he's got, and it was softly, softly, but he was in, you know, the conditions were really harsh in terms of America, you know, how hot and humid it was, he came through that, he looked. Even a Finch fan, I'm on a black cast. Yeah, yeah, he looked. It was really, yeah, exactly, and I know it's not the same level, but you've got to introduce him at some point, and I'd rather see him start a game against Huddersfield in the League Cup where they may, they may change it round as well to start in the Premier League where you know it's going to be 100 miles an hour. It's always going to be difficult to get him into it, but like you're saying, they haven't, and I've got to, you know, we have treated in the last few years like it's a very important competition, and we have to do the same. We know the big clubs once they get going through the, if they get through the early stages, once they get to the latter stages, the squad are so, I mean, when you look at the Chelsea squad and when you look at the Man City squad, it's frightening that this is their fourth choice tournament, and yeah, if they get to a final, they can still, a semi-final, they can put out frightening teams. We've seen that with Man United last year. The City have won this cup how many times in a row.  What I'd say to that is too, we had City in the FA Cup last year, behind closed doors, full crowd, the goodness in there, you don't know what happens. Yeah, but it's the other thing though, isn't it? You've got to get through to those rounds, and then maybe you might avoid them, and if everything could just get to a final, and I know it's a stupid thing to say when we're playing the first nine, but that's why you've got to get through these games. Personally, I wouldn't shop and change too much, because it's still the start of the season. Players are reasonably fit. So, let's just get some game time in them players too. Honestly, I know we've had a toe injury, but if you can't play too much of it, then that's still the problem. I think Richard is going to play, but I think he'd normally play in these games, it would just be down to what the manager thinks in terms of his reserves. You look tired towards the end of the game on Saturday, and obviously he's had a very busy summer. You might look to give him the game off, but you're right, people like Grey. Townsend. I played them. I really would. There's no reason not to play them. Just get the game one by our town and then take them off if you need to be. But then someone like Arlen maybe could sit out this game, and that's when you could bring in. So, only three or four changes. Seamus won't play, but Dean might play. The centre backs, we've got enough quality to centre them. Beg of it will be a goal too. Beg of it will be a goal, so there's enough of a mix. Then you might go, we'll have Lewis Dobbins on the bench then. And if we can get on ourselves a good lead, then you bring him on in it. I wouldn't shop and change too much. I wouldn't make loads of changes, but I think he's got the option if he wants to. And then you can bring a sub on that maybe you wouldn't have brought on if you can get yourself on a decent lead. It's about mentality. We've got the right manager for these kind of games. It's whether we do it or not, and hopefully we will. Take it as another game. That's all we can do now. That's it, and hopefully we get through. Good opportunities to get through to the next round. Hopefully we do. And hopefully we get to see the likes of Gabbaman, maybe an Anthony Gordon. And get through to the next round. That's all we can ask for, so let us know your thoughts in the comments on this one. Who would you like to see starting for the Blues, and do you expect us to get through to that next round? Put it this way, don't get knocked out before some teams are on it. Oh yeah, oh my god. Don't do that. Arsenal, Mike Dahl. Oh Arsenal are in it for the first time at this date for 25 years. It's a tough game as well. You just want to see some knockdown on Arsenal fan theory. I just want to see us win. I've got to leave a monkey bag. There you go. Let us know your thoughts in the comments. Don't forget, give this video a like. Subscribe if you haven't already. If you want more great videos, join us on Patreon. The link is in the description and it's on the screen right now. Thanks for watching. See you later.


This next short video illustrates an exercise used when training sawyers and swampers. There's great value in watching this exercise being performed, but of course, if you want, you can certainly duplicate this exercise on your home unit. Review the Sim Lim Top Drop Job Hazard Analysis before commencing this exercise. Follow all chainsaw safety procedures. Did you know that over 90% of chainsaw injuries that occur happen from overhead hazards while cutting? Watch this practice scenario and give it a try. This exercise is called a Sim Lim Top Drop or Simulated Lim. It utilizes a soft simulated limb, a flagpole, a release line, and a chainsaw with a chain removed. In this case, the soft simulated limb are two pieces of foam insulation bundled together. The idea of the exercise is to increase the sawyer's awareness of overhead hazards by looking up and not relying on ineffective warning methods. Check out what can happen. In order to avoid any falling objects, you need to have a clean escape, and that means having a cleared escape route. Take this opportunity to practice cleaning out an escape route. And you can't hear, you can't depend on anything.  You can only avoid those hazards because there's only seconds left. It was some major delayed response. You saw how it hit the ground before the guy even realized anything was happening. The whole point is, eventually, I'm going to have to learn to look up by myself, and that's my best chance of survival, is for me to look at it and not depend on somebody else. I feel this exercise is very useful in the fact that it is in a control environment, a safe environment, and it lets all of our employees see who are using a chainsaw how quickly a limb can come down, and it is life or death, and we've seen so many people become paraplegic or lose their life, and I want people to really reflect and take this moment, and I feel it was very important. For more similar top-drop information, access the Forest Service Internet at the following website.


Hi, it's Bridget. Welcome to Above Life Channel. The purpose here is to inspire your spirit and to fill you up with hope. Today, we're going to do a channeling with someone who has been requested and with someone who I have been feeling into the last week or so. All right, so we are going to chat with Luke Perry in the afterlife. Now, Luke Perry is most known recently for his role in Riverdale. My understanding, I didn't watch the show. My understanding is that he was a dad in that show. But I know him. I know him from back in the day in Beverly Hills, 90210. And he was Dylan, okay? He was like the kind of bad guy, strong, silent type. He totally has a James Dean vibe to me, which is totally perfect, you guys, because I just channeled James Dean like two weeks ago. So he kind of has that vibe. And he definitely is someone whose death was a shock. He passed away from a stroke. And you know, if you've watched Above Life Channel, that as a psychic and medium, I kind of have a rule, a rule of engagement or connection where I don't like to channel people right away after they died. Now, that's a Bridget thing. That's just a preference I've had because I felt like it wasn't very polite to do that. I kind of felt like it was just not, it just didn't feel, I felt like I needed to give them privacy and respect like the family and stuff.  That's just something that I created for myself to have kind of a boundary around the energy of that person's passing and not just that person's passing because, you know, I feel like death is a private or intimate moment, you know, between the creator and the spirit and the unification of that and the transition of that is really sacred. And it's, it's, it's sacred as birth is. And kind of to dig all into that and be all in the business of people, spirit feels like not super great to me right away, you know, I feel like, Oh, geez, let's, let's kind of give it some time. However, I also recognize that part of the reason why I have tried to stay away from the sensationalization or the focus on people who just die right away, who have just recently passed or what have you, is because I don't want the attention. Like I don't want people Google searching and finding me in my channeling about that person because I feel almost like it can be like a drug, you know, afterlife and and paranormal connection can be like a drug to some people and it can distract them. It can be an addiction. It can be something that redirects you instead of focusing on your own life and your own beautiful spirit and the incredible eternal energy that you have access to that we all have access to, I feel like it distracts people. And I don't want to be a part of that. However, don't worry, I'm going to get to Luke Perry. If you hate that about me and my channel, don't watch. Okay. All right. So for those of you who know how it's done here at above life channel, you know that I got some story to share you for with you first, right? So a couple of days ago, I was blessed to talk to a client that I talked to one other time before who comes to me from the east coast of the United States. And we connected because of above life channel because of the channeling here. And she is such a beautiful soul. I love you so much. You know who you are, I hope. And she scheduled session with me and it takes sometimes you guys sometimes takes like three to four weeks to get in with me sometimes. And so she scheduled the session with me like a month ago. And we just had it this last week. And when she scheduled the session, her mom was not sick. When we had the session between the time that she scheduled the session and we had the session was about a month, right? Four weeks. And during that time, her mom got sick. And then she died. So when I talked to her, her mom had transitioned into the afterlife only about six days before that. She didn't know mom wasn't sick before she scheduled the session. And here I was all of a sudden like I go to open up the session and create the energy connection. And we start to talk and all of a sudden boom, her mom's like right here.  I said, is your mother in the afterlife? And she said yes. And she got emotional a bit. Natural to be emotional. You don't need to apologize for that is beautiful. It's just a reflection of how much you love and care for that and that person that spirit. And I could feel her. I could see her. I could she was so easy, so easy to talk to. And then I finally asked her, I said, Well, when did she die? Because I don't remember. I'd only talked to this beautiful sweet client one other time before. And I don't remember if she had if her mom was in the afterlife that time, you guys, I talked to so many people, so many families, so many dead people, so many living people. I can't remember all that stuff. Oh, please. I can't remember. I can't remember what I had for breakfast this morning. And so it was just such a it was so easy to do.  How long I talk to them? How long I talk to them after they die? Now, I do think that there are still some rules of engagement that I need to make sure that I'm honoring. Like I'm not going to jump on any bandwagons because I just don't like that. Like I feel like, Oh, gosh, it just doesn't seem like me. I'm not a follower like that. But I also think that there's some if there's some relevance and some insight that can be gained, some healing, some opportunity for you to open up your spirit for your own inner healing or connection work. Because someone had just recently died. And for some reason, that could be a portal or opening for you to heal for yourself or to inspire you to go on and utilize your intuition or to make changes in your life or co create your life in a way that's more positive and supportive and healthy. Then yes. Yes. Thank you, Luke Perry, for your patience and waiting for your time to be on scene here. But yes, maybe I will consider that in the future. I'm open minded and open hearted to consider that in the future. But I won't do things that are like, let's solve some murders or let's talk about this person and gossip about them. That's not the intent of a above life channel. If you want that kind of channeling, please go someplace else. That's not there's a purpose for for the channeling of celebrities in the afterlife here that may blow your mind, but it's all about you and inspiring you to live your best life. And that's how I work with them. I'm like the life coach to former people in the afterlife that understand the pressures of living in a very human life on stage. And oftentimes we as people feel like we're living our lives on the stage to open to criticism, judgment, external and internal. And we're always trying to prevent ourselves from being a target or being bullied or being mistreated or misunderstood. So a lot of times we hide or we tone down ourselves. And that is not the point. The point of life is to live it until allow other people to live their own lives. And if they're projecting their evaluation or criticism or judgment or meanness, if they're being mean to you, it's because they feel bad for themselves. We have to start recognizing that. So now Luke, Mr. Luke Perry, you are he is gorgeous. Let me just say he is a beautiful man in human form. And in the afterlife, his energy is glowing and he really does have a nice smile. He's got this beautifully shaped face and he's kind of got this eyebrow thing. And he like is glowing like in a lovely way.  He says, I'm glad that I could help you. He says, he says, if I if I inspire you, then you can inspire others. And he says, isn't that really what it's all about? He says, you know, the impact you can make on this world is, it's part of your legacy. It's part of what legitimizes your life as a celebrity. Okay, so as a celebrity, Mr. Luke Perry, I have to ask you. So as a celebrity, you are well known for lots of different types of work. Like I said, 902 and oh, that's how I know you. And most recently, many people will be fans of you in Riverdale. How as an afterlife, so as a spirit, can you explain to us what what your body of work means to you now? What your life roles and accomplishments from your work? What does that mean to you now as an afterlife spirit? What does it mean in the afterlife to have all these accomplishments? And what is important to you? Okay, wow, he is. When he used the word sexy, even in the afterlife, he is kind of has a way you guys about him. He says, he says, I, I was fortunate. And I recognize that when opportunities present themselves, you've got to take it. You know, you have to take risks. There are some, some things that you will choose to do some projects, or in my case, some some projects or some roles that, you know, just aren't that fulfilling. But they can lead to other things. So Okay, so the advice that he's kind of giving us advice, he says advice I would give about living your life is to recognize that there are stepping stones. It's more like a staircase. And each step that you take, it's you closer to this, this sense of accomplishment, that's really what humanity is about. Being a person, having a human life is, is this series of steps toward accomplishments of goals that that we set for ourselves in our human, in our human time, he's saying, it's hard to identify each of the words in our human time, our human existence. It's important to recognize that, although you may have this big, this grand idea in your mind, this vision for what, what you want, you know, that that perfect role, that perfect career, that perfect life. It's important to know that it takes a lot of small steps to get close to that, to even get close to that. It's a lot of small steps. And you have to build upon your body of work, you have to build upon your accomplishments, you have to build upon the skills that are needed in order to be in the right place at the right time. Isn't so much about, like, timing, as it is about you being willing to go into an experience and make the most of it, no matter what it is. There's, it's not small. It's relevant. You've got to make it relevant. If you have a small part, a small role, says, you know, even if you're doing commercials or acting, or if you're an intern and working in a mail room, he says, the person that works in the mail room can run the company. It's not, he said, it's not, it's not out of reach. It's not out of what's possible. He says, you talk about, you've talked about the topic of manifesting. And I'd like to speak on that a little. I think the, the topic is misunderstood. And there's this mind, mind's view that it's all about what's big, and what's noticed, what's recognized that that the recognition is the goal, but that's not the goal. That's not at all what you're really seeking. And in your words, it would be connection. He says, he points to me and says, in your word, it'd be connection. You seek connection.   And that is how you do get recognition or acknowledgement or invitation, or that's how you get parts and movies or roles or opportunities and projects. Now, have you done directing or producing? Because I'm feeling like that. Like I literally see you in a chair and it says director on the back. It's a black chair and like old school movies and it says director. And I feel like Luke Perry, have you been a director? He says, yes, I have the opportunity to directing showing me like an indie film. And he shows me something for TV. I made for TV something. He says, you know, television has changed a great deal. He said, the way that you consume media has changed so much that entertainment has had to adjust. And it's given a tremendous amount of opportunity to reach people to make connections in different ways. And it's given a great, a great number of platforms, you know, social media, for example, YouTube, Hulu, Netflix, exit, for example, to provide lots of people with the opportunity to share their creativity, to make some really incredible work and to share it. And it's not, it's not as limiting as it used to be as it once was. And I think in the future, there's going to even be even more innovation. And with the on demand services that are available now, there's, there's so much more. But I do feel that in the future, there will be a sort of a nostalgia about the old TV time, the early days of television, where, you know, the 1980s sitcoms and the rise of the coming into your house every week, and instead of a binge kind of a consumption, overeating, over consuming media, there will be, I feel, he says, I feel that there'll be a return to a sort of a routine or a scheduling of almost like an event like a television, but not television in the forms of there's primary channels, and that's the only people that have control and that kind of a thing. But but a way that entertainment can be something that's a routine part of life that provides a routine is the best way, I think he's saying a consistent outlet. Because when when you watch something, whether it's a movie or a television show, or a series, you are consumed, you become part of the, the production, the the dream or the vision of the producers, the creators, the writers, the actors, you become part of that, you become invested in that, and accepted into that. And so every, every week, then there's this feeling of needing to show up and to, in a way, reconnect with that. You have a buy in, you have an interest in how things are going to go and you ride the emotions of that series or that cast in a way that allows you to, in a way, detox your own, your own life detox yourself. It's not just he says, he says, this is interesting, because he knows how I feel about this. Because you can feel that right. He says it's not just escapism, it's not just a distraction. For some, yes, it might start out that way, but it's, it's not you become part, he says, look at the game of thrones, look at the incredible success of that. And I didn't watch that. He says, but many, many of your viewers have, he says, and look at the incredible success of that, there's this, you become part as a camaraderie, you become part of it. And that's, that's what's exciting to, to the people who are creating it, that's what they want.  So you see it so much more entertainment and acting and producing and creating is not just fame and beautiful people and notoriety and awards, it's not, it's, it can be so much more than that. And I think in the era of reality, television, you lose sight of that in the area of, in the era of blogging, like, like blogging, he's pointing to me because I just did a blog this morning on my other channel, where I blog a lot of stuff. And he says, in the era of that, there's this, there's, there's more. He says, there's so much more commitment and relationship that can be achieved. When, when you recognize the part that you play in anything that you watch or you consume or you become part of, he says, the audience is, is critical in the success of anything. It's not just about watching it. It's about the, the commitment that they have. He said, it's incredible. He says at Riverdale, we had a lot. He says, you know, it was, it's hard to compare, he says with 90210, as you mentioned, he says, it's hard to compare that with Riverdale and success wise. It's hard to compare. He says, but in my experiences, it's in Riverdale, there's this a new, a new opportunity for me to connect in a different way. And playing a father, while it seems a bit mind blowing, if you think of me, you know, as Dylan in 90210, it seems kind of mind blowing to imagine me as a dad in a different, you know, way. He says, but there's, we all go through stages in our lives and we all grow and we experience different things and we have different roles that we take on and different challenges. And Riverdale was an opportunity for me to really to influence also a younger generation of actors and actresses and of artists and you know, people really care and or they can, there's a capacity, there's an opportunity to really care about one another and encourage each other and to help and and I do feel that I serve as a mentor or I have served as a mentor and that doesn't make me feel old.  So he's kind of responding to some of the things I'm asking, which I forget that I have to make sure I'm getting I'm getting caught up on the channel here. So I'm asking him about being a mentor and if that makes him feel old, I mean, to be honest, because like I understand because I start I'm starting to feel old, like I have an 18 year old person now adult in my household that I'm like, when did I get old? I'm still like, aren't I cool still? No, I'm a mom now, you know. And so but he's so he's responding to that and he's saying it's it's an accomplishment. It's really it says a lot about about who you are as a person, if people look up to you for advice or they consider you any kind of a mentor, it's a great, it's a great sense of respect and it's a great compliment. He says, a great honor, a great compliment. He says tonight, I still got it. He says, I still got it. I'm like, yes, you do because you are a very good looking man. Even in the afterlife for him, you guys, he just very nice. Thank you for taking on your form.  They're kind of like a little more mysterious and kind of not squinty but kind of you know, they're not like super bright open. And when he smiles, he kind of smiles at one side of his mouth a little bit, he smiles many kind of cocks his smile to the side his jaw to the side a little bit. He's got a nice chin there. And then he's got like a button up shirt on. It's not a flannel but it has like that pattern like a kind of a plaid. I'm not sure it's not stripes and it's not checks necessarily but it's kind of like a it looks like a flannel shirt but it's not it's like a dress shirt. Does that make sense? But it's simple that's what he has and he's got jeans on and just like a it looks like a white or like a light blue shirt like t shirt underneath and I can see that sticking out and kind of a thing and that's it. He looks good. Looks great. All right. Oh, so your death was on expect very unexpected. You had a stroke. I mean, that's crazy.  I mean, I know that sounds kind of morbid. But did you have any kind of sense of that? He says not really. He says not not not anything that I would admit to. He says, you know, you don't you don't think about that if you if you're not feeling well or if you're having headaches or if you're not if you're not feeling great or you're going to the doctor and you're trying to be healthy and you know just like if your blood pressure is high or your cholesterol is high or he says, you know, you do things to correct that but not anything that I felt alarmed about nothing that I was like really cautious or worried about nothing major that I would have. So nothing that to be alarmed about or anything like that. He's talking about having like flu a little bit like flu life symptoms like his stomach kind of feeling upset and I don't know if he little legitimately was like sick a couple weeks before he died. I don't know but he's making me feel like my stomach's upset a little bit and like kind of how like sometimes people have flu like symptoms when they have heart attacks and so that would be the only potential indicator but he didn't actually have a heart attack he had a stroke. So a little bit different but he's telling me about oh thank you thank you okay okay I understand I understand now I understand what this message is. Luke Perry is saying it's important to be aware of your health it's important to recognize the morning signs for things like heart issues or stroke. It can happen to you even if like we have had this conversation even if you feel young and you can't believe that you you know have a child that's 18 he says even if you don't even if you don't feel like you're old and you associate having a heart attack or high blood pressure or stroke with old people he says quite frankly that's what people do you've got to pay attention to your health you've got to pay attention to your health even if there's no warning signs even if there's no family history you've got to pay attention that's that's one thing that I think is important that could come out of this that's good he said he says this is Luke Perry saying one thing I think that's important that could come out of this that's good is for people to recognize their health to to not to stay on top of that you know to be preventative is important to be realistic be realistic and be preventive and just be healthy as healthy as you can and some things aren't aren't you know aren't you can't avoid everything you can't prevent everything but it's it's a good idea to be informed and to take care of yourself as best as best that you can he says as best that you can and that's not going to stop everything that's not going to prevent everything he says but would it have stopped you and what's going on with you he says no he says no I you know that's something that I can't really answer if I had known more about the possibility of strokes or what the symptoms were what I have recognized probably not because I didn't that wasn't something that I was even thinking about I didn't I'm not you know an 80-year-old man I why would why would that be something that I would even worry about so I think it's a perception thing and that's the that's the part that can come out of this is to be to consider your health as a whole and not not not put it off as something that's oh that happens when you're old or that only happens to people who smoke or that only happens to people like this or that only happens to these kinds of people or people that do this or people that do that that's not that that's not the case that's not that's not the case and he says health is just health is important it's just something you got to do you got to take care of yourself but as far as prevention I don't know he's saying I don't think what happened to me can be prevented not at the time not at the time it happened maybe in the future at some point there'll be some kind of early warning signs or there'll be campaigns about it like there's campaigns about heart disease or breast cancer maybe there'll be campaigns about stroke and informing people about that but at the time that it happened to me no that wasn't even on anybody's radar nobody was even thinking about that really all right okay and he's saying he's sending a lot of love to his castmates and his family and his friends people that were so he's recognized that people that were so loving and saying such nice things about him and came out to the hospital to the memorial to the he says the wake to really show their love and appreciation and support for his family he's saying thank you thank you for supporting my family and my loved ones and my friends who he says obviously had a very hard time with this he said I put myself in their shoes and if it would have happened to one of them I I would have been devastated it would have really been hard for me and so there's this like he's saying thank you thank you for respecting my family and and thank you to all of the love all those who said such kind words and wonderful things and I appreciate that he says I appreciate that very much thank you thank you for that he's saying like there's a girl a young woman I think her name is it's an s name like Sophia Sophie he's mentioning I don't know who that is if you guys know who that is put in the comments below Sophie or Sophia and he's making me see her like hug him and stuff and so I don't know what that's about and it looks like he's laying down if she's hugging him so I can see that I don't think it's Sarah I think it's Sophie I think it's S-O-F-I-A-P-H-A I don't know and then I also see Archangel Michael just steps in right now so that's beautiful thank you very much Mr. Luke Perry and thanks for waiting for me to do all my chit chatting because you have been showing up to me for the last week and that would be the end of June and the early July this I'm recording this on July 2nd 2019 so I don't know if you have a birthday or if there's somebody that you love that had a birthday or an anniversary or something at the last week of June the first week in July if you know if you're watching this go ahead and put that in the comments below if there's a significance like a birthday a child's birthday a significant other a spouse a loved one's birthday his birthday an anniversary a marriage whatever last week of July first week in or I'm sorry last week in June first week in August or for last week of June first week of August because he's been here for at least 10 days I've been feeling him a lot a lot and then somebody just commented at a above-life channel on another video hey can you do Luke Perry and I'm like yes he's been around I've been thinking about him great minds think alike you know so so thank you for that and thank you for giving me the opportunity then Luke is because connecting with you I was thinking well how long has it been since he died I'm feeling like it was like May or April or something I don't know exactly it wasn't that long ago but I'm like it really opened me up and then after the session that I had with that woman's mom showing up and just recently had died and how easy it was to communicate with her and just really opened me up and so Luke I thank you for being part of that I appreciate your help and I was totally a fan of my autono and I thought Dylan was awesome all right thank you so much for being here I appreciate it and thank you for being here at above-life channel I'm Bridget it's my pleasure to help to inspire your spirit to fill you up with hope because this this is your life now go live it just live it thanks for watching


Welcome to the journey. Today we're gonna play a little game. And guess what? You guys can play at home too. We're gonna discover the top five most expensive domain names. We've bought a domain before, or one of your friends, and it's ranged from a dollar to ten or fifteen bucks, kind of like a lunch date. But it actually can get as high as thousands of dollars, tens of thousands of dollars, which those are considered premium domain names. And this might come as a shocker, but actually some domains sell for millions of dollars. And this is happening every day, day in and day out. So on our game today, we're gonna explore the top five most expensive domain names. So when you think about your premium domain names, those higher price, tens of thousands of dollar domain names, I like to think of it as an expensive neighborhood. So maybe the Lower East Side in New York, or you're on the West Coast like me. So Beverly Hills, Rodeo Drive 90210. And so similar to those neighborhoods, they're in high demand and with higher demand, higher price tags. So you might be at home wondering, why would I spend that much on a domain name? Well, it's pretty simple. You spend more for that desirable domain name.   So you might be at home wondering, why would I spend millions of dollars on a domain name? Emma mentioned 10 bucks, 15 bucks for one. Well, think about it like real estate, right? This could go up in value. I know with marijuana.com back in 2001. It sold for a million. 10 years later, guess how much? Four million dollars. So that's a reason you might want to consider buying a domain now. Spend a little more than what you might expect, but because it's gonna grow in value later on. Then you can sell that, reap the benefits. Put that in your pipe and smoke it. All right, and with that, without further ado, let's dive into the five most expensive domain names with our game and our contestant, Sam from Austin, Texas. Sam, the moment everyone's been waiting for. I'm gonna put you up for a challenge. We have five domain names here. These are the most expensive domain names. And what Sam is gonna do is organize them in 60 seconds, according to the right price. No pressure. Are you ready? Ready. All right, let's hit the clock. Go. 60 seconds, Sam. So how'd you do your studying for this? Or is it distracting when I answer? You're distracting me. Okay. All right. Clock's ticking. Sure about that voice one? We'll see. All right. All right. Let me check in with our judges. Judges, you got one right. So you got 45 more seconds. Start organizing those. And if you're at home doing this, don't cheat. Don't Google. Clock's ticking, Sam. Don't ask Alexa. Don't ask. You're going to home. All right. Let's check in with our judges. You got two right. How many more seconds on the clock? Seconds go. Wouldn't be great to know which two you have right, Sam. It would be. That'd be helpful, huh? Which one are you feeling most confident about? All five. All right. You feel good about this. You do know what the prize is, right? Judges, how many does Sam have right this time around? Four, you got one. Then you got two. Well, you're back at one. Now, one right. How much time do we have on the clock? Game is rigged. 15 seconds, Sam. Let's go. Rethink your whole system because you went from one right to two right to back to one. This grand prize is looking like it's going home with someone else. Right. Get down to the wire. This is hard. Five, four, three, two, one.  All right, Sam. Thanks for playing. You got two right. Let's go ahead and reveal what the top five most expensive domain names are according to price starting with 49.7 million dollars. The correct answer is... Pretty confident was that. You feel good about this? Yes. If that's true, carinsurance.com. The second one, 35.6 million dollars is actually insurance. Oh, come on. Yeah. So let's switch that one out for our audience at home. And as for the 35 million dollars, you did in fact get this one right, vacationrentals.com. Have you ever used it before? No. Recommend it. And for your 30.1 million, I'm sure you can figure it out. Switch these privatejet.com and coming in for a 30 million voice.com. Game is rigged. So Sam, have you ever spent a lot of money on a domain name before? No, I haven't, but I understand why. You buy these domains that have all these people that know about it. You have the traffic, so the entrepreneur doesn't have to fight an uphill battle. So you can make it easy for yourself and buy something that already pays the road out for you. Totally. I'm all about making life a little easier. Work smarter, not harder. So that's a wrap. You've learned the top five most expensive domain names. Be sure to like, subscribe, and comment below on our video also. Ring the bell so you'll be the first to be notified when we have fresh new content. This is The Journey.


It's easy. It was a big day. You have a director here? You have a director who swaps these things together? No. Okay, fine. Mr. President, one of the primary concerns of many of Radio Free Europe's listeners is their separation over the last four decades from the rest of Europe and the sense of loss they feel as a result. In your remarks on the Normandy beaches last year you spoke eloquently of quotes the great sadness of this loss echoing down to our time in the streets of Warsaw, Prague, and East Berlin. The Soviet troops that came to the center of this continent did not leave when peace came. They are still there, uninvited, unwanted, unyielding. Mr. President, what can the United States do to overcome this artificial division of Europe? What can the other democracies particularly in Western Europe do? Do you see a particular role for Radio Free Europe in this crucial regard? I believe that the principal thing that we in the United States and Western democracies can do and must do to overcome this artificial division of Europe is to stand for freedom, democracy, rule of law, unconditional individual human rights, and governmental legitimacy by the consent of the governed. Forty years ago, American and Soviet soldiers met on the banks of the Elbe and they celebrated the V.E. Day in the spirit of comradeship cemented by blood. The event was symbolic of the hopes of many ordinary people both in America and the Soviet Union that the wartime alliance would lead to peacetime cooperation between the two great nations. Needless to say, these hopes proved illusory. But looking back to those promising days, what are your feelings and thoughts concerning the great chance and great challenge the world has missed? And what can now be done to ensure that the peace begun in 1945 will endure? We greatly appreciate the enormous sacrifices the peoples of the East made in the struggle against Nazism. But the great hopes for post-war peace proved so illusory because they were based on an unrealistic understanding of what it took to create real peace. People somehow forgot that real peace is indivisible from respect for human rights. Great. I think you have a career after this.


for a C sharp code into functional style. Best time to ask questions or make comments is when you have it, so please don't wait till the end. Any time is a great time. So I want to talk about just a little bit and then get into some code examples after that. What do we really get out of functional style? So a couple of things very high level to highlight. One is declarative, meaning the code you're writing is really telling you what to do rather than focusing on how to do it. You let the underlying libraries decide how to do things. You're using higher order functions, meaning you can pass functions to functions, receive function from functions as well. You honor immutability. We talked about this during a few sessions. So you are trying to prevent immutability as much as you can. You are honoring immutability, which takes a little bit getting used to, but that's a better way of programming because there are fewer moving parts in it. And you also honor pure functions. Pure functions are functions with no side effect. You're not trying to mutate state. While the function is running, you're not modifying something outside. While the function is running, something outside doesn't affect the outcome of the function also. But why do all of this? First, the code is more concise. I want to distinguish between the two terms, concise and terse. A terse code is short, but waiting to hurt you. Concise code is short and transparent. So we want concise code, not terse code. And usually this code ends up being very concise. It's very expressive. So it's very easy to read the code and understand, communicate your intent much more easily. We usually end up writing a lot less code. And as a result, it's easier to understand because of the expressiveness. Once we get used to the syntax, it's easy to modify the code because of the way it's structured. The code begins to read like the problem statement. We end up having fewer bugs in the code as well because of fewer moving parts in it. And almost effortless to paralyze and make it efficient as well. With all that said, it's really a paradigm shift in terms of how we used to code to where, how we want to code. So I want to start with some examples to work with it. The first is about iterating. One of the reasons I want to talk about this is I work with quite a number of clients who also use C-sharp. And when I start working with them, one thing I noticed quite often is they still continue to write code the way they used to using the traditional for loops. And they haven't quite made the transition even though C-sharp has had functional style of programming a Lambda expression for a number of years now. So let's talk about iterating just for a minute with a little example here. So what do I have on my hand in this case? Notice I have a little C-sharp code. And the code has a list. And I'm looping through the list one element at a time and I'm printing it. That is all I'm doing here. So this is a very familiar code, right? So you have a list of values, the four i equal to zero, i less than the count, i plus plus, and then you print the value. Now this is called an external iterator. And an external iterator is where you control the iteration all by yourself. Now there's a good news about this iteration. Normally people say this is a simple iteration. But I wanna say the word is not simple, the word is familiar. There's a very big difference between the two. Not everything that's familiar actually is simple. Something that is familiar is something we have kind of accepted even though it may be really complex. In fact, I would argue this code is complex because it's got way too many moving parts in it. Now take a look at an example here. I'm gonna say for each and I'm gonna say element in numbers. And I wanna output the element. Now notice these two code for a second. You can no longer claim this is simple because we simply saw another one that's simpler than the other one, right? Now why is the code on line number 19 simpler than the one in line 15? And the reason for that is the one on 19 has fewer moving parts. You are not initializing a variable. You're not setting a boundary condition on it. You simply said for each of the elements do this. Both of them are external iterators. However, the second one is simpler than the first one. We could have done either one of them and she sure has had both of those for a very long time. However, we would much rather do internal iteration rather than external iteration. So notice rather than that about two, we could rewrite this. We could say for example numbers and then we could say for each. And we could start using the internal iterator on this and we are saying for each of the values in this collection, I wanna perform an operation. So given an element, I wanna output the element in this case. So we are trading our external iterator to an internal iterator in this particular case. Now if you look at this particular code, the idea behind this code is you are rather than controlling the external iteration, you are relying on a polymorphic behavior. Now what is polymorphic in this case? You're calling the for each on the collection which means the iteration could be sequential, the iteration could be concurrent, the iteration could be lazy. Whatever those options are, you can gain from those because as we know polymorphism, go ahead and call a method on an object but the real implementation is postponed to run time rather than being decided ahead of time. So this gives you that flexibility to pick and choose the implementation at a later time. This could be a collection, could be a parallel collection, what have you. That benefit comes to you when you start using this kind of behavior. The code is also concise as you can see, expressiveness of course, we gotta get familiar with the syntax but it's expressive because you're saying given this particular collection, I wanna do some operations with that collection, that's what you're expressing. So the idea really is that you are getting to the values very effectively to iterate over them. So in this case of course, I am asking you to iterate through the values and perform the operation on the values in this collection. So the idea behind this is it's an internal iterate. So what does an internal iterator really mean? The internal iterator means that I'm gonna send a function. This is a function that we are trying to send. So I'm saying for each and I'm making a mistake here, I'll figure out what it is in a second. So I'm saying for each of the methods, I wanna pass in a function as a parameter. So notice rather than saying do the looping and do this work, you are asking it to do the work but you're sending the unit of work as a function. So given an element, I wanna go ahead and print the value of the element, that's what you're commanding in this particular case. So that becomes a very natural way to express once you get used to the syntax, please. Right, so in the case of ordering, by default, this is a sequential collection. So the iteration is gonna be sequential. In the case of printing out, you're absolutely right, the ordering does matter. But in a lot of other cases, the ordering doesn't matter, right? So you need to pick and choose when it doesn't, when it doesn't. The for each itself is going to be a simple sequential iteration for most part, so it wouldn't be a problem for it. But on the other hand, if I'm doing some mapping operations, let's say for a minute. Well, if I'm performing a mapping operation, I can certainly do maps more concurrently rather than doing it sequentially, right? So you gotta pick and choose when it makes sense to perform one operation versus another, and that is pretty much domain and context dependent. You can't really make a claim one way or the other. You gotta make a decision based on what you're trying to really do, and that's basically what you have to pick and choose. So the idea really is that you wanna really make a choice based on what you're trying to do, basically based on the domain that you are working with. I'm not sure exactly why this guy, oh, I know why the problem was. I need to include import over here, that's the reason for it. I actually have a generic import, so I'm not sure exactly what the error was. Let me see what the error says over here. Okay, so I had a mistake here that I couldn't recognize what the error was. Anyway, so you can see the iteration works just fine by providing, that's the lambda that you're passing to this function for it to exist. Okay, now let's go a step further. What if I want to perform a filtering operation? What does that really mean? Let's take an example for this to understand how the filtering is gonna work, and then we can compare and contrast it. So let's look at the old style of coding first of all. I got a collection of values, and what am I doing with this collection? With this collection, I first set filtered and I created an empty collection as you can see here. Then I loop through one element at a time, and for every element, I check if it is even, and if it is, I add it to the filtered collection. Then I loop through again and print the values. Again, you can see the imperative style of coding right here. Now, if I run this code, we can see that in this case, we only printed even values from the collection. So that isn't again an imperative style of coding, but as we get used to the code, we elevate ourselves to more of a declarative nature. Let's see how that's gonna feel like. So I've got numbers, but what am I interested in doing here? Given this collection, look at what this code was doing at a very primitive level. It loops through one element at a time, checks if a value is even, and if it is, it adds to another collection. In other words, this is really a filter operation. So what I can do is I can say, given these numbers where, so where is an operation I perform, and normally in functional programming, we call this a filter operation. Well, in C sharp, they didn't call it a filter. Would have been nice if they did, but they call it a where instance. So this is kind of like saying, given these values, only do this operation where this predicate applies, right? That's what you're trying to do here. So where, given an element, you can say element mod two is equal to zero.  So this is gonna give you only the values that are meeting that criteria. Then you can say for each, and for each of the values, what do you wanna do? Given the element, I wanna go ahead and print the element out from that particular result. That's what you're trying to do as an output operation, right? That's what the for each is doing here. So the idea behind this is, a where operation simply says, select these values, and for these values that are selected, you know, give me a result, a collection, and I could loop through and print the values, whatever that I wanna do, I could perform at that particular operation. So the idea behind this is simply to bring in the operations, and of course, because, okay, there's another small detail. The for each is only available on a concrete collection, unfortunately. This is a bit of a let down, in my opinion. So as a result, you have to escalate that to, or down, bring it to a list object. So to say, I wanna iterate on the list and print it. Would be nice if you don't have to come to a list and still continue with the operation further. That would have been really nice to work with. So the where operation does the filtering operation for us, and then you can bring down the filtered operation. I'm gonna bring the code here with the error that's displaying. So where, again, the operation that we performed here, do list, and then for each, and I'm performing that operation and printing the result, and getting the output. So notice the difference between the code again. You're not at the low level of operation. Instead, you elevate it to a higher level and you're flowing through. This is a function composition or transformation you're looking at. So numbers where that criteria is met, put the result into a list, and then from the list, go ahead and loop through and get the results to me. So what's the model of the story? We should really deprecate or expire the traditional foreign moves and go more towards internal iterators as much as possible. Now, what's the biggest difference in doing so? The first difference is we are going from an imperative style to a declarative style. So in the case of imperative style, we specify every single step of not only what to do, but how to do it. Think about the code we had a minute ago. Go through each one element. Take one element. Check if it is even. If it is even, then add it to this list. Notice how you're focused on every single low-level step. In the case of declarative style, you focus more on the high-level step. You say, here's a collection. Perform this operation where elements meet this criteria. So you're focusing more on the whole rather than each and every single value. You are focused on how, in the case of imperative, you're more focused on what in the case of declarative. You say what to do rather than how to do it and you let the underlying library functions take care of it. You are dealing with mutability versus immutability. If you recollect the old code, what did we do? We loop through and we said add, add, add. Well, add is a mutable operation. You take a list and you keep poking at it and you're adding elements to it. And obviously, that's very difficult to make concurrent as well. In this case, you don't have any mutability at all. In fact, you just ask it to do the work and you tell them, give me a result, a resulting list. So you're not in the business of creating a list. You are in the business of telling what to do and it gives you a result of a list as in response. So you avoid explicit mutability in this code. You have side effect versus pure functions. What is the side effect in the other code? Well, the mutability certainly is a side effect. You're sitting there and constantly modifying the collection, whereas in here, you are not really mutating anything at least explicitly. Mutability may happen under the hood, but your code is not doing any mutation. So you're focusing on pure functions. You accept data and objects in imperative code, whereas here you are accepting functions as well. Notice in this code how you are able to receive a function as a parameter rather than just passing objects alone. So that is where the where is a higher order function because you're passing a function to this function rather than passing objects alone. So you're doing function composition rather than object composition alone. So that gives you the benefit of putting together this function composition. In the case of functional style, imperative style, it's hard to compose. Remember the for loop that you had? What do we call this? We call it a for statement. You do one for, you get the result, then you come back to do another for and another for. So if you notice the code we had, we got two for loops. You could merge them into one, but that's trying to do too many things in one place which only makes the code more complex. Whereas here, you got a nice function composition. Operation one, the result of which flows into operation two, the result of which flows into operation three and you are transforming this code, the data nicely. That's function composition at work. And rather than mutating data, you are transforming data. So it feels more natural to say, this is the current state, this is the new state rather than saying this is the current state and I just polluted it with the new state, the old state is gone, right? So you're preserving the value that you had and you are making a copy of it. Now of course you may say copying is inefficient, well it doesn't have to be inefficient. That's where the smartness of the libraries and the language comes in and we'll talk about how the efficiency is not compromised in just a few minutes. Now let's look at one more example. I want to double values let's say in this particular case. How do I double the values? Well for doubling the values what I'm gonna do is let's take one other example and work with it. So this is called doubling the values and again look at the low level code. I got a collection of values. Then I take the list, I loop through every single element and I double the value and then I add it to the list. Again notice the symptom of imperative, mutability at work, specifying things at a low level per element. Then we loop through and print the values. But this is doubling the values. What can we do to avoid this? So notice what I'm gonna do here. Numbers start, well in this case we are not filtering any values, right? So this is a transformation where we wanna take a collection of values but we wanna produce another collection where every element in the resulting collection is a double of the values in the input collection. So for this we use a select method. In functional programming we normally call this map. I wish they had called it map here as well but they called it select. So what does select do? Select says given an element return whatever that may make sense. In this case I wanna return double of those values, right? So this is essentially a mapping operation. Again notice how you focus at the high level rather than the low level of this object. So then I can say for example a two list and then I can say for each and I can specify what the value is and I just realized what my problem was. I was typing a lower case F and that's what happens when you program in two many different languages your brain doesn't switch over it's gotta be uppercase and C sharp, there we go. So E is the element, what do I do here? And I wanna print the value out here, right? So that's what I'm trying to do at this point. So the main idea behind this is compare the code up here to the code below, right? Concise, high level, expressive to the point and it feels like you're speaking to an adult rather than a toddler, right? So at the highlighted code you are sitting there and babysitting through every single step. Whereas here you're saying given this collect perform this mapping, give me a list and print the value, right? So it begins to read more natural once you get used to it compared to the previous code. Now think about this for a second. If you are looking at the top code and somebody comes to you and says take the highlighted code and make it multi-threaded because this operation is too slow I wanna make it faster. The short answer is tough work, right? In the bottom code I don't have to do much work at all because I could use a parallel collection and the select can go concurrently. I don't have to expend any effort. Structurally the code is gonna be exactly the same so that has a very big benefit as you can see, please. Sure, why? I want to multiply by some number. So let's take an example here. Yeah. Just as an example let's say even numbers I wanna double, odd numbers I wanna triple. Yeah, something like that. So notice the beauty here. In the code about what would we do? We would say if element is even, then you would say double dot add and then you would say, for example, E times two and then you would say else E times three. Well, we could probably make that a little bit better by storing the result temporarily. You could say int result equals and then you would specify this as a result over here, you get the point, right? And then you would do add once. But in a sense, if you really look at it, you have kind of lost sight of what you're really doing. Why? Because you gotta step into the code and you gotta examine that and say, what are you really doing? And then you're like, oh, I got it, right? In other words, this fails a very important principle called slap. It stands for single level of abstraction principle. Single level of abstraction principle says when you have a code, the code should focus on one level of abstraction. And if you look at this code, this is all over the map. Everything happens here, right? There is absolute disregard to abstraction, right? Oh, I've got to loop. I've got to work with the collection. I've got to, now, all of a sudden, I'm making a low level decision. I've got to make a comparison, right? So look at what we lost in it, right? We got everything going on in one place. Instead, let's go ahead and go to this code in the bottom and let's just go ahead and say, just as an example in this class, let's say static int. Let's give it a name, right? Whatever that operation you could, we'll call it as transform, well, let's say double or triple, whatever you want to call it, right? Based on your domain, it's going to have some logical meaning. And then you could say int number, and then what would you do here? You could simply do something like number, well, return, of course, and you could say number mod two is equal to zero. If it's even, then return number times two, otherwise return number times three, right? Whatever that may be, the logic, you can implement it separately. Now that is a low level detail, would you agree? That's why it's a slap, right? You isolated that into a separate method because that's where that logic belongs. Then you say double or triple, and I will simply come up here and I would say double or triple, right?  So this says select double or triple, meaning map that on that operation, then convert to a list and do my work. Then the low level detail, see how this promotes doing the right thing. So that is one thing we need to keep in mind, right? A language should promote good behavior, imperative code promotes more bad behavior, right? It is inviting you to do more bad stuff, right? Whereas here, it's like, you know what? If I put a massive if-else condition here, that's gonna get very stinky very quickly. And then you're gonna look at this and say, well, I don't think I should be doing that. That clearly is not the right thing to do. Now we follow the slap principle, right? A single level of abstraction principle, and we moved it down. So that is another nice thing, is the language should provide us the right behavior, as you can see, right? Really good question. So notice how we moved this down, and then we can say, you know, even things are doubled and odd things are tripled, or whatever that logic is, that's where it belongs. And so we also applied a slap, single level of abstraction principle, which is a better, better healthy coding anyways. We'll explain it. Thank you. Absolutely, really good question. So that is an example of how we can go towards that. Well, this also leads us to being lazy. And the point about being lazy, this is a great example to look at it. Notice in this example, I have done this operation here, but this operation of select is happening right here. Let's go ahead and just output for our purpose. Let's say, you know, done. You could notice in this case, I could go back and write this just to show that this is being called, called for, let's say, number. So if I run this, you can see those are called for each of those numbers, right, makes with sense. But the beauty is this. These methods are, they are very deceiving in a way. When you look at them, you don't see this. It appears like they're here towards poor performance, but they really are not. Because if you look at this collection, we are saying select, meaning map on these, then convert to a list and then do this operation. Let's say we don't care to convert to print right now. We'll just keep it as a to list for a second. And when I run this, you can see those things are being done also. But if I go back and remove that part also for a second, did you notice no work was extended, right? This is like, I was mentioning this earlier, this is like some people at work. They come to work, look around, the boss is not at work, hey, great. I don't have to do any work today, right? So these guys are lazy to the bone. So even though you call select, the select says, I don't have to really do any work because my result is not used, so why bother doing the work, right? So we talked about earlier in the Haskell session, if you were there, we talked about how these functions can be lazy. That's exactly what you see here, right?  And the select says, and later, I don't have to do this now, right? So it postpones it. And how long does it postpone? You could do another, right? So you could say dot where, and what do we wanna do? Given an element, I could say element is greater than five, for example. So notice in this case, still no work was extended. So all that work that could have been done was never done. And then you say, now I wanna convert this to a list, only now it is doing the work, not otherwise, right? So in other words, these are terminal operations, and terminal operations don't take effect, I'm sorry, intermediate operations are these. Intermediate operations don't take any effect until terminal operations kick in. So this is laziness baked in. And laziness automatically gives you efficiency and code. If we had written this code through the imperative style, we have to work hard to get that kind of efficiency, right? Because our code is eager all the time. But there's benefit to being lazy. What's the benefit to being lazy? Well, if I don't ever have to do this, then avoid it doing the work, right? And if you avoid doing the real work, then you're more scalable, because then you spend more effort doing real work that you need to do, rather than spinning the wheel doing stuff that is of no consequence anyway. So you can see that laziness is already built into the language. Where is lazy? Select is lazy already. And there are these functions that are absolutely lazy already, and all we have to do is just use them. So there is another benefit to using these, instead of using the looping as we saw before, because we got the laziness baked into it. This is something that really fascinated me, called the tell don't ask. We all write code like this all the time, and we tend to forget about some nice principles. And thanks to you, we talked about one extra principle, which is the slap principle. But one other principle in good object-oriented design, or good design in general, is called the tell don't ask principle. The tell don't ask principle says, do not go to an object, perform a query on it, then make a decision, and then go back and affect its state, right? We tend to do this quite a bit. You go to an object and say, hey, how old are you, for example, not you specifically, but how old are you? And you find out what the age of the person is, then you make decision for them, and then you go back and say here, you can have this or you cannot have this. Well, rather than that, you instead simply tell the person, you know what, here you go, do this if you are eligible to do, right? Then your code becomes a lot simpler, and b, the function you, the code you are calling, can evolve polymorphically. Tomorrow, you have to decide, let's say for example, let's take an example, right? Let's say age has to do with something, maybe the voting loss. Let's say, hey, if you are less than 18, you cannot vote. Well, who makes the decision? I'm gonna make the decision. I'm gonna ask you, how old are you? And then based on that, I'm gonna make a decision. Well, imagine there's a state law change, and one state which is agreed to get more votes decides. People who are older than 16 can vote in that state. What's gonna happen to the code now? Your code is dead in the water, right? Because now your code has to say, well, if you are in this age, and if you live in this state, then, and that is gonna become a mess to deal with. Instead you say, hey, person, vote if you can. Well, the person decides whether the person can vote or not. Well, tomorrow, the state law changes. Well, the person living in the state evolves with it. Your code is still intact, it's extensible, right? So extensibility is attained by removing responsibility and placing it exactly where it belongs. I'll give you one example which I ran into which was quite fascinating to think about because sometimes we do this and don't realize it. So let's look at an example of, I call this the ask example, and let's take this example to see what it feels like. I've got a class called room, and the room class contains a Boolean field to say whether the room is booked. I've got a constructor that tells me whether the room is booked on create. I've got a ease available method that returns to me whether the room is available or not. And then I have a book method which is going to take a date and perform a booking operation, right? So notice the way this code is structured, it's structured for the ask rather than tell, right? So you would first go to the object and say, are you available? It says yes or no.  Now there's another inherent problem in this code. By the time you ask it if it's booked, to the time you come back to book it, it probably is taken already. That's more fun for you to deal with, right? So this is again going back to what we talked about in your previous question, right? We impose this complexity, right? We deserve punishment for this because this is accidental complexity we introduced on ourselves. That is the room class. Now it's even worse. Look at this code now, what does it do? This code says I got a bunch of rooms on my hand. I'm gonna first say room is null, right? What is null? The way you pronounce null is smell, right? That's what it really is. It's very smelly. So you got a null variable on your hand. Then you'll loop through every single room. You ask if a room is available. If the room is available, you book it and then you set this variable to the room and then you break out of it. Notice a very primitive set of code that we are using here. And once we do, then we print what the booked room is. There's another problem here. It is quite likely that the book room is actually null at this point because all the rooms were taken, oops, sorry, all the rooms were taken and as a result, we ended up with no room and we have to deal with it. So that is the consequence of this code. But how can we get around it? Well, I was actually working on something when we wrote a little unit test, we wrote this code and I looked at this and I stared at it and said, okay, something doesn't feel right here. This test passes, the code is there, but you have sometimes that feeling, right? You know something is wrong, but you don't know what's wrong. There's a little gut feeling that something is smelly but you can't put your finger on it. So we're working with this and we wrote this code and left a little unhappiness. What is the problem in this code? And after a few minutes of thinking, it jumped on as like, ah, I get it. It's a failure of tell, don't ask principle because we are querying the object, making a decision and then going back and setting things. So rather than doing this, what we could do is we could rewrite the room. So what we can say here is rather than ease available and do this, how about the following? We could simply say public void, book if available, right? So one shot, book if it's available and we're gonna specify the date and time, whatever that information it needs, date. So we can pretty much make these methods as private methods for now. These are not accessible anymore. And then we could simply say in this case, we could say if, well, first of all, we could say available equals ease available for, ease available for date, right? So first we check, well, if it is available, we still have to say whether we got it or not. So if it's available, what do we do? We can simply say book on that date, right? So book on that particular date. So we could simply say date and return the availability, right? So this will tell you whether you were able to get it or not. So book is available. Well, if it's not available, don't book it, right? It's gonna be false. If it was available, then go ahead and book it and return it, true for me. So we converted this into a one function called delegating the responsibility. What is the benefit? Tomorrow, the logic on booking changes. There's a special rule. Some rooms cannot be booked even if it's available if it is a certain period of time. You know, maybe a high season, whatever it is, right? Well, where does that logic go? It rightfully goes right here. But in the previous case, we'd be polluting the code with that logic where it doesn't belong, right? So that is basically the difference in this case, we wrote this method. But then what we do is, remember that laziness we talked about? Well, we can leverage the laziness very nicely. So what we're gonna do for that is, we got a list of rooms. So rooms dot, and we can simply say in this case, where. So once again, we are applying a filter operation for this guy. So we say where, and what do we wanna perform in the where? Well, given a room, we're gonna tell him room dot book if available, right? And then we're gonna specify the date that we are interested in. So what is that particular date we are interested in? Well, date dot now, so we could simply say date equals date dot now. So we are asking it for that specific date. Well, this is a filter operation, so what does it do? It gives you all the date rooms that are available. But no, we don't want to book all the rooms. We only wanna book one room, right? Whichever is the first room that's available, that's all we are interested in, not book all the rooms. So we could then take that, and we could ask for the first one to be available. Now when you look at this, it is not intuitive until unless you know about the laziness of functional programming, right? So when you say do thousand things, but get me the first one, it won't do thousand things and get you the first one. It'll only do the first thing and get you that. This is especially important from the point of view of infinite and lazy collection, because you don't even know how far this is, but you ask it to do only minimum work to get the result for you. So if you look at that code, compared to the code you have in the bottom, notice how we went from again an imperative style and failure of the tell-don't-ask to simply saying, hey I tell you to book and get me the first one, whichever is available, right? So you can bypass a lot of work and focus on applying these kinds of principles. It takes a bit of effort to rethink about it, but to me the best design tool ever in my opinion is how do you feel? To me that is one thing I always listen to. I would write a piece of code and I would be walking around and I would tell myself, I am not happy with this code. Sometimes the kids come over to me and say, Daddy are you really angry right now? He's like, no it's not you kid, it's the code that's making me angry, right? So you gotta feel that anger in you, right? I wrote that code, it stinks, I'm not happy with it. And then in a matter of minutes you will refactor it and find a better way to do this and that can be pretty helpful to rewrite the code in a better way and that can help us a lot in getting the things done very differently. So let's go back and look at this example real quick. This is gonna be the book to room that we are interested in and I could save that away into book to room. So we could save for example room and that's gonna be the book room equals and we can store that away into the room. So the idea really is we are again using a very, very high level of code. So did you notice what he did? He did checking, checking, checking, room booked and then he gives you a room but how many do we have? I have one, two, three, four but it checked the first and the second. They both are booked already. Then it checked the third which is the first one that's available but notice it never checked the fourth one because the third one was available, it booked it, right? So that's why the where doesn't run all the way through the where runs only until it pleases the first, right? The where works for the first. It's extremely lazy, right? It's like, hey, you wanna report? Here, are you happy with it? Yes, I don't have to write anymore, right? So you're just working for just to serve the terminal, the laziness takes effect. So the code becomes very expressive as you can see because of that in this particular case. So what we saw here is a very systematic imperative functional rather than being low level at element level, be at a high level at the collection level, right?  So we are saying, well, here is an operation but I can postpone the operation until I really have to execute it and you can see how the laziness comes into play here by writing the code in a very highly elegant way by simply saying, go ahead and do this for me at this level and get me the first element. So the laziness, without laziness, this code would be incorrect as far as the logic is concerned, right? Because poor thing, this would book all the rooms and get you the first one, which is complete nonsense. We don't want to do that, whereas the laziness comes to help here. It only books the first available room and gives you that value, right? Of course, you can't make this quite parallel because it may end up booking multiple rooms. So going back to the earlier question you asked, we got to be careful whether to make it parallel or not. We got to know the logic, right? Oh, no, it is hard to reason because of unfamiliarity. That is something to keep in mind, right? When you are unfamiliar with something, it is hard to reason. That is why I keep saying several times once you get comfortable with functional style, right? So when you start working with functional style, your eyes should start looking at laziness. But remember the very first time you looked at polymorphism and said this is gonna be hard to reason, right? Because what does polymorphism do? You call a method here, it ends up over there. It's like how cool that is. And there are people scratching their hands is that really cool? That can be hard to understand, hard to debug, hard to work, right? Same similar concept. So once you're familiar, your mind thinks along those lines, then it becomes easier to reason. It's like, oh, I got this collection, I applied this operation, get this result. It becomes easier to express that. But again, you have to know when it makes sense to parallelize and when not to parallelize. A lot of times parallelization is useful when you have optimization problems. You don't care which results you get but you want one of the results that would make sense. Whereas in these kinds of cases, you gotta be very careful which one you are really getting as a result. You gotta be very careful about that too. There's also one small consequence in this code which is this code actually has a side effect, right? Because you are modifying the room and so in effect you are mutating it, which is really something you gotta be very careful about because you're altering that. So an alternate may be to return a copy of the book to room and the original rooms are left intact so you can work through that to avoid the kind of mutability if you want to. But that's basically the idea is systematically going from imperative to declarative and functional, avoiding for loops, trading internally to raters and working with these higher order functions and then thinking about formulating the problem in a way it becomes more expressive. So fewer lines of code which is more expressive is better than a code that is convoluted and then of course we also saw how the single response of the principle the single level of abstraction principle all that is much more expressed beautifully here compared to in the imperial style of coding, right? So I hope you found that useful. That's all I have. Thank you.