What's up everyone, Takedown here, welcome back to the channel today and maybe talking about the PlayStation 4, what's going on with it and why people seem to be in a rage about it. So, let's just get right to it. Recently, the CEO for Sony has announced the PlayStation 4 is at the end of its life cycle and a lot of people don't know what that means, they're assuming by the title that it means the PlayStation 4 is dead this year, it's the last year for the PlayStation 4 and that next year the PlayStation 5 is coming out and if you read the entire article you would know that is just not the case. So, for a company like Sony that is releasing a big product like the PlayStation 4, it's five years old right now and they already started seeing a decrease in profit, last year alone they made $6 billion profit for the PlayStation 4 and they're at the peak of profit annually for the company. Here on out, he has announced that they're going to start losing money every year, not really losing money but they're going to be making less profit yearly and then that's going to make them consider releasing a PlayStation 5 which they likely already have in development, it takes years for something like that to be developed so they already are developing it in my opinion but he did not say anywhere that the PlayStation 4 is dead, that the servers are going out or that the PlayStation 5 is coming out, people just didn't read the article and they're just assuming by the title that's what he meant and it is not. He said by 2021 that's when he expects that they're going to start considering strongly to release the PlayStation 5 to bring their profit back up for a new system which makes completely sense, by then the system would be about eight years old and that's what an average system lasts until the next one is released and a lot of people to me it makes no sense why they're saying the PlayStation 4 is going to be dead when the PlayStation 3 servers are still online. They're not going to cut the PlayStation 4 servers if the PlayStation 3 servers are still online. People just don't think they start making allegations, they start saying things that they think is true and or stuff that they want to believe is true like the PlayStation 5 coming out which is just not the case. I think there's still some big things going to be coming soon for the PlayStation 4 new games coming out that they've already announced and it's just not time for a new system in my opinion, I don't want to buy a new system every five years and it's just not something I'd like to do. One thing that they're still gaining a little bit more profit from and the reason he thinks it's not going to be until 2021 till a new system comes out is because there's a lot of people and a lot of new subscriptions to PlayStation Plus that are happening right now, a lot of reoccurring people and new people purchasing the PlayStation Plus so it makes sense that that's kind of making up the difference from them starting to lose profit for the PlayStation 4. They're still making six billion dollars profit for it every year now but it's going to start going down and making them less and less profit moving forward so I just want to make this video to kind of tell you guys that that's the real case that's why that's what he meant by the end of a life cycle and also that the original PlayStation 4 is out of production right now but that doesn't mean all PlayStation 4's are, there's the PlayStation 4 Pro, there's the other one that's out so I mean there's still gonna be making the PlayStation 4 for years now there's not gonna be cutting it off anytime soon and I just wanted to tell you guys that and give you guys more information because I see a lot of people on Facebook, YouTube, Twitter and everywhere else on the internet saying that they're gonna be ending the PlayStation 4 and the PlayStation 5 is coming out and I just I don't like people being misled so that's why I wanted to make this video. Hope it got hope it did help you guys understand more of the situation hope you guys did like this video if you did please leave a thumbs up and it'll help me out more than you guys think and I'll see you guys in the next video please take care peace


Matt Ritchie corner, she's dribbling low. They're talking about keeping the ball on the floor and that's exactly what Matt Ritchie's done. He's drilled that corner in. That's a training ground routine. There's no doubt the ball must have worked on it and it's worked to perfection. A couple of times he's got under pressure with those high balls he hasn't dealt with. Here's King, Bobbing-Bolsterborn on deep end stoppage time. It's game on. That's a great strike from King. He did a couple more of them from in today but right at the end there, look, chest and a great half volley into the corner, isn't it, Lars? Daniels. King. Terrific run by King. Magnificent goal. Josh King makes the breakthrough for Bournemouth. Less than four minutes to the second half played. Everton's Huff and Puff has come to nothing. Demonstrating run by King. DeFoe and I played their part as well. A thumping finish and Bournemouth take the lead. You always felt it was going to be on the counterattack and Averintson have left themselves exposed at times. 2v2 at the back. It's a lovely ball, way to pass into Josh King. He's up, a phobie. Now King works in. Wow! Lovely manufactured goal from Josh King. It's 1-1. Well, he's redeemed himself. After that penalty kick, it about a bit of a night. But this is a well-taken goal. It's a bit scrappy, it's bouncing around in there, but nothing scrappy about that. Flicks over Fonser. Harry Wilson. Fraser. Now Smith. It's King. Time to bring it down. Josh King, but there'll be a big inquest in the Manchester United penalty area about how he had as much time as that. The United Old Boy, back to Houghton. And Bournemouth will take a half-side lead. Exactly that. I think Bournemouth did a good job of keeping Callum Wilson up the pitch and them a bit more of a target. And they were able to keep the United pending. How did Josh King have that much time? I thought the chance had gone.


