Hello, everyone. I am Puneet. I run a digital agency. We work exclusively with WordPress and it's called Idea Box. We build WordPress products. We started as a services agency, but now we build a WordPress. Okay. Is it rollable now? This one is working actually. Okay. So, recently there have been a lot of talks about Gutenberg. Can I ask how many people here use Gutenberg already? Okay. How many of you are using it just for blogging or content writing? Okay. And how many do we use page builders here? That's quite a lot. Okay. So, there have been questions about how Gutenberg is going to impact page builders. Because a lot of people see it as a page builder in WordPress core. We are not sure how it's going to affect the market, whether we should stop using page builders now and start using Gutenberg. So, that's what I'm going to talk about. First thing, what is Gutenberg? If you go to WordPress.org slash Gutenberg, it says it's the new editor. This is something we have been looking forward to for the last few years, I think. The existing Visivig editor which we have been using is not actually true. What you see is what you get editor. It has been missing some functionality. We needed more flexibility and those kind of features where you can arrange layout. You can create media rich or customized blog post layouts, which was a bit difficult with existing editor. So, the new editor is trying to solve that problem. The good thing about new editor which I like is it's everything is in blocks. There are no short quotes. You don't want to worry about embeds. You don't have to worry about short quotes. You have to just learn one terminology that is blocks. So, I think for new users who are coming into WordPress ecosystem now, who will start writing content with Gutenberg, they will find it much easier because they won't have anything to compare with. For us who are using WordPress from a few years back, we might find it a bit frustrating initially that we have to learn the new thing and we have to go for a few more extra clicks. But in the long run, if we see it's more of a consistent system which is built around blocks. What are the features which I think I personally like about Gutenberg is, it lets me create content and layout for my blog post. More than pages, I like it using for blog post. If we go to a news website or a magazine layout blog post content, it was not possible or easy to do with the existing content editor. So, what we get here is as a content writer or a publisher, a distraction free writing experience like the full screen mode which existed earlier, it has become much better now. There's almost live preview. I would not say it's completely 100% true live preview because we are still working in the back end and what we publish might look different from what we are writing. But still you get a feel of how the content is going to be laid out and presented on the front end. Media rich content. If you have a blog post which has a lot of images, videos, blog quotes, pull quotes which we usually see on popular blogs like Mashable or TechCrunch or other technology blogs or personal blogs, it's difficult for us to create simply without using a third party plugin right now. But if we are using Gutenberg and a Gutenberg compatible theme, it will be much easier to create those kind of layouts. Another good thing is switching between blog types. So let's say you start writing content and you have created a paragraph block. You can easily switch it to a heading block anytime. So you don't have to rewrite the content which existed with the current editor, but there were a few users who might not be aware of this feature. Like you can easily switch between the blocks from paragraph to heading, heading to list or any kind of text block, similar blocks which can be switched between. If you take an example of image block, you can switch it to a gallery block, you can switch it to a cover block and you can switch a cover block back to image block. Creating layouts with a column-based layout is much easy now. So instead of writing custom HTML and CSS to create a three-column layout in your blog post or creating a table in your blog post or a page, it's much easier because you have the direct blogs you have a visual editor to work with instead of writing CSS or using a plugin for short quotes or something else. And simple page layouts. I think this is a great use for a lot of users who are building websites, hobby websites or just want simple page layouts. Creating a landing page which requires a heading, a few columns, a few images and call to action sections. Those can be done easily without having to install a third-party plugin. You won't need a page builder to do that now anymore. Good things about Gutenberg. Move forward for the WP visual editor because everyone needed something new, right? We have written a lot of content about WordPress. We have written a lot of content about how to write certain kind of blog post. We have written a lot of content about how to improve the content design or everything. But we wanted something new. So this is something new for WordPress community. You have a whole new range of questions to be answered. The most common question is how to disable Gutenberg. So everyone who is writing content around WordPress, they have a new topic to write about, they have a new topic to talk about, and you can educate your users. We can educate our WordPress developers about new things in Gutenberg. And it's making publishing easy in my opinion. It's making publishing easy in the long run. A new text tag. There are a lot of developers, WordPress developers right now. And it's difficult to differentiate between who is a developer, who is a beginner or who is an expert developer, who is an intermediate developer. And also we have been limited to the same technology stack like PHP, MySQL, a little bit of HTML, CSS, JavaScript for years. But now since we are using React, it opens up opportunities for a lot of developers from the React community or the JavaScript community to come in, bring in some more innovation, some more features, and even it's a good thing for us existing developers to start learning new technologies and work on new technologies and improve ourselves. Core functionality. I think this is one of the best parts because this is a part of the core. So it's going to stay for another few years. When Visvig was first introduced in 2005, I guess, we have come a long way till 2019 with the same editor, or 2018 with the same editor. So if we are looking for the long run, we have a new editor which we can rely on. If we are building some products around it, or if we are building some add-ons around it, or if we are building websites using it, it's going to be there for years. We are not limited to a particular set of plugins or features which are from a third-party developer. Bridging the gap for writers and website builders. It's still in the early stages, but a lot of content writers and website builders can use it to a certain extent. So there's no differentiation between what tools we need to use as a user or as a business owner. If we are looking for an average user who is using WordPress, they can use the WordPress Gutenberg to simply write blog posts. They can use the same thing to build their homepage, about page or contact us pages. Limitations with Gutenberg. What is currently missing and what can we expect in the future? But right now it's a bit frustrating. These limitations are holding us back from doing much more that we can do with Gutenberg. So it lacks true front-end visual editing. As I said, you are still working in the backend and the functionality and the styling relies on your theme. So even if you are adding a blog, it doesn't have its own styling properties. It has limited set of styling options. When you switch the theme, it might look different, which is not the case with page builders. Significantly fewer features. For example, if I am adding a section with three columns, there's no option for me to change the background color or adjust the padding and margins. So again, it's a limiting feature right now. It relies on theme styling. Once you switch the themes, as I mentioned, the layout will look a bit different. Although it might look different in your page Gutenberg editor, like you might pull out the image to the left or to the right, but it eventually relies on your theme, how your theme is going to style that particular blog. And it's a work in progress. So Gutenberg is currently divided into four phases. Phase one is already complete. Phase two is in works. Phase three and phase four are about to come in coming years. With phase two and phase three and phase four, the core team will be focusing on improving the experience for widgets. The widget pages customize their experience and make it seamless for everyone so that every part of WordPress is using blocks. And when this is complete, they will move on to other sections like header and footer. So eventually in the long run, the plan is to make it a complete page builder or a website builder and not just a content creator or a visual editor. So that was all about Gutenberg. Now the question comes, what is a page builder? How it's different from Gutenberg. Page builders have been in market for a couple of years or like five years or seven years. And it has completely changed the way we are building websites. The first one was probably Visual Composer, which is quite popular. Then came in new page builders like Elementor, Builder, Brizzy. There are a lot of page builders right now. So page builders introduced the concept of building websites completely on the front end without having to write any extra code. And this has changed a lot over the time, right from short codes which was used by earlier page builders. Now they don't rely anymore on short codes. They have their own HTML output, CSS output, JavaScript output. Everything is optimized for performance, which was missing in the earlier page builders. And the capabilities of page builder have gone beyond just the pages. Now you can even build header and footer with page builders. So if we are looking for a complete website building experience right now, page builders are doing a good job. You have a true front-end editing, visual editing. What you see is actually what you get with a page builder. When you are styling something, it has its own styling. The page builder retains the styling for you. There might be a little bit conflict with the theme, but the overall output is going to be almost similar to what you are building in the page builder interface. Build custom page layouts. You can build as many page layouts as you want with complete flexibility. And then you have options to build header and footer. Some advanced page builders will allow you to edit those parts of the websites as well. And then there are templates for archives. If you are building complex websites which need multiple kinds of archives or templates for various post types, custom post types, pages, these are the sections which you can target easily with page builders. Advantages of page builders. Why I would prefer using a page builder at the moment or why I have been using page builder for the last few years and why I am going to use page builders in the coming years. So it's built for website builders and business owners. So if you are building a lot of websites, it has all the options that you will need as a business owner and provide a complete website solution to your clients, which I won't be able to do with Gutenberg right now because of the limited options. Advanced layout and styling options, like I gave an example of row and columns, those options, margins and paddings are missing. In Gutenberg, those are very limited. But with my page builders, I can get more options, more of control for desktop devices, mobile devices, and medium screen devices, which again is missing from Gutenberg. Intuitive UI for building all kind of layouts. The UI for page builders has been simplified for one sole purpose of building websites. It's not targeted towards multiple user bases. It's just for people who are building websites, who are tech savvy, who are not beginners but intermediate level of WordPress users, who know their way around WordPress. So the UI is focused with that approach and it has been built to make your website development process easier rather than just focusing on content. While there are a lot of good things with page builders, there are certain challenges with page builders as well. We have a lot of options right now. It's just not limited. In core, you have only Gutenberg or the classic editor. You can switch between the two. But if you look out at the page builder market, there are several page builders. Elementor is there, Breezy is there, WP page builder is there, there is a page builder by site origin. So there are tens of page builders. And every page builder has their own learning curve. Some might call content block as a module, some might call it as a widget, or some might call it something different. So every page builder comes with its own limitations, its own learning curve and features, sets of features. So it's difficult for a new user to compare and figure out which page builder to go with. Shall we go with the one which provides the maximum options? Or shall we go with the one which is limited to the requirements which we need? It's difficult for beginners to add up to page builders because everyone has their own approach towards building the page layouts. Some page builders are trying to do advanced stuff, providing more options. Some page builders are trying to keep it lean and just focused on certain sets which are required for almost every user. So if a new user is just starting out with WordPress and we give them an option to start using page builders, they will be a little confused because these page builders are using advanced terminology like padding, margins, which a normal beginner user might not be aware of. Then there is a lock-in effect. If you are building with a page builder, you are going to continue with that page builder, using that page builder for your website in the future as well. For example, a page builder that relies on short codes and if you plan to switch it to some other page builder, you are going to be left with a lot of short code mess on your website. So you need to redo those websites because it's not a part of the core. But in case of Gutenberg, it's a part of the core. So as Gutenberg grows, you will have more and more functionality and features as a part of the core. Page builders versus Gutenberg. Now we come to the topic, we have talked about Gutenberg, we have talked about page builders, but how many of you here think that you will go with a page builder instead of Gutenberg? And how many of you will go with Gutenberg? Okay. So those who are going with Gutenberg, are you publishing mostly using it for publishing blog posts or using it for building websites as well? Blog posts. Anyone here who is doing websites with Gutenberg right now? I think there's no one. Okay. So that says, who is the winner here? Page builders. But yeah, I'm not going to declare a winner. It's about picking up the right tool for the right job. So let's talk about the similarities between page builders and Gutenberg. More or less, both the page builders and Gutenberg are using a similar approach towards building layouts. They have certain elements which can be added to the page, pre-built elements.  But the goal is to provide a way for users to use the existing functionality. So if I need an image, I just need to click on the image block and insert it to my page or blog post. And if I need a gallery, I can just insert a gallery block or gallery module or a visit, whatever it is. The same thing can go for a slider or a carousel. The same thing can go for related post or recent post. So the way everything existed in WordPress before was in forms of plugins and visits. Probably that is going to change into the form of blocks in coming time. Then we talk about the way we are creating custom layouts. Both Gutenberg and page builders allow you to create custom layouts. There are limitations with the functionality, but again, the goal is to create, allow users to create layouts without having to write code. So if we are using Gutenberg, we'll have limited set of features, but we'll still be able to create a decent layout and it can work well for a few users. But if your design is using advanced styling or colors or gradients or shadows, border areas or those kind of things, you need more control over designing, you'll be able to use page builder. Visual editing. Gutenberg provides visual editing. Page builders also provide visual editing, but there's a difference between the output. There's a sort of similarity again here. In the long run, we might see Gutenberg providing a 100% visual experience. But right now, page builders are doing that better than Gutenberg. What are the differences? We come back to the same thing. Layout and styling options are different. We have limited set of features with Gutenberg. It's not possible for me to easily drag and drop elements in Gutenberg. I have to navigate using the up and down arrows. And I get that flexibility with page builders. It's easy to drag and drop elements anywhere in the page and take control of every minutest detail of the design, be it for desktop devices or medium-scale devices or mobile devices. I can style every aspect of the website. I can't do that with Gutenberg. True visual editing, what you see is 100% what you get.   Just the base plugin, which is your page builder. It compiles your CSS. It compiles the JavaScript required for the page. It stores it and delivers it on the front end. So it's 100% user-friendly as well. You don't have to worry about something getting changed. Extensive design controls. If we are talking about creating a simple button in Gutenberg right now, you can create an outline button or a solid button, something like that. But what if you want to change the whole state or what if you want to add a shadow? What if you want to adjust the border radius? Or what if you want to change the padding, font size or width? Those kind of functionalities are not available with Gutenberg right now. And the target user is probably the main major differentiator here. Gutenberg is built for everyone. Page builders are not built with that focus. Gutenberg is going to be used by 34% of the websites which are using WordPress. Every website that is built with WordPress is going to be using Gutenberg. But the user base for page builders is limited to people who are building websites for others or people who are already aware of page builders. So it's not for everyone. So you get a better solution with page builders right now. Things to consider. When I'm picking a final tool for my next project or next website, what are the things I would like to consider? First thing is usability. Is this particular solution going to fit my requirements? Gutenberg alone can't do anything. But there are several add-ons which can extend Gutenberg to next level. You can get multiple blocks. You can get extra functionality. You can get extra options for your default editor. And if you are looking for more, if you need a better control, maybe you can look for a page builder. But since this is a part of core, it gives you an edge. It gives you a benefit that everyone is going to build around for Gutenberg and not just for any particular page builder. Then we have capabilities. If you are looking for a functionality where you want to edit the header and footer of your website or where you want to edit the custom post types layout, you won't be able to do that with Gutenberg. You need to use a page builder. But if you are looking for a website where you are going to write a lot of blog posts, let's say you have a blog, you have a magazine, and you want to create a unique layout for every blog post that you are writing, then you are going to use Gutenberg for that. And you can't use page builders on single post post layouts. It's difficult to use page builders just for single posts. That's why they are called page builders and not post builders. Extensibility. As I said, currently we have WordPress core and we have everything built as plugins and themes. So if you want to extend a functionality for WordPress, let's say at a content form, you currently have a plugin. But in future, this can be just a standalone blog. If you want to extend a functionality for WordPress by adding a carousel, currently we are using a plugin. But in future, this can be a blog. So there are plans for a blog directory for Gutenberg. So we will see a new phase of development and a new set of features which will be available for the core editor. And just similar to WordPress plugins, we will be able to extend Gutenberg with its own blogs and functionalities. So that is one thing which is really amazing because it gives you a number of options and pick up the right tools the way we are doing right now. We are picking up the tools which we need to extend WordPress. And the same way, in future, we will be able to do that with picking up the right tools for Gutenberg and extending and installing what we need and using what we need, not just using all of the options, just actually what we need. In case of page builders, if we talk about it, a page builder is built by a few developers, a team or a particular business. So there are limitations like not everyone is going to build around those page builders, a particular set of team, a particular set of developers or designers are going to decide the path forward for their product and maybe a few developers who are going to build their business around them and extend their functionality for page builder. But with Gutenberg, it's more of a community project. So the feedback which we receive from community, the requirements which come up from community will be entertained and we can look forward to a brighter future with Gutenberg and more options and more functionality in the coming time. So the last question is, can page builders coexist with Gutenberg? How many of you think it can happen? Absolutely, I agree with that. So I'm going to use page builders for building websites and for creating blog posts, I'm going to use Gutenberg right now. That's my plan right now. But in future, again, as I said, Gutenberg is built for masses. It's for 34% of the websites on the Internet. So everyone is going to use it. I believe the core is going to be lean and focused around usability for everyone. It should be as simple as using WordPress. So Gutenberg is going to follow that philosophy and stick with the functionality and options that they are going to offer for everyone, not just become a blotted plugin or a complicated plugin, which is not similar to a page builder. But a lot of other developers will be able to extend it and take it to another level. So I think page builders and Gutenberg can coexist in the coming years. So that's all from my end. If you have any questions, I'll be happy to answer. And you can connect with me on Twitter. Any recommendations on the best page builder? I think that's tricky to answer and answering from a WordCamp stage. It will be a bit more difficult. Currently, if we see there are two page builders going on in the market competing. One is Beow Builder and another one is Elementor. Elementor offers a lot of functionality which is available for free. Beow Builder is focused mostly around the pro version, all the functionality you get is in the pro version. And they are targeting, I think, mostly business owners and agencies. I've used both the page builders. We build products for both the page builders as well. And it's eventually about picking up the right tool for your job. If you think you just need a certain amount of features, stable functionality, not frequent updates, I would go with Beow Builder. If you think you are doing more of complex designs and advanced functionality where you need pop-ups and other things, I would go with Elementor. Both the products are doing really well right now. Hi, I'm already coming in. So you talked about, like, you did a versus thing, Beow Builder. Honestly, I would like to know your view about, like, officially, Gutenberg is not even a year old. Yeah, that's correct.  Right. So what do you think? There is a huge gap, as you said, how narrow the gap would get in the next three years. And how do you think, how close it will get? And I'm pretty much, Sam would like to have more questions on that because he did a Gutenberg thing today and I just want to know how narrow that gap would get and what are your views on, like, three years down the line? As I said, Gutenberg, there are two things. Gutenberg, first, it's built for masses. Like, it's for everyone who is using WordPress. And second thing, it's community-driven. So the gap can be narrowed down, not by the core team, but by the community. The way we are extending WordPress with plugins, the same way community will come around, developers will come around, designers will come up with their ideas and try to bring in as much functionality as possible to Gutenberg. So it will be a community-driven path for Gutenberg and for base builders, it's like a business-driven path. It can be as close to as a page builder in future or a complete website builder in future. But again, the core is, I believe the core is going to remain lean and easy to use for everyone. So if you are looking for a solution which is a complete solution, you will again rely on some third-party developers to complete it or you can just pick up a complete solution which already exists in the market and use it in the long run. My question is the same and from what you just said, my bet would be in three years, you would be up to 75%, just 25%, do you agree on that, that it would be there? It could be there because as I said, the long-term goal for Gutenberg team is to make it a complete website builder, like to have a team which can just request calls to different blocks. They can be a block for header or they can be a set of blocks for header and then they can be a set of blocks for content and then they can be a set of blocks for footer. So these are the theme parts which are going to be built with Gutenberg and then the team just renders those blocks and displays them on the front end. So it can be there, it can be there. But for me, the major differentiator is always the user base. Then again, my idea box makes an add-on for the viewer builder. Viewer builder, yes. Could you see that maybe because Gutenberg allows also people to make add-ons to it, right? Right. So maybe some of the business now just speculating that the page builder could actually move over to something like your company where because you are already covering several page builders. Yeah. So maybe you could be able to make something that would say good for close-up to where the page builders are today. Right. Yeah, because it can be a community-driven project, like maybe a particular business or a group of individuals can extend Gutenberg because it's open source, it's the code base is available to everyone. There are a lot of options that we can add to Gutenberg. We have tried several things on our own as well in our team and we were able to add similar options as page builders. There are certain challenges with compiling the CSS, displaying the output, but those can be overcome. So there are quite few, there are quite some chances that a lot of developers will shift from page builders towards Gutenberg and we can already see a few of them doing that. But this is also quite possible that page builders might eventually come up with something which can let them switch between page builders and Gutenberg. So maybe if you are adding a module, you can convert it to a block or convert a block into a module or use a template inside a block. Those are the opportunities as well. Yeah, right. Thank you. Kind of half answered my question. Following on from those two, we've touched on the future of Gutenberg. Do you have any opinion on where you see page builders actually going? Because they're five years ahead so I would hope that in three years we're going to be three years ahead of where Gutenberg is now. So as well. So page builders started with just page building experience and now they are into theme parts, header footers, everything like almost everything, be it custom post types or archives and with page builders like Elementor they are introducing more and more advanced functionality like animations and popup builders, contact forms. So there are certain page builders who are trying to be a complete website building solution like Elementor itself. Then there's Beaver Builder. So in long term Gutenberg can be a website builder because eventually we are going to compete with users who are trying to move to Squarespace or Wix. So we are trying to build a solution which is good for everyone and we can bring in those users back to WordPress and not let them go to Wix or Squarespace. So with the plugin, with the release of full site editing plugin so Gutenberg has already taken a really large step in that direction of becoming a website builder. So if you look at the past like eight, nine months not only has it become increasingly stable it's now actually allowing users to have a great defined template for contact pages, for product pages, about pages, service pages and you can just add those templates and essentially your site is designed. So I guess my question is with Gutenberg itself like you said it's been built for the many. So it'll service again 80, 90% of that maybe 34% that's out there with those websites and then you'll have a niche market of course always for paid builders I think because of the animations and those things that you mentioned. So given that full site editing has already released it's already launched and it's available do you really think it'll take three years for Gutenberg to catch up? I mean I see that happening much sooner and I just feel that in the last eight months a lot of progress has been made and at Automatic we are testing the full site editing plugin with users already on our platform which is in several million so I think when we see that the result it's had we're really optimistic about it and I know it's a controversial topic but do you see it taking three years or do you see that there's going to be a much quicker uptake as more people get to use the full site editing plugin? Projecting like a complete timeline would be difficult but yeah as you said it's been going at a fast pace especially after it has been pushed into WordPress core so there's been a lot of development there's been a lot of improvements so there can be a set of features which will cater a lot of users in the coming years like the full site editing plugin again it will take everyone in the community to level up with Gutenberg it's not just the plugin itself or the editor itself we need to have Gutenberg compatible themes as well so in future all the developers will have to come together to extend Gutenberg and it will take a while and while things are stabilizing for Gutenberg a few developers are also skeptical about is it the right time to build for it because there are certain challenges if we build it right now what if it changes they asked Matt this at WordCamp Europe and he gave a really good response he said that Gutenberg is going to be the future of WordPress for the next 10 years so if you're a theme developer you're a plugin developer absolutely start developing for it because the next 10 years WordPress will be all about this editing experience absolutely like as I said the last visibility was introduced in 2005 it has lasted for 14 years almost 14 years people are still using it so this is at least going to be there for 10 years we can start building it but I'm not 100% sure if it will be a complete website building experience in less than a year 2 years or 3 years because the way the level which page builders have reached or attained over the last 5 years or 6 years Gutenberg is trying to come up with those features now and plus it has to focus on the usability for everyone like their accessibility limitations which page builders won't probably have to worry about yeah thank you okay thank you alright that's all that's my time thank you very much


Presenting What Makes a Hero on the Cavalcade of America, sponsored by E.I. Dupont-Tunamurzen Company of Wilmington, Delaware, maker of better things for better living through chemistry. Before we begin our play, here's a happy suggestion for making your home bright and cheery. It's about Dupont's Speed Easy, the wonderfully smooth and velvety wall finish that makes almost any wall surface like new again. Speed Easy is ideal for use over wallpaper. You'll like it because it's speedy, it dries in an hour, then your room can be used again. It's easy because all you do is thin it with water and apply freely with a large brush or roller. One coat is all you usually need. Remember, just ask for Dupont's Speed Easy wall finish. Speed Easy. Its name tells the story. And now for our play. This evening, in a radio play written by Russell Hughes and Bernard Feins, the Cavalcade of America tells the true story of an American infantryman who today wears the Congressional Medal of Honor, the British Military Medal, and the Soviet Order of the Patriotic War Second Class. His name Corporal Jim Slayton is home Gulfport, Mississippi. The Dupont Company presents What Makes a Hero with Richard Whitmark as Jim Slayton and Statscotsworth as William Tanner on the Cavalcade of America. My name is William Tanner. I'm a war correspondent. Maybe you remember reading this line some time ago. Corporal James Slayton, United States Infantry, was today awarded the Congressional Medal of Honor for extraordinary heroism in battle. Well, a lot of our GIs rate that line. Later I filed this. Corporal James Slayton, United States Infantry, was awarded the British Military Medal in the Soviet Order of the Patriotic War Second Class. Naturally I wondered about Corporal Slayton, what he looked like, where he came from, how he talked and acted. Then other things happened, happened fast enough to make me forget about Jim Slayton. I didn't remember him again until I received a letter from home from one of you. That letter asked a question. What makes a hero? I thought about that. I wondered what happens inside a man to make him a hero. I wanted to write a piece about it so I looked up Corporal Slayton. When I found him, maybe I was surprised because most of us have an idea of what a hero looks like. I know I had. But Jim Slayton, well, here's his story. Sixth Betrayer, huh? That's right, Mr. Okay. Here you are. Say, you're pretty small to be hacking, aren't you? Something wrong, Mr. Wrong? No, no. I was just wondering what you'd look like driving a truck. Meaning I'm little, huh? Oh, no offense. I'm no giant myself. No, guess you ain't. But don't you worry none about hurting my feelings, Mr. Ever since I was knee-high to a duck, people been kidding me about my size.  But I can get mad. Yeah, I guess you could all right. But you've got to be careful who you're getting mad at, huh? That's right, Mr. Right now, I ain't mad at nobody. Well, that was Jim Slayton back in 1941. He was married, had four kids. He was good natured, mad at nobody. Then one sunny Mississippi day, Sunday, December 7th, it was. Jim sat in his cab. He had his radio on. He was dozing for the music. Howdy, Jim. Oh, howdy, huh? Nice day, ain't it? Yep. Business flow, huh? Yep. Nice music, huh? Pretty fair.  Something's on my mind. Having trouble? No, not yet. But sure as today's Sunday, something's going to happen. What are you talking about? Gone at my face was burning again.  Ah, Jim, what could happen on a nice day like this? I don't care, Art. When my face starts burning, something's bound to happen, always does. Burn the day I ran into that truck. Burned the time one of my kids got measles. Ah, Jim, you're standing still so you can't run into a truck. The kids ain't going to get measles again. Jim, that means we're going to be in it.  We ain't only in it, I'm going to be the first guy in line. Hi, Jim. I want to sell my heat, Mr. Kennedy. Oh, going out of business? Didn't you hear the radio just now? Didn't you hear what those jabs done? Sure, son, sure. I heard. What do you offer me? A bunch of a market for used taxes these days, Jim. Well, I'll just leave this heat with you, Mr. Kennedy. I'll trust you to get the best price you can. What's your big hurry, boy? I'm going into this year war, first thing in the morning. Well, this war ain't but an hour old. You got four kids. They'll call you when they need you. No, sir, I'm mad clean through, Mr. Kennedy. I'm going to do something about it right now.  What those jabs done there at Pearl Harbor will take me a long time to get over being mad. We got to make it so Pearl Harbor sticks in their car and choke him. Now, simmer down, son. You get your chance. That's what I'm aiming for. Hey, do you know where Pearl Harbor's at? Well, I guess I don't, rightly. But where it is, I'm going to get there to hurry. Well, that was Jim Slayton. Up to and including Sunday, December 7th, 1941.  In fact, a man five feet four weighing 100 pounds doesn't give anybody the idea that he is hero material. But let's go on with the story just as I heard it. It was the following day, December 8th, that Jim Slayton showed up at a recruiting station. All right, all right. Breaking up. Now, keep in line.  Hey, hey, hey. Where are you going? You talking to me, sir? You guessed it, shorty. Look at that. Please don't give me no trouble, sir. I come in here to enlist. I had my place in line and stepped out for just a second to toss out a cigarette. OK, but stay where you are and keep your clothes with you, shorty. Why? You'll find out. All right, now keep it moving. Right through this door. Name? Jane Slayton. Age? 28. OK, here's... Holy mackerel. Where's your mask, son? Oh, now look here, corporal. Just give me that paper and let me go. OK. Straight ahead. And don't fall through the cracks on the floor. Five feet, four and a quarter. Four and a quarter. Weight? 100 even. 100 even. Thank you, sir. Where do I go now? Uh... What's your occupation, Slayton? Taxi driver, sir. Then I suggest that you go back to it. A solar taxi, doctor. I'm sorry, Slayton, but you're under the minimum weight. We can't accept you. But I'm as big as those jabs any day. I'm sorry, but the minimum weight is 105 pounds. You are five pounds under it. You mean you're going to turn a man down for five pounds? That's it, Slayton. But, sir, only five pounds? I'm sorry, but that's it. All right, next man, on the scale. But, sir, then five pounds won't make no difference in a man's fighting weight. I'm going to get a gun, ain't I? That'll make up for the five pounds, won't it? Now look here, son. The army has rules and regulations. One of them is a man can't get in if he's under the minimum weight. You couldn't stand the gap. It's tough. Now move along. Yes. Next man, 162 and a half. 162 and a half. Now you guys wait here. Well, how'd you make out, kid? Just like you said, Sarge. How much you miss it by? Five pounds. Five, huh? Yep. That's tough. Say, look here, Sarge. Hmm? Is there any one of them rules and regulations that says a man can't give it another wheel? Not at all, kid. Not at all. Okay. I'm going to get them five pounds. Well, son, you can try. It looks to me like you're just about as big as you're going to get. Maybe you didn't stay out in the rain enough when you was a kid. Rain? What are you talking about? Forget it. I was just ribbing you. Now you go home and forget about it, kid, because, well, that's the way it is. Five pounds under the minimum weight. Five big pounds that looked at Jim Slayton as hard to get as five million dollars. But he went at it. In a couple of weeks, he added two pounds with three to go. Eight a lot of things he'd never liked before, kept on eating them until he had one more pound to put on. That one was the toughest. It had to be picked up ounce by ounce. But one day, Jim Slayton put himself on the scales. They tipped over at 105 and a half. And Jim hurried himself down to the recruiting station before he lost those precious ounces. The army took him in. And he went to basic training. Are you making it, soldier? Me? Slowly, slowly. You've got any idea how much all this stuff weighs? About 60 pounds. What's the matter? Having trouble with it? It does seem like the last ten miles give me the heart. Here, give me a rifle. I'll tow it for you. No, buddy. I'll do it myself. Did I tell you something? They sure ought to make these helmets out of cardboard. This one's pushing my head clean on down to my ankles.  You're marching at attention! Okay, slow boy. Stick with it, Slayton. Only ten miles more. I sure do. I sure do. Okay, Sergeant. So, Jim Slayton went through basic training. It was tough, hard, grueling. Now, maybe by this time you and I have some idea what it takes to be a hero. Or have we? Training is one thing to stick out. Battles another. The one takes guts to keep from blowing your top at things you think are GI nonsense. The other? Well, let's keep on with the story of Jim Slayton. One day, Jim Slayton, United States infantry, height, five feet four, weight, military secret, found himself overseas. What am I doing here? Is Pearl Harbor over here? Is there any Japs here? That's who I come out to fight. Well, maybe they didn't want to scare the Japs too much, Slayton. Why don't you stop giving me the needle, Sergeant? Not for the world, Slayton.   Save it for tomorrow. We're moving up. Moving up? You mean we're going to get a chance to do something? It's just about that. Oh. What's the matter, kid? Deciding not to be a hero after all? Who ever said I wanted to be a hero? Well, you said you were mad, didn't you? Sure, but I was mad at Japs. Yeah? So were a lot of us, kid.  I'm older than you. I'm 28. I got four kids of my own at home. You're not even married.  I'm just driven. Now, you better grab some sleep because we're going out early and I don't want to have to carry you tomorrow. Good night. Good night, Sergeant. And listen. Yeah? Do me a favor. How's about laying off the cracks about my size? Huh? Okay. It's a promise. And you lay off worrying about the Japs. Why, sir? Because we're going to have plenty of Heinies to worry about. The outfit moved out. Infantry. Foot soldiers. The guys who pound through the mud and dust. The guys who take a piece of ground and hold on to it. And Jim Slayton was with them. Corporal Slayton now. He may have been little, but he had a heart and somebody saw it and put a couple of strikes on his sleeve. Jim had his tastes of battle. And it was bitter. Just as bitter as it is for a boy from St. Paul or Omaha or Cincinnati or Casper, Wyoming. And the hero stuff? Well, who thinks about that when the goings hot and tough? Jim didn't. Not even when his outfit was holed up in a farmhouse outside a town. A town that had to be taken. Ah, this is a great thing this is.  Seems to me it's better being a gopher and still breathing than popping our heads out and stopping breathing. Maybe you're right, Slayton.  You ain't got much to hide. Now take Larkin over there. Six feet for 250 pounds a guy. That's a lot of stuff to hide in a fox hole without having some of it sticking out. There's that sniper again. Yeah, and every slug he sends over gets closer. If we could only get one look at that cookie we'd get more to him out. Six of us, he's got already. Sergeant Collins. Yes, sir. Take his men as volunteers. Scout that hill up ahead. Yes, sir. Sergeant. Yes, Captain. Yes, that's the sniper. Yes, sir. All right, you guys. You heard the old man. Who wants to go to a surprise party? I'll try. Me. Better than playing ground squirrel for the whole war. Help me in. I'll go, sir. Rick and I'd like to come along for the walk, sir. Ah, now look, Slayton. I'm a volunteer. I'm one. You are listening to What Makes a Hero with Richard Widmark as Jim Slayton and Scott Cotsworth as William Tanner on the Cavalcade of America sponsored by E.I. DuPont in the Moorsen Company of Wilmington, Delaware. Maker of better things for better living through chemistry. This evening's Cavalcade is the story of a man with fighting spirit. All the more remarkable because of his stature for pint-sized Jim Slayton stood at five feet four and a quarter in his stocking feet and tipped the scales at an even hundred pounds soaking wet. But Jim was a fighter and he finally succeeded in joining the army as an infantryman and was sent overseas. As our Cavalcade play continues Slayton has volunteered for a detail that has been ordered to wipe out a German sniper's nest. Calling to this scrub is no good. Can't see what's up that hill. That sniper must be someplace up there. Nope. That Heinie's got himself covered like a two dollar bet. Hey, Sarge, wait a minute. Is he something, Slayton? No. It's just a trouble, Sarge. But I feel something. Well, then what's the idea holding us up? Come on. Please hold it, Sarge. I'll cut it out, will you? This is bad enough. No, look, Sarge, maybe then Heinie's are waiting for a chance like this. I just know there's more than one.  A sniper up there, Slayton. Get it? A sniper. There are nine of us. Sure, but I'm telling you, I'll feed something. All right. What are you cooking up, Slayton? What's this gag? And it better not be a gag. Well, I can't tell you exactly what I mean, Sarge. All I know is my face is getting hot. And when it does that, something's going to happen. Look, Slayton, I don't know what you're trying to cook up, but you're not going to snaffle this detail with that wacky stuff we got ordered, see? I know it, Sarge, but just listen to me for a minute, will you? All right. What do you got? Look, there's nine of us. We'd be easy pickings if there's more than one crowd up there. Now, one guy could get through and take himself a look, see around. And I ain't big. I ain't got so much to hide, Sarge. You said so yourself. Let me take a look around, huh? I tell you, something bad is up there. I know it. My face always burns when there's something bad. I think you mean it. I sure do. How about it? Okay. But if you're not back here in 10 minutes, we're coming on. Okay. Now, you see that ridge up there? Yeah. I'll make for that, but I'll keep the cover.  Okay, Slayton, that's a deal. So long. Good luck. Hey, try to keep an eye on him, you guys. That's going to be tough. He ain't big in the first place. In the second place, he can hide under a leaf. Well, maybe he'll get through. Yeah. Maybe. What time you got, Williams? Well, it's 10 minutes up, if that's what you mean, Sarge. Yeah. That's what I mean. Well, I guess it's goodbye, Slayton. Okay, you guys. Let's split up in two sections and let's get that sniper. Let's stay down and hug... Holy cow. That's no sniper. There's a machine gun down. Keep down. Hug the ground. The little guy was right. There was trouble up there. Yeah, and he's got it right in his lap. Hey, that was a rifle. Slayton. Where the devil is he? Hey, there's another machine gun there. Over there on the left. Two of them.  Hug the ground, you guys. That first machine gun stopped. I think Slayton got it. Take it easy, take it easy. Those stinkers are pulling another trick. Just wait a while. What do you think about Sarge? Slayton. You know, he was a nice guy. Yeah. Yeah, I'm gonna miss him. Yeah, maybe I shouldn't have ridden him so much. Took a lot of guts to go out like he did. That lousy sniper. See where that shot came from? No, can't see a thing. Hey, that's Slayton quiet. The fake. One of those American speaking honeys. Hey, Sarge, can't we no more hide behind those bushes? That is Slayton. Hey, you all right? Holy cow, look at this. Two of them. One got it right through the eyes, and this guy bayoneted clean through... Hey, fellas, four guys in this other machine gun nest, each one filled clean through the noggin. Boy, in 200 yards. That's what I call shooting. Okay, Slayton, what really happened? Yeah, I know. I don't rightly know. They must have been surprised to see me, I reckon. I jumped in with my bayonet and got one. I think I held the other one down with my foot. Shot him after I got my bayonet away from the first one. Yeah, but how about the second machine gun nest? Well, when I caught sight of that second nest, I figured something had to be done. This mound here hid me from the crouts up there. They had to stick their heads up to see what was happening where I was when they did a shot. You know, I just got to thinking about something. What's that, Jim? About my face burning. That ain't starting again, is it? No. But I just remembered I used my last bullet when I knocked off that last hanging. And my face never warned me. That's the story of Corporal Jim Slayton. I thought about it while I was writing it. I thought about the question one of you wrote me, what makes a hero? That bothered me. It bothered me so much that I had to go back to Jim Slayton and ask him some more questions. Well, Mr. Tanner, I don't rightly know why, did it? Unless maybe I figured it was me or them. But that doesn't answer it, Jim. It doesn't answer the question of why you went up there in the first place. No, no, I guess you don't. Maybe I was mad. At what? Well, at first I was mad at the Japs, Pearl Harbor. Then when they stuck me to fighting Heinies, I guess I got mad at them. Well, that's part of it. Isn't there anything else? Well, you know, Mr. Tanner, like I said, at first I was mad at the Japs. Then when I got over here, I got mad at the Heinies. And then, then I guess I just got mad at things. Things? What do you mean? Things like, uh, well, things like what I wouldn't want to happen to my kids. Yeah, I guess that's it. Yes, that's all, Mr. Tanner. I guess that's all, Mr. Tanner. A guy who got mad at things, things he didn't want to happen to his kids. Maybe the question, what makes a hero, can't be a hero, can't be a hero, can't be a hero, can't make a hero, can't be answered any better than that. Thank you, Richard Whitmark. That's Cotsworth and members of the Cattlecade cast. Now, here is Ted Pearson speaking for the DuPont Company to tell you how to transform old no longer used furniture into gay, bright, useful pieces with your own personality for the finishing touch. There were over a million and a half marriages in the United States last year, and since it takes two to make a marriage, well, that means we have more than three million newlyweds. These days, of course, most of the men are in uniform. You see, young couples holding hands and trains and buses riding bravely off into their future. When couples set up housekeeping these days, finding furniture is a problem, more often than not, they have to buy old furniture and modernize it. And newly married couples are finding, as thousands of other people have found, that refinishing old furniture can be fun. Let's do largely to a man and a name. The man is Peter Hunt of Cape Cod who makes the business of remodeling old furniture, redecorating it in colorful, simple designs with DuPont Duco finish. The name is Transformagic, Peter Hunt's method of transforming old no longer used pieces into gay, bright, useful furniture with your own personality for the finishing touch. You can take an old bureau and change it into a sparkling chest of drawers gay with little red hearts and scrolls. A worn out kitchen table with the legs shortened and a few simple color strokes becomes a low table for the nursery. A school debt bought for a dollar or so second hand becomes a convenient holder for books, magazines and dad's pipes or mother's sewing. An over ornamented picture frame rejuvenated with Duco in a pastel tint becomes a shadow box wall cabinet with convenient shelves for knickknacks. Easy, not only is it easy but it's fun. The peasants who created the cottage furniture of Europe like the farmers who made so much of our own early American furniture weren't artists. You don't have to be an artist either. Peter Hunt has reduced his designs to a few simple strokes of the brush and DuPont has prepared a 64 page booklet called Transformagic, a gay adventure and restyling old furniture. Illustrated in full color crammed with detailed instructions what to do about the old finish how to apply new finish coats how to antique all the things you've always wanted to know about refinishing furniture. Your nearest Duco dealer will give you Peter Hunt's booklet free of charge or you may obtain a copy by sending 10 cents in coin or stamps the radio section DuPont Company Wilmington 98 Delaware. Duco Finish is one of the DuPont companies better things for better living through chemistry. Next Monday evening, Cavalcade presents The Doctor Gets the Answer a story of vital interest and encouragement to every American concerned with the well-being of our fighting men. Our story told for the first time on the air is the factual account of a young flyer suffering from mental shock as the result of his battle experiences. The Doctor Gets the Answer tells how this flyer has returned to the newly developed rehabilitation program instituted in the hospitals of our army air forces. The orchestra musical score was under the direction of Donald Voorhees this is Roland Winters sending best wishes from Cavalcade sponsor E.I. DuPont de Nemours & Company of Wilmington, Delaware. The Cavalcade of America came to you from New York is the national broadcasting company