TfNN, headline, news update. Down 91, Nazekoff 214, S&P's down 38, gold, gold contract down $15.70 trading at $17.72 an ounce. We have Silver down 40 cents, $21.88 an ounce, light sweet crude up 73 cents, $70.56 a barrel, notes and bonds. The 10-year, down 7 ticks, trading $130.20, the 30-year, up 10 at $162.05, and King Dolls up 259 ticks at $96.577, Euro 112, Yen 113.5 and the British Pound 132-1 at $1.00. We're going to take a look at the S&P, this is going to get interesting out here, I was shaking this out, because we do have the Fed tomorrow coming out with an announcement at 2 o'clock, you have a news conference at $2.30, the way this market is trading right now, so what we have, you get the spy down at $3.90 right now, and this is a doji, and what happens to these dojis when you get a doji down one day, it doesn't mean much, but what we have found is that sometimes that's just a halfway move down, and in this particular case, that's just what it might be, it might come down to the highs of the lows of last week, of a week and a half ago, it doesn't look to me like it's going to be much at this particular point, meaning tomorrow you get the announcement, yeah you might get lower price, but then you'll probably go right back top side on the short term basis I'm talking, you know, six, seven weeks, I think we're going to be down at $3.50 inside the queues, inside the spy, you're talking about $4.26, right now you're at $4.62. We're going to take a look at the NDX100 at the three queues, you're going to see the NDX100 out here, that right now is trading down, the queues are trading down at $5.38, you have some volume on the move on the way down, bottom line is that inside of the NDX, it's pretty amazing that Microsoft isn't the largest mover on the way down, you get Adobe, but man, Microsoft's down big too, so if we take a look at this, same type of setup, I mean you come down, you get Adobe happening, that's saying that we very well might come to the low end of $3.87 on the queues before you do another bounce, you know, but I suspect that's game to be had right now, that's the real bottom line, you know, we're coming into it, you've done 58 million shares, that's saying we're going to do about $9.68, maybe about $72.75, man coming into $105, but you got to remember something that it's closed the lows of the day, you open up, nothing's going to happen until 2 o'clock, might hit the end of that, the low end of that consolidation. Stay right there folks, come right back.


Hi everyone, I'm Ram Krishna Patnaik and I work as a software engineer at Red Hat Bangalore with the middleware team and I'm going to talk about this keyword in JavaScript. This is one of my favorite programming jokes. After all these years of working with JavaScript, I still get confused regarding what this points to. As JavaScript developers, we are placed with many tools and libraries that abstract out the confusing bits of JavaScript for us and let us build amazing things easily at scale. While we can keep building things without knowing how JavaScript works under the hood, knowing them will indeed help us in the development process and identifying occasional weird behaviors. And this keyword is something we actively ignore. So in this presentation, we are going to see some common behaviors of this. Here is the most common use case. The keyword this points to the object which is executing the method. It is also known as implicit binding. Now the question arises, what if the function is not associated with any object? Let's jump to the next slide. When we have a method defined as a standalone method, it's this refers to the Windows object by default. Hence, this is known as default binding. If we try to run the code from previous slide in strict mode, we will see that this isn't referring to the Windows object. It simply points to nothing and hence returns undefined. The examples before show how the implicit and default binding work. Now we are going to see how we can explicitly bind a method to a particular object. Unlike the previous two bind mechanisms, the explicit binding gives us control over what this points to. There are three methods for explicit binding. Call, Apply and Bind, the last of which we might have seen many times while working with React. Now let's go through them one by one. In the given example, we have made the this of introduce method point to a given object using call. The first argument to call is for the object it should be bound to and rest of arguments are parameters to the method invoked by call. Then comes the Apply method which is almost similar to call. The only difference is that the arguments are needed to be passed as an array. The bind method is a little bit different from call and apply. While others invoke the method, bind creates a new function bound to the specified method. And then we can call the newly created method with its signature. Until now, we have discussed about normal function definitions. Now let's talk about fat arrow functions which were shipped with ES6. Arrow functions do not have their own this. They inherit the one from the parent scope. The example above is a standalone method. So here this will be bound to windows object as expected. Let's get to the next slide to see how it differs from normal method definitions. We always hear that arrow functions can't or should not be used as object methods. The reason is they aren't bound to the object. They are bound to the parent scope. Executing the example above, we can see that the method grid doesn't get the name from person object. It instead gets name defined in global context, which in this case is the windows object. Here is another elaborate example to understand difference between normal and fat arrow functions better. The code snippets have object methods that aim to print the property name using inner functions. The inner function in left one is defined as normal method. Hence, it is bound to the windows object and method gets name property defined at global level. Whereas for right, the arrow function inherits this from parent scope, which in this case is the outer function was this points to the object person only. So we get the person's name as desired. I hope the presentations and examples help you understand the concept of this a bit better. Here are some of the articles you may find useful for learning more about this. You can reach out to me via mail or twitter for any feedback or query. Thank you.