Welcome back! It is time to announce the winner of the 2019 spring 100 frame animation challenge. Strange Power was the topic and it was strange and it got us strange submissions but by strange I mean fantastic and awesome. So all the votes came in so there were a couple of them that had multiple votes and these are the clips. And in last week's submission clip I forgot to include one so at this point I want to showcase that one as well. But ultimately there can be only one. Yep there can only be one and the winner is... Congratulations Peter! It was a fantastic clip. Everything came together really awesomely. The animation, the camera work, the surprise, just the connection to the theme. I thought everything was really really cool but again there were a lot of really good submissions. It's always a huge huge pleasure to see what people are coming out with. And we're going to do another one in fall of course. It's always twice a year spring and fall so tune in for the next one November, December. December is the next one but thanks again for everybody who submitted. Thanks again for everybody who participated and congratulations Peter and we will be in contact in terms of your price. And for those that are watching this for the first time the winner gets either $100 through PayPal or something that I can send them through Amazon and I'm adding something new which the previous winner actually preferred to choose. So instead of money he preferred to take that equivalent of $100 and go for animation critiques. So if you win you get three submissions for anything you want to send me that you want feedback on. There you go. Animation Challenge Spring 2019 is over. We will see each other again in December, December 2019. Thank you.


Now, what we're going to do really quick is we're going to go to the market. All right. So what I'm going to do is I'm going to bring up an execution system here. So I want to show you exactly, you know, we're going to go from point Z before we go to point A.  Hold on a second. I'm going to bring this up really quick over here. Now what you see right here, fellow traders, is just give you a second here. We have a couple of stocks that I'm moving this morning that did pretty well. VT, by the way, anyone see the stock right now? There's VTYX this morning. They have any catch on to it to see the stock trade this morning? Just let me know. Just look at something here. No one saw the stock. Nobody traded the stock VTYX. Really? OK. Well, have you ever seen a stock go up and it went from three dollars right at the pre-market and shot up to seven? Now you're probably asking yourself, how did that stock go from three to seven? Now, some of you have been trading here for a long time, and I'm going to ask you. You tell me, why would that happen? What would drive a stock to go up literally almost 100% in less than 30 minutes? Does anybody have an answer? Give me a yes or no. Bill, you don't know. Mike, you don't know. John, you know. OK. Phil says news. Andrew doesn't know. Sameer knows. What is it? What drive this thing go up? What made it go up? All right. Now, if you can't answer this question, I'm going to tell you something very important, you should quit trading. And please don't take this a bad way. But there's a very big failure rate in trading.  And so but the answer is, which I hope everybody could agree with me, it's buying and selling. That's it. Supply and demand. That's the only reason. Yes, there are probably news, Albert, and everything else. But regardless of the news, sometimes you're like, is that really good news? You know, like, is it really? I thought it was bad news. And it's like, wait a minute, was it that great of a news that made the stock go up that much? Well, the only person that it matters to is the people on the street. OK, the market makers, the algorithms, the high frequency trades, all those. And now what you're looking over here is orders. Now, let me just get my crayons on here so you can follow along right here. There you go. So you can see my little pointer here. All right. So you could see right here that this stock, if I drew a trend line, you'll notice that you got big support levels here. You got resistance levels here, you know, all the way up there. And wherever it may be. And what really you need to focus on. I'm going to get my crayons out here, too. OK, there you go. Is this you got to focus on this? Twenty two thousand shares, eleven thousand shares, fifteen thousand shares. You need to look at these big, big, big block orders. OK, because that's what makes what we call support and resistance levels. Now, obviously you could see where there was big resistance levels here, but you're like, OK, why was the resistance levels at six? Well, you could see that you got eight thousand share sellers, 27 orders out there. These are what make support and resistance levels, buying and selling. I'll do one more. All right. By the way, anyone want me to look at any stock out there? Anyone out there want me to look at a stock? Tesla, OK, I look at that one because people, that's like a very popular stock. Let's look at Tesla. All right. And I'm going to bring up Tesla up over here. So you could see Tesla, right? Had a pretty big resistance levels here today, just right below two hundred. Right. Does everybody see that? Big, big stock popped this morning, went to two hundred and then came back down. Now, I can't really see the orders here. Let me change this to a little bit lower. So I'm going to go 90 and if you notice right around two hundred, you see the last person on the bottom of the totem pole. There's fifty six thousand shares are going to be sold. There is one thousand two hundred and thirty five orders out there. Now, there are sellers, thousand shares, twelve thousand, fifteen thousand. There are sellers everywhere. And when you're looking at fellow traders on the left hand side, this is a seat on the exchange. You're seeing every single buyer and every single seller out there. Now, let's think about it. How much smarter and better trading decisions if you're able to see all these buyers and sellers out there? Would that be great? And how about this? How about I introduce you to something of level four? How about if you were able to see the reason why that big two hundred share seller was not really fifty six thousand. But maybe it was somebody under New York Stock Exchange, CBOE, whatever it is. There was over one hundred and eleven to one hundred and seventeen thousand shares out there, two hundred and he's been out there since nine thirty this morning. Now, let's ask yourself this question, fellow traders. How many of you here are in a position and see those one hundred and seventy thousand share sellers and buyers out there? How much smarter and better trading decisions would you have made if you were able to see those orders out there?  And the leaders are the people who are trading the most amount of shares. And that's what we're about to learn from a cyber group member today. Just click the link below and receive all these amazing products and a world of knowledge for just nine dollars. Do it today.


My name is Rafał Wesocki. I work at Intel in the system software engineering division and I work mostly on the mainline Linux kernel and mostly on the power management support in it and ACPI support code in it. Today, I will be talking about suspend to idle, which is the power management feature in the Linux kernel. But before getting into details, let me give a short introduction to this topic to get everyone on the same page. So, suspend to idle is a variant of system suspend, which is a feature by which the system can be put into a low power state as a whole. And in that low power state it doesn't do anything except for basic maintenance like battery monitoring and temperature monitoring. And so the state is referred to as a system sleep state because it is kind of analogous to animal sleep in which the body is not, does not appear to do anything. And whatever it does is regarded as basic maintenance. So, why is it needed? Why is it there in the Linux kernel? So, there are use cases for that. Obviously, that's the reason. And actually, there are more use cases than just the two listed here in the slide, but these two are canonical use cases for system suspend. The first one is a laptop in a bag case. When the user puts laptop into a bag, closes the laptop lead and puts the laptop into a bag, and then the laptop is not expected to do anything except for the basic maintenance. And that's why this is a use case for system suspend. Another use case is when the user goes away from the computer keyboard, walks away from it, and after a certain time, the system may decide to suspend itself with the assumption that it is not going to be used for some time going forward, or it only needs to do basic maintenance. So, again, this is a canonical use case for system suspend. As I said, there are other use cases, but the two above or in the slide are just enough to have it for having it in the kernel. So, that's why we have system suspend. Now, a bit of terminology. So, as I said before, the system state after suspend is referred to as a sleep state. And in contrast to that, the system state in which the system is operating and processing data and doing everything the user needs is referred to as the working state of the system. So, you have two states, the working state and a sleep state, and a suspend transition which takes the system from the working state to a sleep state, and a resume transition which takes the system in the opposite direction from the sleep state to the working state. The suspend transition is triggered by user space through a special control interface. I will be talking about it a bit later. And the resume transition is triggered by a so-called wake-up event when one of the devices in the system signals they need to wake it up from sleep state. And these are the cold flows for system suspend in Linux. One of them is referred to as platform-based suspend and the other is the suspend to idle I will be focusing on in the rest of my talk. So, the platform-based suspend has been there for like several years. It's been introduced around or was introduced around 2004 and was stabilized around 2009 and then it has not been changing a lot since then. And suspend to idle is newer, it was introduced in 2013 and it evolved quite a bit since its introduction. I will be talking about that. So, if you look at those cold flows, you will notice that there are similarities between them and there are differences. So, the first steps of the suspend transition, the three first steps in both cases are the same and also the three last steps of the resume transition are the same in both cases. So, when the system is asked to suspend itself by user space or the kernel is asked to suspend the system by user space, I should say, it first calls notifiers in order to notify all the interested subsystems about the upcoming transition. Then tasks are frozen, which means that every user space task gets a signal and that causes it to enter a function in which it doesn't participate in any mutual exclusion and waits for a notice to leave that function. So, it's looping in a function until a corresponding towing of tasks happens during the system resume. Kernel threads may or may not participate in that it is on an obtained basis for them. The next step is suspending devices, which is carried out in four phases. I'm not going to go into much details about what those phases do in particular. There are four of them in which phase all the devices can be accessed, can be touched and that the phases happen each after another in the order given in the slide. So, during the system resume, there also are four phases of resuming devices, which are analogous, each of them is analogous to one of the suspend phases. And after resuming devices, the tasks are thought so they can continue running and then all the interested subsystems are notified about the completion of the resume transition. So, in the platform based suspend case, there are more actions carried out in addition to the ones I was talking about, but they are not carried out in the suspend to idle case. So, generally speaking, the platform based suspend after suspending devices, it prepares the system to call the platform firmware to complete the suspend transition. So, the last step is calling the platform firmware, the platform online step, offline step, sorry. And then the platform firmware takes over and does something to turn the power off and finalize the transition. And also, in that case, the platform firmware handles the wake up signaling. So, suspend to idle is kind of a simplification of that, which is based on the observation that the last steps of platform based suspend are not actually necessary on contemporary systems. So, they may be skipped and instead of that, the CPUs can go into idle states and wait in those states for a wake up event. In that case, all of the wake up events have to be handled by the kernel, by the operating system. So, as I said before, suspend to idle is kind of a simplification of platform based suspend and that's the reason why it was introduced and the slide summarizes the most important properties of it. So, first of all, it is a system suspend variant. It is expected to draw less power than runtime idle or active idle, which is, so runtime is a combination of energy efficiency features which are available in the working state of the system. So, if the system is suspended, it should draw less power than any combination of power management features in the working state. That is theoretically, suspend to idle is more lightweight than the platform based suspend, which is kind of obvious because it does less or takes less steps in order to suspend the system. It relies on the CPU idle infrastructure. So, if the CPU idle time management infrastructure is not available, suspend to idle is not actually supported. And it should be available on all platforms that have the CPU idle time management infrastructure in contrast to platform based suspend which requires specific support on the platform side. Here's a control interface to control system suspend. So, there are two main files in SysFest for that. One is SysPowerState, in which can be used by user space to trigger a transition into a sleep state. Actually, mem is the string to write to this file to trigger system suspend and it can be either platform based or suspend to idle depending on what is supported by the given system. The one in this slide, the example system from which those files were taken, supported both suspend to idle and the platform based suspend, which is referred to as deep in this interface. So, the SysPower mem underscore sleep file can be used to choose the variant of suspend that will be triggered by writing mem to SysPowerState. In the example in the slide, this is suspend to idle by writing deep to mem underscore sleep, the square brackets removed to deep and then the platform based suspend will be triggered by writing mem to SysPowerState. In addition to those two files, there are multiple files in SysFest for controlling wake up. So, every device that can wake up the system from sleep or from the sleep state entered through system suspend has a power slash wake up file, which can be written to with one of the enabled or disabled strings and if it is enabled, then the device is expected to wake up the system from sleep state in particular from the suspend to idle sleep state and if disabled is written to this file for this particular device, then the device is not expected to wake the system up. Okay, so this is how it works and how to control it, but it is instructive to have a look at how it evolves. So, in order to kind of recall how we got here, how we got what we have currently in the kernel and I'm going to focus on that in the rest of my talk. So, first of all, suspend to idle was introduced in Linux 3.13 in 2014. So actually it appeared in 3.14, it was introduced earlier in the development cycle of this kernel. So, but this is the first release in which it was present. And that that was very similar to what we have right now in Linux, except that it was much simpler than the current implementation. And I would even call it oversimplified. The idea at that time was very, very simple, it was that, yeah, the system suspend infrastructure, which was introduced for system-wide suspend or system platform-based suspend, sorry, which was introduced for platform-based suspend, was actually considered to be sufficient for suspend to idle as it was without any modifications. And the idea was that, oh, we can just, instead of taking non-boot CPUs offline and so on, we can just kick all the CPUs into the idle loop, and then make the suspend task, carrying out system suspend, to simply go to sleep and wait for a certain situation or certain thing to happen. And that thing was that it waited for a specific data to be written into a specific location in memory. And obviously, this had to be done by somebody, and the idea was that it would be done by an interrupt handler. So, when there was a wake-up interrupt, a handler would run, and that handler would write into a location of memory monitored by the suspend task. And then the task, the suspend task, we'll see the write, and then it will wake up and then it will carry out the resume of the system. Well, that was straightforward enough, except that it didn't work as expected. And the reason why it didn't work as accepted is related to how interrupts are handled during system suspend and resume in Linux. And that is, so in order to explain that, I need to say that there are two levels of interrupt handlers in Linux. There are so-called low-level handlers, which take care of the action specific to the interrupt controller in the system. So, for every interrupt controller, there is a low-level handler. Or you can think that for every interrupt controller, there is a low-level handler, which is called every time this interrupt controller signals an interrupt, and that handles the controller itself. On top of that, there are device-level handlers, which are referred to as action handlers, and device drivers can register those action handlers, and there may be multiple action handlers per interrupt line or IRQ. And they all are invoked when the interrupt happens or triggers on that IRQ after the low-level handler has handled the controller. And the problem is that the action handlers were expected to wake up the system from or kick the suspend task to trigger a system resume while the system was suspended to idle, but action handlers actually don't run while the system is suspended as a rule. During system resume, there is an operation referred to as IRQ suspend, which prevents action handlers from running between the suspend late phase of system suspend and resume early phase of system resume. So the orange and gray area in the slide is when the action handlers don't run. So actually they cannot wake up the system or they cannot kick the suspend task to carry out the system resume. So in order to address this problem, the low-level handlers, the low-level interrupt handlers had to be modified, and the modification was done for actually for all of them at the same time. And what was done, there are two flags or two new flags were added. One of them IRQD underscore wake up underscore set is used to notify the IRQ subsystem that this IRQ for which it is set is expected to wake up the system from suspend. And there is another flag called IRQD underscore wake up underscore armed, which is set by the IRQ subsystem during system suspend if the other flag was set earlier for the given IRQ. And if the armed flag is set and the IRQ triggers during while the system is suspended to idle or in this gray box that was showing in the previous slides, the IRQ subsystem will automatically trigger the suspend task to carry out the system resume. So this is automatic. This is done in such a way that it doesn't, it is not noticeable in the, the handling of this is not noticeable in the working state of the system. And it works quite well and the actual handlers don't actually need to worry about system resume anymore. All right, this change was made in Linux 319 in 2015, along with several other improvements listed in those in those blue balloons in the slide. So the analyze suspend tool was introduced, which allows people to, to profile system suspend and find out which devices take, take how much time is taken by, by individual devices to suspend during system suspend and so on. So if you can get a profile system with respect to system suspend and resume. There was another interesting feature that was added during that time is direct complete which allows some devices that were already suspended in the working state of the system to stay suspended over system suspend and resume. And of course, there was this wake up interrupts handling rework that I was talking about and, and suspended idle started to ask for the deepest idle state of CPUs after, after devices have been suspended. And also device callbacks in all of the phases are now asynchronously calls, so which means that they can be in each phase, they can be called in parallel with each other, as long as there are no direct dependencies between the devices. In question. Okay, so improvements were made. But that was not enough or not all yet, because there are timers. And some of the timers are periodic. And the way the periodic timer works usually is that the timer function programs the timer itself to trigger again after a while, and so on. So that periodic timers program, periodic timer programs itself to trigger again. The problem is that timers, the timer interrupts are actually are actually handlers for timer interrupts, I should say, are actually allowed to run during the late suspended early resume of the system, or the Noir Q phases, and also while the system is suspended to idle. If there is a periodic timer, it or if there was a periodic timer, it would cause the system to cause at least one CPU in the system to wake up, see what's going on. Obviously, this was a timer so it was not a wake up in a wake up interrupt for the whole system right. And so the CPU would go to idle again, and this was going in a loop, while the system was suspended to idle. Obviously, it prevented the system from or the CPU, the CPU blocking the system from, from saving energy, or at least from saving as much energy as it could save or could have saved. So that needed to be dealt with. And the way to deal with it is to add the ability to suspend timekeeping to the suspended idle code. Kind of straightforward because that the the suspended idle code knows which CPU is going into the into an idle state. As the last one, right. So if this is the last CPU going idle during suspended idle, it will trigger suspended suspend of timekeeping. And the suspend of timekeeping causes basically prevents any timer from being used going forward. So it is, it is sufficient to suspend the timekeeping in order to get rid of the timer problem entirely. If the suspend going idle, if the CPU going idle, sorry, at the moment is not the last one, it only has to stop the scheduler take on itself. And after or during wake up the first CPU waking up will resume the timekeeping and the next CPUs going out of idle will start the local scheduler tick on themselves. And the rest of the processing is, is as it was before. So the suspend of timekeeping allows us to avoid the timer issue. So this is the last one in the in the news for four in 2016. In addition to that, in the same kernel, the that there was a new framework for for managing IRQs dedicated for system wake up. So on some systems are there are dedicated for waking up the system from from sleep states, and they are not used for anything else. And, and the kernel got a new framework for managing those, those IRQs. Okay, and this is the time when, when it looks like that everything was done. And, and the feature was complete. So it was sort of like in the in the human development when the when the kid goes to a university. And he or she thinks that he knows everything and now, you know, can can do by by herself or himself. But, but it turns out that there are challenges and, and, and they need to be faced and they are like part of the adulthood life, adult life. So that happened to suspend to idle as well. So in 2017 to changes were made in Linux for 10 which improved the feature. So first of all, system suspend generally started to support device links device links are featured that allows device dependencies to be taken into account during suspend and resume more precisely than it was possible before. And that allowed, allowed developers to fix many problems related to device to device interactions during suspend and resume of the system. And interface to the control interface I was talking about was was changed to get its final shape as it is today. So the interface that I was talking about was actually introduced at that time in Linux for 10. And then it turned out that that there are problems. And the problems were related to, to the way that system wake up events were handled by embedded controllers in some PC laptop computers. So, the embedded controller is a small processor running in the, are located in the system, which executes a program to control system features like battery fans, thermal monitoring and similar things. Usually, the embedded controller doesn't have any business to be to signal anything to the main CPU during system sleep, it should, it should just take care of the basic maintenance by itself without, without interrupting the main processor. However, in some systems, embedded controller is also responsible for handling system wake up events, such as the power button press. So if the power button is pressed, it, the signal from it goes to the embedded controller. And then the embedded controller is responsible for signalling the main CPU about that through the special IRQ associated with ACPI which is referred to as ACPI SCI or system control interrupt. And SCI is a, is a multiplex interrupt which is used for many different reasons that are made trigger for, for many different reasons like the wake up signalling from PCI devices or wake up signalling from, from non PCI devices and so on. The ECGPE signal, signal shown in the slide is a, is a, is a signal line from the embedded controller to the ACPI SCI multiplexer that, that causes the SCI to be triggered. And usually, if, if the embedded controller was not responsible for handling system wake up events, that ECGPE line can just be disabled while the system is sleeping or suspended to idle. And so the embedded controller would never trigger SCI in the states. Unfortunately, if the system wake up events are, are to be handled by the embedded controller, that cannot be done. Which means that all of the activities of the embedded controller would now cause the SCI to trigger during system sleep and that would interrupt the main CPU. And then it is necessary to, to distinguish the wake up events coming from the embedded controller, from non wake up events coming from the embedded controller, like, you know, battery status change or thermal, some thermal events that, that it may want to notify the CPU about or something. And that is not easy. So there was an attempt in, in, in Linux 4.15 to handle that by, by looking. So obviously, you know, in order to distinguish between wake up and non wake up events from the embedded controller, the embedded controller needs to be looked at. And then the events need to be processed and then, and then it turns out if they are wake up events or they are not wake up events. So the attempt in Linux 4.15 was to do that after partially resuming devices. So between the noir, curism phase and the resume early phase during system resume. Because the idea was to do that after allowing the action handlers for, for interrupt lines to, to be, to, to run again. So that if there is an interrupt trigger during the EC processing, then it would be handled as usual and then there wouldn't be problems with processing of events. Unfortunately, it turned out that this, this, this didn't work because device drivers were confused by this additional loop between the noir, curism and noir, irq suspend of devices and some of them didn't work correctly because of that. So that needs to, that needed to be reverted or rather, or rather changed. So that the whole flow looks like the initial one. Actually, there is only, there is no additional loop in this, in this flow. All of the processing of wake up events happens in this gray box at the bottom. And, but, but today it doesn't only include wake, wake up interest processing, but also things like embedded controller events processing. So if there is a wake up interrupt, and it turns out to be ACPI, SCI, then the SCI interrupt handler is run in line or in band in the context of the suspend task, which is handling all the suspend and resume of the system. And that SCI interrupt handling covers the embedded controller processing. So if, if an SCI triggers the embedded controller is looked at and the events coming from it are processed and they are, and they are handled as appropriate depending on whether or not they are, they are system wake up events. Most of them are not system wake up events, but if there is a system wake up events, event coming from the EC, it will trigger the suspend task to resume the system. Okay, so this is a whole story basically, and it illustrates very, very nicely in my opinion that the virtuous cycle of the kernel development, which is that if you change the code in order to implement a feature or, or improve it. People will start to use it and then experiment and test it. And then there will be problems. The problems will be reported and that, and that obviously needs to be investigated. So the tools are developed and diagnostic features are added, and then it allows developers to understand the issues better. And then that's in turn allows them to write better code and make code changes and the circle closes this way, right? So this is like the, or the cycle closes, I should say. So, so this is what happened in this case in, in, in, in a few, actually a few times, right in a row. So some changes were causing people to try them to try try the new, the new code, and then they found out that it didn't work as expected and then reported problems and that caused the new the problems to be analyzed and understood and new code was written and it happened at least three or four times in the development of suspended idle. So it's a good illustration of how the kernel development at large works in my opinion. All right, so that is basically all I had to say. But let me mention two things. So first of all, I have references to presentations that in that space are related to power management and to system suspend and resume in particular. So even before, mostly during Linux Foundation conferences. So in the reference part of my slide doctor is there are a few references that should, the links should actually be active so you can use them to see what I had to say about this. It's mostly is the links are mostly to my presentations, one of them is to the presentation from land Brown. So that there are more details in those in those presentations and so you're going to come to try them and see what what they are about. So I have to show this slide. That's climbers like required by Intel. All right, so that's it. And if you have any questions or comments on concerns. Please let me know.