The Chevrolet program starring Jack Benny with Frank Black and his orchestra. Frank Black opens the program with Charlie's Home. This week, throughout the United States, a series of big, colorful posters are growing up on the billboards. Reading, every minute someone buys a new Chevrolet. Watch for these new signs, my friends, and bear in mind when you see them, there's signs of better times. There's signs of bigger business for the world's largest builder of motor cars. Also, there's sure signs that the one best buy in the low price field must be Chevrolet. America certainly wouldn't buy Chevrolet at the astonishing rate of one every minute unless Chevrolet were the one best buy at its price. And that's exactly what it is. The only car in its field with a Fisher body. The only one with Fisher no-draft ventilation, with a cushion-balanced engine mounting, with a time-proved six-cylinder power plant, a starterator, an octane collector, and no other full-size car in the world is so economical on gas and oil and upkeep, or so dependable. In view of all these things, do you wonder why? Every minute someone buys a new Chevrolet. And now, Jack Benny. Hello, Samor. This is your New York correspondent, Jack Benny, the Earth Galliper, coming to you with all the late news reports with the courtesy of the weekly watch. The news that brings out all the dirt. Okay, Frank, let's go. Thank you. Uh, Chicago, Illinois. World Fair gets off to good start with many notables arriving daily to represent their respective countries. Sam Insel will represent Greece. Jimmy Walker will represent France. And Black's Orchestra will represent Russia. Scotland sends Harry Lauder, COD. Jack, Jack, another wire, just a minute. All right, what is it, Mary? Quick. World Fair, Chicago. Molly will be suggested to ride representing Pans for Rainier. Mary, go away, will you please? Bombay, India. Hmm, more Gandhi news. Mahatma Gandhi finishes 21 days fast and is now wearing a cigar band. When last seen, he was mistaken for a panatella. Babylon, Long Island. Man and wife discovered here with 16 children. Cork pound dead on soup. Overworked day, you know. Ah, special cable dispatch. Frank Buck and Jimmy Walker will sail for America shortly.  Let's go, Scotland. Harry Lauder also sailing for America. Local citizens getting big blowout by putting tack in his rear tire. Pretty good for Scotland. And now, folks, we have also added a want ad column to our paper as we cannot exist on circulation alone. So take down these addresses if you are interested. Traveling salesman wanted. Must be familiar with traveling, salesmanship, farmers and farmers' daughters. Address box 482, this paper. Wanted, 30 chorus girls. Apply Minsky Theater, New York. Wanted, three more chorus girls. Apply to Melton, Black and Benny. Got you in on this, Frank. For sale, baby grand piano by Lady with electric attachment. Girls wanted, to knit sweaters for Cats, Broomberg and Riley. Hmm, the boys must be cold. Woman 55 will trade a pick and ease dog and a canary for slightly used husbands. Realizes mistakes. Address RFD-4 Pump Handle, Ohio. Female health wanted, good secretary. If good looking, don't have to be so good. Jack, can I read one now? Go ahead, Mary. Wanted, good massive ceremony for Chevrolet program. Graham, wanted Howard Claney to say something about Chevrolet. Oh yes, you will find that Chevrolet saved you on oil, gas... Play, Frank, don't wait for this. Play, don't wait, don't wait, play, Frank. Mr. Black, thank you. That was My Darling from the Vanities, played by Frank Black and his orchestra. And now, ladies and gentlemen, we continue with our penthouse murder that was started last Friday. Do you all remember our terrible murder mystery last week? Well, it's terrible this week, too. Who killed Mr. X? You remember, folks, Mr. X was killed in his penthouse, so we could go tonight, between 8 o'clock and the bathroom. And the only clue found was a hot dog running away from a stand in Coney Island. You may also remember that during the trial, we were unable to place the guilt where it belonged. Garbo had to go home, Maywest had a date, and the other prisoners were not interested. So it still remains a horrible, unsolved mystery. Who killed Mr. X? I said, who killed Mr. X? Oh, pardon me. Yes. Watch those cues. Now, what could have been the motive for this crime? Let us analyze this. Mr. X was the landlord of three apartment houses, so you see he had no enemies. He lost every cent in the market. His wife was pressing him for back alimony, and he had incurable rheumatism, so there was no reason for suicide. Now, what was it? How old was he, Jack? 95. Then he did not die of old age. Neither will you, Mary. What did he have to suffer the night of the crime? Liver. Then it couldn't have been a heart attack. No, Mary, it couldn't. A pipe was pulled out of his mouth, and he was examined carefully. What kind of a pipe? A gas pipe. Oh, well. Oh, well, a little gas never hurt anyone. I know. Well, anyway, folks, we've had two detectives working on this case, Detective Melton. Detective Melton, you've been out on this case a week. Yes, sir. What have you found? I found a place where you can get a sandwich and a glass of beer for a nickel. Mary, take down the address, so that doesn't help solve the mystery. Detective Clainey, what did you find? I find that every minute of the day someone buys a Chevrolet. Well, now we're getting someplace. After all, that's what we're here for. Did you find anything else, Clainey? Yes, but the Chevrolet has sufficient no-drop ventilation. That's great. Now all we have to find out is who killed Mr. X. Jack, why not put it in the hands of Sherlock Holmes to understand crime? You're right, Mary.  Hey, Jack. Jack, wait a minute. Yes, Jimmy? I hate to interrupt your mystery, but do you mind if I sing my song now? Oh, no, pardon me, Jimmy. So, right ahead, what are you going to sing? Franz Leha's Frasier Serenade. I know that, Jimmy. I just couldn't pronounce it. You know, play frankly. In the silence of the night When the moon is shining one more world at last Is past destiny Every creature goes to rest In his cozy little night His very own sorrow There's a little nest of mine Of a starry, blue divine Watch a little home Was left Is a parent at a bar Waiting for the magic of We fight with you And through your love Every once and for a new world So close to be complete And slow, so calm Is everywhere The wall in the silence Of the night When the moon is shining bright Little man I shall never fret or pine For someday you will be mine To come through That was the Frasier Serenade, sung by James Meltz. And now, ladies and gentlemen, we will continue in our mystery and take you to the residence called Sherlock Holmes. Hmm, hmm, hmm. The quarter of seven. Only one more hour until a quarter of eight. And just an hour ago it was a quarter of six.  Mm-hmm, answer that, Mary. I'm not in. Hello? Hello? You want to speak to Sherlock Holmes? Yes, this is Sherlock's home, but Sherlock isn't home. He's working on a case right now. Yes, he's on a glass bottle. What is it, Mary? It's about that ten-house murder of Mr. X. They want you to stop working on it at once. Oh, yes, yes. Mm-hmm. I was expecting that case. Tell them I'll take it. Hello? Mr. Holmes just came in and said he'll take the case. Tell Mr. X not to worry. Goodbye. Mary, Mary, call in Dr. Boston. We have work ahead of us. Oh, Mr. Sherlock, I hate to ask you this, but can I draw five feelings today? That's elementary, Mary. I get it, Sherlock. Sherlock to you. Call, uh, call Dr. Boston. Dr. Boston, the boss wants you. Okay, I'm coming. No, Sherlock, but you. Boston? Boston, we have much work ahead of us. Mm-hmm. By the way, you've been eating herring. Is that right? Sure. But tell me, Sherlock, how did you know it? That's elementary, Boston. Besides, I can smell it.   You know, Boston, you're really supposed to be an Englishman. Uh, what am I saying? Mr. Holmes, I'll try, you know? Mm-hmm, I like the other dialect better. All right, what do you want? Boston, mm-hmm, you have a strange mystery to solve. Mr. X has killed Ms. Penthouse, and we start working on the case today.  You're always working. No, I just made some nice homemade soup. What kind of soup? I made some chicken, vegetable, and noodle. What do you want? Mm-hmm. We leave. We leave, Boston. We leave for the Empire State Building in ten minutes. The Empire State Building.  I've got a lot of thinking to do. Mm-hmm, mm-hmm. I must think. They last when he picked up his violin, but when he started to play, they screamed. Quiet, Mary. Quiet, I must think. I must think. Come, Boston, a thought just struck me. We must get to the Empire State Building in a jiffy. I am a jiffy, and my silver label gives us their justice, please. And much safer. At times, Boston, you feel signs of intelligence. You have just heard what these two famous detectives have said about the Chevrolet. It is quick, safe, and dependable. That's elementary, Cleaney, and get out of my study. Come, Boston, we must hurry. And by midnight, we will find the murderer of Mr. X. I like your own opinion. Boston, you're nuts. Come, let us away. Music You have just heard playing with the devil. And now we take you to the lobby of the Empire State Building where we meet Sherlock Holmes and Dr. Watson. Tell me, sir, like, why did we come here to the Empire State Building? What has this got to do with the murder of Mr. Hex? Watson, I'm surprised at you. While playing the violin, I made the following deduction. Mr. X was killed by some guerrilla here in New York. You follow me? A guerrilla was seen climbing up the Empire State Building with a girl in the palm of his hand and is at present on the tower. How do you know? I saw the picture. Now, if he could climb up a building the size of the Empire State, why couldn't he have climbed up that penthouse and killed Mr. X? You mean the guerrilla of King Kong? Of course, of course. Who else is covered with hair like that? Jobs, but not Shaw. Well, he didn't know it. Well, here's the elevator. What floor, Captain? We want to go to the tower. That's a hundred and second floor, boss. Yes, yes, yes, yes, I know that. When will we arrive? Sunday night, sir. You know, sir, like that elevator boy looks very suspicious and very familiar, too. I think so. What's your name, son? My name's Jim Milton, sir. Oh, sure, Jimmy. He's our tenor, boss. Hey, Jimmy, I hate to ask you this, but did you kill Mr. X? No, sir, I can't mind him killing my lady killer. Uh-huh, uh-huh. Uh-huh, uh-huh. Quick, boss, and the needle. How? And cut out those jokes. Well, we have two days in this elevator. Two days, hmm, hmm. I must keep my mind occupied. Hmm, hand me my saxophone. That was stormy weather. Brought fuel through the courtesy of the Chevrolet Motor Company. Hundred and second floor, all out. Hmm, hmm, Sunday got here quick. I'll be careful, boss, and very quiet. Very quiet. Please follow me around the edge of the roof. We must use our wits and track him.   You must have? That's elementary, boss. Come, come, follow me. What's that? The drummer just dropped the cymbal. Frank, keep the boys quiet, will you? Just a moment, boss, and don't move. It's so dark up here. Why didn't we come at the end of daytime? Quiet, quiet, go ahead, I'm right behind you. I'd, I'd sure not be behind you. Watch and look. Look carefully. Carefully, hmm, you see that figure standing down the doorway? Yes. Look, look, somebody is handing him some money. Oh, that's how it's made. Here, here, here. You know, he runs this building and he's collecting the rent. How low are you? Ah, you're... You're wrong again, wrong again, boss. What, what, what is that, Sherlock? Hmm, hmm, hmm, that's Tinkong. He's here all right. Keep down, Watson. You mustn't see us. Be careful, Sherlock. I think he sees us. Grab him, Watson, and don't let him get away. Thank you. Look, look, he's got a girl right in the palm of his hand. It looks like Mary Livingston. Wait, wait, it is Mary. Mary. Mary, what are you doing there with Tinkong? There's something in his eyes that makes me realize he got me in the palm of his hand. The girl of his friend. Mary, we must rescue. We must rescue Mary from that root. I'm not afraid of him. Hey, Tinkong! What's the idea of climbing buildings and carrying women with you? Well, it's rules of sport and I just love the fresh air. If that's Tinkong, I'll get him. Wait, wait, Watson. It may be a trick. Now, look here, Tom. You've been climbing buildings, dragging people out of their beds and murdering them. Did you climb up to the Penthouse and Park Avenue and kill Mr. X? No. You lie. You did murder Mr. X.  Well, I did have eggs for breakfast this morning. Then you admit that you killed him. No, no, no, no, no. Take him away. Take him away, Watson. Goodbye, Mary. I'm sorry, I can't play with you anymore. Goodbye, Paul and Harry.  Well, well, it didn't take us long to get him. He did it, Watson. Yeah. Yeah. Yeah. Yeah. Who's that? It's me, the voice of the shadow. What do you want? You think you've got the murder. Yeah. Yeah. Yeah. Yeah. Well, King Kong did not kill Mr. X. Then who did? Mr. X was killed by... Yeah. Yeah. Yeah. Ladies and gentlemen, this mystery will be continued next Friday night. But there's no mystery about the Chevrolet Motor Car. It's the best buy in America today in the nation's choice. Play Frank. We got the mother. They look so outplayed. Without your smiling face, my dear. My merry-go-round. They look so dusty, they're just... And no one can bring me back. Take us back where we belong. Whenever you see or hear the figures, 445 FOD factory, always think, my friends, of Chevrolet. Of the new Chevrolet, Standard 6. The car that made $445 famous. Of the smart fast-stepping Chevrolet that gave a new meaning to 445 by giving so many wonderful new features for that wonderful low price. A Fisher body. A big comfortable interior. Fisher no-draft ventilation. Safety plate windshield glass. An octane selector. A load of a road chassis that rides smoothly and steadily. And a six-cylinder valve and head engine that's not only one of the snappiest on the road, but listen to this. Some Chevrolet Standard 6 owners report gasoline mileage is as high as 26 miles to the gallon. And nearly all of them are getting between 18 and 24 depending on how they drive. So if you have a minimum of money to spend on a new car and want that money to do you the most good, to bring you the most fun and the greatest savings in return, save with a new Chevrolet Standard 6. The big general of his value that made $445 famous. Well folks, this concludes our program for tonight. We're here making the next Friday. Try and figure out for yourself who killed Mr. S. Mary, Mary hand me my violin. I must sing. Yes, ah, ah, ah, ah. Good night folks, good night. This is the National Broadcasting Company, W-E-O-S, New York.