Silver nanoparticles have been shown to be effective against various types of pathogens such as bacteria, fungi, and viruses. They can also be used to prevent the spread of infectious diseases by blocking the entry of pathogenic agents into host cells. Silver nanoparticles are able to interact with the outer membranes of lipid-enveloped viruses, thereby preventing them from entering their hosts. These interactions have been observed with HIF-1, which suggests that silver nanoparticles could be used to prevent the spread of this virus. This article was authored by Ixtapontorrent Liliana, Gazetrovino Ilsa N, Lara Umberto H, and others.


This study found that lyriglotide, a type of drug called a glucagon like peptide 1, GLP1, receptor agonist, may be effective in reducing binge eating episodes in adults with obesity. The study also showed that lyriglotide resulted in clinically meaningful weight loss. However, there was no statistically significant difference between the lyriglotide and placebo groups in terms of binge eating remission rates. This article was authored by Kelly C. Allison, Ariana M. Chow, Maya B. Bruzoss, and others.


Over the last 11 weeks, we've seen 41,000 people in five African countries. We've trained over 500 teachers to deliver engaging science with simple items, and I think most importantly, we trained over 160 local Africans. A big part of Science Circus Africa is really kind of planning a seed so that African countries can carry this on. So we train locals, we donate them equipment, PA systems, whole exhibitions so that they can keep running the circus when we're gone. One of the really special things was seeing how the science got interpreted in an African context, so when we wrote the shows and the exhibits, you'd always think, alright, how can we make this relevant to Africa? But of course, when you get over there, you'd find all this stuff you never would have thought was out there. For example, we're doing sound experiments with the little straw trumpet. You cut the straw, it makes a little trumpet noise, and as we're doing it, this kid comes up and he's got this bit of, you know, cut up kind of bamboo reed with a plastic bag on the end and we're like, what? And then he starts playing it. So, you know, he's using the same concepts that we're teaching, but really interpreted in an African way. The great thing about this program is, you know, we totally smashed the kind of numbers that we thought we'd saw, outcomes much bigger than what we thought, so it's got a chance to really hit a number of development goals if you think about things like health, sanitation, they're all underpinned by science, and so that makes science education a really critical thing, particularly in these countries where the formal science education is not in good shape, and if you look at informal science education, it's basically non-existent, so we're really trying to help them get that going.