So far, we've been working with the actual QTCP socket and with the raw HTTP protocol. That's not the most efficient way to do things. You don't want to reinvent the wheel, especially when Qt has gone ahead and made a Q network access manager class that does all of that for us. And it's extremely simple to work with. So this is actually superseded old classes like the QHTTP class. You may see in older tutorials and, well, I hate to say it as easy as this is to work with.  What does this really do? Well, it really encapsulates HTTP at its very core. You can get, you can post, you can delete, you can get the header, you can do all sorts of things. And, well, it's all working through signals and slots. So simple is about the only way I can put it. This is ridiculously simple to work with. We're just going to do a real bare bones example. Let's flip into our code. I've already got a bare bones Q object class. And we're including the network library. So let's go into the worker here. We're going to copy and paste some includes and go over them. Q object for obvious reasons, Qtabug for obvious reasons, Q network access manager. This does the heavy lifting. The network access manager works with what's called a Q network reply. This would be the response back from the server and a Q network request. This is the request you're making to the server. Q authenticator, that's for any username and passwords and Q network proxy just in case we want to work with a proxy server. Let's go ahead and make some slots. In the HTTP RFC, get is the means of downloading something. So whenever you get, you're actually getting it from the server. And post is a way you would actually put something to the server. That thing that you're putting to the server, it could be a file, it could be data, it could be pretty much anything. So we're going to send it a Q byte array and simply call it data. Now we're going to make some private slots and really we're just ripping these straight out of the documentation from Q network access manager. We're going to say authentication required, encrypted finish, et cetera, et cetera. I've already got these queued up. So I'm just going to copy this, save us a lot of typing. There we go. Ready read. Well, very, very self-explanatory. This is just simply when we know there's data from the socket. Authentication required. That is when, well, the actual remote server saying, hey, I don't really know who you are. You need to authenticate encrypted because we could be using an SSL socket finished. This is when the reply is actually finished. Remember there's a whole handshake that has to happen and the protocol itself may go back and forth between the client and the server several times. So let's go back here. Network accessible change. That's basically meaning whether or not the network is actually accessible. Remember that Qt runs just about everywhere so you don't know if, well, you're on a mobile device, if you're on an actual computer or laptop, pre-shared authentication key. This is basically the SSL handshake. This is the pre-shared authenticator, proxy authentication, pretty self-explanatory. This means we're talking to the proxy server and SSL errors is everybody's favorite. Whew, that is a lot. All right, let's go ahead and let's make a variable, let's call this manager. So really all we need to do now is, well, you got it. Create our signals and slots, connect them all up and fill out our implementation. And our actual constructor here, I'm going to just get a lot of this out of the way. All right, so we are connecting the Qnetwork access manager authentication to authentication encrypted, encrypted, network changed, pre-shared, proxy and SSL. Pretty simple, pretty easy to understand and wrap your head around. Yet, this is where we're going to actually make the connection and we're going to get something from a server. And we're going to say Qnetwork reply, and this is going to be a pointer. And notice how when we say manager, we get a whole slew of things we can do here.  In case you're wondering, we're just going to go over a very high level. Get downloads the resource. Put is a special way of putting something out there. Basically if you want to put some sort of file, that's where you would put it. Head gets just the head, but not the actual document. So let's say we're actually getting a four terabyte file. Well we don't want to grab the entire file. We just want to grab the information of the file, so we know how big it is. And then post post data out there. And then there's a whole slew of other things you can do. We're just simply going to get, and we're going to get a Qnetwork request. And this request is going to be a Q URL of the location. Seems pretty cumbersome and there's a lot of confusion what's going on there, but really all we're doing is we're saying Qnetwork access manager, go get something from the server. This is the location we want it and we have to give it in a special format. We have to tell it, hey, make a network request and we want to know the reply back from the server. But because we're getting a reply and this is all going to happen behind the scenes asynchronously, we want to connect up some signals and slots here. So we're going to connect the reply. We want the Qnetwork reply. We want the ready read and we want to connect that to this ready read. Notice how we are not doing a direct connection. We're just doing an auto connection and that's because it's smart enough in the background to know what we want it to do. One of the very few times I'll actually trust that. Post is literally almost the same thing. Let's go ahead and let's just grab this whole thing and we'll do a little bit of surgery on it in here. We're going to post a server and we're going to say we're going to make a network request and then we want to actually set that request here. And what we're going to do is we're going to set a header. If you're not familiar with the HTTP protocol, there's different headers that you can set. For example, the connection, the protocol, what sort of content you allow, things like that. We're going to do a Qnetwork request and we want to do a content type header and we're going to simply tell it, hey, we're going to send you just plain text. Probably a much easier way of doing that. So we're basically manipulating the raw header of that request using the Qnet request content type and we're going to set that to text plain. That's a mime type in case you've ever heard that before. Mime types basically tell the operating system what sort of data is in there. So text plain would be something you'd open up in a text editor. All right, now we've got our network reply. We're going to take that reply. We're going to say manager post and we're going to send it the request that we're creating here. However, we also need to send it the data. So we're just going to make a copy of that data and then we're going to connect up ReadyRead with ReadyRead. Pretty simple, pretty straightforward. So why do we have to do this? Why is this step even required? Well basically we need to tell the server what type of information we're sending. That way it knows what to do with it. Some servers, if you skip this step, it's just going to say I don't know what this blob of data is and it's just going to ignore it completely. All right, ReadyRead, this is basically going to say, hey, we've got some data back from the socket and we want to do something with it. Click the wrong button. There we go. So ReadyRead and let's go ahead and let's get the information back from this. So we're going to get the queue network reply and we need to cast the sender. So we're going to do a queue object cast. Remember sender is just a pointer to a queue object so you have to cast that, otherwise it's just going to not have any of the information that we really want. If we actually have a reply, then we're going to do something with it. In this case, we're just going to spit it out under the console and we're just going to read all bytes. There we go. Nice, simple, easy to work with. And then we're just going to fill some of this in. We may use this in future tutorials. Let's grab this network changed. I'm just going to flush this in real quick just so we can see what's going on under the hood in this class, get all these things wired up, make them look pretty, give us a good save, give it a build, make sure we didn't screw anything up. You see, we get a lot of these unused. So let's fix these up real quick. We're just going to simply say, queue unused. Very simple way of getting rid of those. Now I once got asked, why do we even worry about these warnings? Well, you kind of want to clean this up as much as you can because warnings can actually lead to errors. That's why they're called warnings. Most warnings, to be brutally honest with you, just really mean nothing. For example, is it going to crash for our program if we don't use this reply? No, 100% will not even matter. But someone somewhere out there is going to say, I downloaded the code and there was a bunch of warnings. So now we can give it a good build. There's zero warnings, zero errors, and everything's good to go there. Now that we've got this in place, we can go into our main. And let's just say, include at our worker, I'm going to say, got some notes, misspelled, of course, queue network access manager really encapsulates the HTTP protocol, includes SSL by default. So we don't have to do any real brain surgery here. Let's go ahead and say worker, we're going to get a cubite array and we're going to call this data. And we can actually do some pretty cool things with this. Let's say data, dot append, and we're just going to send it some parameters. So really what's going on here, and I'm going to actually just kind of, for the sake of argument, add this in here. What we're doing is we're just adding parameters. And this is just a simple way of posting something out onto a website. Parameter is a key value pair. So your key equals value, the ampersand really means, and another one. So if you've ever been in a conversation with someone who talks a lot, they're like, and another thing, and another thing. That's really what's going on there. So you can just chain these out pretty much almost infinitely, as long as the server will take the request, you're good. There is a hard limit, but it's actually pretty big. We're going to post this. And I'm going to copy and paste here, rather than even try to type that out. There we go. So we're going to post to postman-echo.com slash post, and we're just going to post the data right here. So really what this is going to do is it's just going to mirror it right back in. So there we go. So what the postman-echo website does is it just returns a JSON blob of the data you basically just sent it. So you can see all of the information pretty much right at your fingertips. There's our parameters, accept language, English, contact type, plain text, user agent. Notice how it is actually trying to mimic Mozilla 5. Pretty interesting. Forwarded port to 443, meaning it forwarded it to an SSL port for us, and there's the actual URL. We could have very easily done something like this. And let's just comment this out real quick. It does essentially the same thing. So the difference between get and post is actually pretty subtle. You got to really kind of deep dive, but you notice the URL. So get, you're actually getting a document, and you're trusting that the server is going to take this, and it's going to say, hey, here are the parameters, do something with it. Whereas post is something completely different, even though the differences are very, very subtle, where you're basically saying, hey, do something with that data, here's the data. Notice they're very distinctly different commands. But from a use case, they look pretty much identical. Let's just face it. Qt is extremely complex, and it has a massive learning curve. But once you learn it, you can do just about anything. Unfortunately, learning Qt is a challenge in itself. And if you've tried learning straight from the docs, you've probably become easily frustrated. While they do a really good job, they're arguably some of the best documentation in the world. They don't go that extra step and leave a lot of people guessing what to do. How do all these things interconnect? That's why I started developing videos. I've done videos not just on my own YouTube channel, which you're watching now, but also on the official Qt Studios channel. And I've started doing video courses out on udemy.com. Right now, I have the Qt Core series. It covers beginners, intermediate, advanced. So it'll take you straight from Hello World, all the way up to building a complex, multi-threaded, encrypted TCP server. On top of that, if you don't want any of this, you can still join the Voidrom's Facebook group, which has a pretty flourishing group of developers. And we discuss everything, not just Qt. I hope to see you there.


Hello, hi. Good afternoon everyone. As we draw this Kubernetes on edge day to a close, I want to extend a heartfelt thank you to each and every one of you of your vibrant participation and for the rich discussions that took place today. My name is Tina Jo. I'm the director in for ecosystem from ARM. Thank you for Sergio talking about the benefits of ARM. And I'm also the governing board chair of Elv Edge. I see Elv Edge was mentioned in several discussions and presentations. From the insightful keynotes to the deep dive technical discussions and sessions and the collaborative breakout discussions, we have witnessed the incredible energy and potential that Kubernetes and Edge computing hold for our industry. By the way, I also have a talk tomorrow Tuesday for the Kubernetes on Edge together with Google. So, the CNCF IoT Edge working group and Elv Edge have shown us the future is indeed at the edge, a future that is distributed, dynamic and diverse. Let's carry forward the spirit of the openness and collaboration and that defines the Kubernetes community as we continue to push the boundary of what's possible. And the CNCF IoT Edge working group joins twice a month, correct me if I'm wrong. And also you can see order GitHub information or here. And as we say goodbye, I encourage all of you to stay connected, join the CNCF IoT Edge working group and contribute to the ongoing projects and don't hesitate to reach out on Slack or GitHub. Remember the conversations that start here don't end here. They grow and evolve just like our technologies. And here is also the Elv Edge. Elv Edge has 12 projects underneath. This is an umbrella project. You feel free to join from our website. And there is a technical community. The technical advisory committee meetings is also twice a month. And we have a Slack channel and a video recording on the YouTube. So you can also go to GitHub and some projects use the Gary as well. So I would like to show some of the upcoming event. So this is, I think there's this in Paris. We want to meet you in Paris. So this is Kubernetes and the cloud native com next year. Until then, keep innovating, keep contributing, and most importantly, keep supporting each other. I would like to give a special thank you goes to our organizers. And this is the hard work of the event organizers and the program community and volunteers. Your dedication and effort make this event not only possible, but also a great success. A special thank you goes to our speakers and panelists who have shared their expertise and experiences. Your contributions have sparked not just conversations, but inspirations and lay down the groundwork for innovation and growth. I would also like to thank you, the program committee. These people have been here for several years, some of the new and it starts several months earlier with the very heavy review. We got a lot of submissions. It's overwhelming, but we can only give the spot to some of them and I hope you can contribute more and hope the program committees can volunteer again for the next event. I especially I want to thank you, our diamond sponsor, Spectre Cloud. Do you have a representative here? If you can stand out, we can give you a round of applause. Thank you. And to our platinum sponsor, Agnesis. He was sitting here. Yeah. And thank you for attending. Thank you once again for an incredible day and safe travels back home. And let's continue to make the edge or cornerstone of our cloud native journey. So I guess I will conclude for today. And I hope to see you at the reception today 5 30 to 7 p.m. Just at this location. All right. Thank you. See you next time.