What's going on ladies and gentlemen welcome back to day number three where we're going to be taking you through a phase three workout All concentrating on tricks Very similar to what we did yesterday. We're gonna do a minute of each trick We're doing 10 of those you rest 30 seconds in between and you repeat this a total Sorry one more time so you complete it a total of two times This is a month three or phase three weeks nine through 12 However, you want to call it of our newest jump rope workout program Which was basically created by you guys and giving us feedback on all the different workouts that we already have on this channel So we put together workouts based off of your feedback. They're all new and this workout specifically today Is gonna help you incorporate tricks in your workouts so you can have more fun jump more rope get leaner and live an epic life All right, ladies and gentlemen to start things off. We're doing a warm-up just like yesterday's workout We're gonna do 20 jumping jacks 10 air squats Then we have 10 front lunges five on each leg followed by 10 push-ups Don't rush through this guys. Just make sure to warm up properly and if you need to do an extra round That is totally cool as well You know dance a little bit. It's okay to dance and get warmed up All right, ladies and gentlemen to start things off. We're going jump rope run in place jump rope run in place So I'm gonna just get warmed up here And what I want you guys to focus on is again the form just being the elbows jutting out to the sides of your hips Everything looks the same as it does for regular bounce running in place. It's not that much different of a movement My wrists and forms are controlling everything and keeping that rope nice and tight. Come on Zendu nation do the thing Also guys if you want to get access to these three months of workouts This is just one of the workouts from phase three of our new jump rope workout program. You can click the link below And check that out Good ladies and gentlemen be sure to go as fast and as intense as you can while still being able to Maintain a good jump rope rhythm You want to be able to the whole idea behind doing tricks is that you want to be able to increase your speed increase your ability to Do transitions so that you can look like an awesome jump rope ninja while at the same time losing body body fat The great thing about Jumping rope is that it's a skill that you can constantly improve and have a lot of fun with while at the same time producing an extremely high calorie burn and Allowing your body to maintain its lean muscle mass So I say this a lot but think about the jump rope body as like the zen dude physique or do that physique is Like a soccer player like a muscular lean soccer player or an NFL wide receiver for guys or You know a shooting guard that type of fast athletic body is what we're shooting for here It's a new fitness and jump ropes a big part of that The biggest part of it obviously Next guys jump rope double unders jump rope double unders now notice here on the double unders I'm not going like every I'm not just doing double unders for a minute I mean God bless you if you can do that but with this rope it is a little bit difficult And again, we want to maintain our form So what I'm doing is three double unders and then three to five skips just regular. Okay, maybe more like five to ten And then following that up with three double unders Good next up ladies and gentlemen got the jump rope fast skip jump rope fast skip this one now all these Moves guys just recognize that we have tutorials on all of these So if you don't know how to do some of these moves, that's totally fine Just go to our tutorials playlist and you can learn them for free All right guys the fast skip by the way is just you're bouncing on one foot twice And the other foot is kicking back and kicking forward So while you do the one-two hop on your one foot You're just kicking back and kicking forward with the other one before switching it. That's the best way I can describe this move. All right ladies and gentlemen simple simple simple boxer skip here Just alternating the weight of our feet going from right to left and shifting that weight while both feet are technically tapping the ground at the same time This is a move that you just want to get down to again look like a jump rope ninja look like a boxer look like a fighter when you're training It's it's a great move to learn and it's the best because it's like the basic jump rope skip So that's a very good move to have in your repertoire It also allows for a lot of transitions It also takes a lot of pressure off your feet because it's a very kind of lazy step if you will All right guys next up jump rope heel taps jump rope heel taps now You're probably getting a little bit tired. That's okay push through this ladies and gentlemen remember the best thing about doing high-intensity short burst workouts is that You never have to worry about Sorry thought I turned my mic off there for a sec the mic is on ladies and gentlemen The best part about doing high-intensity workouts is that they don't last that long so guys I know you're getting tired right now But just get as intense as you possibly can for the remainder of this workout Repeat it one time and be done with it. Go do whatever you have to do the rest of your day to live an epic life Gentlemen, we're on the second half now jump rope toe taps jump rope toe taps Jump rope toe taps looks a little bit like feet front to front to back, but it is not okay You're leaning back and reaching out to tap your toes rather than feet front to back You're literally moving one foot back and one foot forward This is just you're staying in the regular bounce stance, but then throwing one of your feet outward Right ladies and gentlemen the crisscross now we're gonna get into some more challenging tricks The crisscross I'm only doing it every few if you'll notice here and by the way guys I'm sure you've seen this by now Brandon and I mess up like we have a lot We mess up all the time when we're working out the key here. See I just messed up Doesn't matter just get right back on with your workout and put a smile on your face You know jumping rope is a fun thing especially when you're doing it in front of graffiti I also highly recommend jumping rope in front of graffiti that is colorful because it will immediately improve your day and raise your dopamine levels So do that right now We're gonna up it up up it a little bit and have jump rope run in place crisscross So a little bit more challenging you got to get your feet down a little bit more For this move, but all we're doing here is doing a crisscross Notice how my hands stay in that figure eight kind of motion and what I recommend guys actually choking down on the handles Grab the handles a little bit lower and let your wrists be loose Do you see my wrist how I just kind of fling the rope in it and it just does this nice little cross while keeping the rope tight That's because I'm letting my wrist just kind of flow freely and my forearms are what's torquing them down there Nice easy rhythm guys. All right ladies and gentlemen second the last one. I know you're tired, but Let's go 110% come on side swipe side swipe now There's a bunch of combinations you can do a side swipe for example You're gonna see me here sometimes I'm doing One side swipe and then a regular bounce underneath me other times I'm just going side swipe the whole time other times I'm going run in place with the left to right side swipe So there's many ways that you can do this trick I recommend just picking one that you think is cool and you know stick with it for a little bit Lastly ladies and gentlemen, we got the jump rope three-step twist. This is a tough move This looks pretty easy, but what I want you guys to focus on is tapping the feet in the middle and then Going to the right going back to the left. So don't think of it as three steps necessarily Think of it as you have to keep going back middle every other jump So every other jump you have to come back to the middle and then the other every other jump You're just throwing your feet out to the sides Thank you for tuning in ladies and gentlemen. Thank you for giving it your all and doing the thing with us here at ZenDude Fitness We just want to again say a huge shout out to the community for continuing to build the momentum that we see It's awesome guys There's a ton of people leveling up and we just want to thank you for being part of this awesome ZenDude Fitness community Lastly if you want the workouts, they are linked up below ladies and gentlemen. I will see you on the next workout If you guys like this video Please if you would so kindly give us a thumbs up below followed by a subscribe So we continue to grow this jump rope revolution Do the thing ladies and gentlemen and if you want access to this new program It is linked up below peace and dudes and do that