Our next speaker is Anya Yarochevich. Her title, How the Psychology of Poverty affects behavior and financial outcomes. If you were tasked with getting people out of poverty, how would you do it? Historically, welfare policies and charities have examined poverty in a pretty one-dimensional way by looking at the amount of money people have and then giving them more of it. And this makes sense. After all, that's the definition of poverty, not having enough money. But is this the right way to think about poverty? A growing body of evidence suggests that, no, it may not be, because poverty isn't really just a lack of resources. It's a constellation of psychological states. It's feelings of helplessness, of fear, of uncertainty, of shame. And in this thesis, I argued that incorporating those psychological states into welfare policies can help individuals escape poverty more quickly and more definitively. Now, why would this be the case? Well, unfortunately, people in poverty have been found to exhibit behaviors that may exacerbate their poverty. For instance, they may be more impatient and they may be less willing to take risks. And while researchers have commonly assumed that this is the direct result of lacking money, in this thesis, I argue that it's actually the psychological states that drive those harmful behaviors, and in particular, helplessness, uncertainty, and shame. So what evidence do we have for this claim? Well, as is common in psychology, we start by taking a large group of people and we randomly assign them to different treatment groups, in this case, orthogonally manipulating poverty and the psychological state. So for instance, in one study, in which we're testing the effect of feeling helpless over your financial state, we start by either giving people enough resources to complete a task or purchase something, that's the wealthy group, or not, that's the poor group. At the same time, we can also manipulate whether they have the ability to get more resources, that's the agency group, or not. That's the helpless group. We then test the behavior of the people in each of these four groups, identifying how impatient they are and how willing they are to take risks. And what we're identifying in this study, as well as the ones for the other psychological states, is that it's not actually the lack of resources that's driving these harmful behaviors, it's those psychological states. So what does this mean for policy? Well, incorporating the powerful psychology of poverty can help individuals pick themselves up by their own bootstraps, helping us tackle poverty from the ground up. Thank you.


Black garlic is aged garlic, so it's regular garlic that we grow, but we age it under some specific conditions And that changes the appearance and the flavor and the texture of the garlic. It's going to be a super food I'm Mark Johnson, and I'm the co-founder of Snow River Black Garlic based in Jaramon Faroes, Gippsland Our property wasn't directly hit with the 2009 and 2020 fire event But we were affected by all the infrastructure issues that followed. We were shut down essentially for that period of time After the fire, we had some of our best months on record and then COVID rolled in and it was just like turning the tap off again A lot of people don't talk about it, but your mental health suffers. How do we navigate this process? What are we going to do about it? We were introduced to the business recovery advisory service and an advisor within that and he's like well This is what we can do. We can get you some assistance financially to help you move forward and we can start to roadmap a way out of this We knew that Snow River Black Garlic was a unique product and so the business recovery advisory service assisted Mark to find his marketplace We're in a really strong position. We know what's required to run the business But we've also got these connections that we can bounce on if we need them Our advisor is only a phone call away and I've had informal discussions rang him up and go Hey, I just need to chew the fat. You know, I'm just having a bit of a down day. You feel good about farming again The advisors have actually all been business owners. We're local. We're knowledgeable We're accessible and We listen to our clients That's just a great service. It's been pivotal in getting our business back on its feet. That's something that will be forever grateful for