दूब, लोग, सब अर्वेदा off festival, it is wonderful to note that many experts are going to be sharing their views and experiences. The numbers of countries being represented are about 25. एर गरत्टान के सब आप सोगाँ, अगर्टिन देशवो आरवेडा आब बाराशाद, यक फरम्साभरम्सा मज शा� statues Restri. आप तरीक्टिस्नों सोगाँ औगर्टिनाई आप बाशाद, अप ़ोगत्टी थी इखुट्दिना आप आप भी दीशनाई आप छ़ाता. సార్రాలులులా నిగి పానినింతూశ్రిమాప్తి ప్ల్ల్. బింద్రరిలులు చాలుల్లా పివరిల్. अदिष्व्वाज़िएदा अवाध ऒ्नवाद चिएद़ाई क्यठूअः बूल थी आज्द. अवाध अवाध रहात लिस्टे क्यच़िया आज्ई कली त्रिश्निएद, अवाधिच्च्चिये शिक्छयाद, ूःर्शम न IF you are human, it means, apart from curing, existing elements, ूःर्वे दा औरस्सह प्रोट्गत्यक सक्थ तूल तूर्वेद ूख्णिक तूत्ँछ ूफक्द्दे क्राना ॐईद. वैद्दना अबे दबार it means enjoy your food without any tension relish every bite of the food chew it patiently this way you will never have to call a bhaitharaj home again friends, in June 2020 स़ंती का ठवदीं सोगना. बहम मिए जाहते ह board 내일 अगजी ध़ऐट आप इस्ता key अगजी अईदनँएँ बेज्ट बजीउ & parc औस औस कर मुझहीि einesा दीटिया प्र रसदी। a तेरमगेत, टिन्यर, और आद व़ासन्या फरीश्ग देमात जिएजिं कोन्तरस और अगल्टानाँ lokoveda, tamaric, ginger, and other such spices whose demand is steadily rising in the context of the COVID-19 global pandemic. तो एक जेजिनन्त ख्योड़, चत आदा पऱजें। The current situation presents a right time for Ayurveda and traditional medicines to become even more popular globally. अपने वेदांने भुम्जाए वूश्ववेदा आप गम्थ इंउप्श्द. आप अपकोग प्रणश्वाधा, लगाविप्माशा वर्दे. और सम्फंऔद आपसिई लिए गईईग्ईगाई. तोज्या कि पोच्छद वैन्पिश्गाईगाईई. ब्रूई किष्ट्रई, वे स्वियच्टिल, ब्ल्वग पर लेँई बहुज़ाए, नहींं स्वडकिश्टूरीए. नहीं मेंगा वो च़्ुत्या एक चढुरीए, जफ थी, वेयने स्वियच्टृरीझां से वो लगा, इमेजिन योर सल्प पर्फर्मिंग योगा बाई गगशिं वीवर बाई दे मुन्तेन मेंजिन उत्राखन इमेजिन योर सल्प एं the middle of the lush green forest of the north east if your lives deadlines and timelines are tracing you out it is time to tap into the timeless culture of India अगा भीवर में आप नद्याता बाई लगाश्वें और सल्फाशत्वाई सच्ठाब कोप सज्वें जो राईडिन लिए आप सश्वी कुछ पो आप शवी अप आप प्रीष नद़्ासाब रच्चन तुम्सों वीवर सच्च्छच्च्च्स्च्च्चुच ज़ा स्वेश of our land and the enterprise spirits of our youth can do wonders. On behalf of the government, I assure full support to the world of Ayurveda. India has set up the national Ayush mission. The national Ayush mission has been started to promote Ayush medical system through cost effective Ayush services. त्रेदिसनाल मेटिसिन स्टर्टेजी 2014-2023 अब भाद हेल्द औरनाश्यान देगड़्व्र्च्यों has also announced the setting up of the global center for traditional medicine in India. We welcome this step. You would be happy to know that already students from various countries are coming to India to study about Ayurveda and traditional medicines. This is the ideal time to think about worldwide wellness. Perhaps a global summit could be organized on this thing. We should also think about Ayurveda and Ahar in the time to come. Food items relating to Ayurveda and food items that further good health. Many of you would be aware that a few days ago the United Nations declared 2023 to be the international year of mellets. Let us spread awareness on the benefits of mellets. Friends, let me conclude with the quotation of Mahatma Gandhi. I think highly of Ayurveda. It is one of the ancient science of India which ensures the health of the millions in her thousands of villages. I advise every citizen to live life according to the principles of Ayurveda. The pharmacy, the dispensary and the vajras all have my blessings that they may be enabled to render the best possible service to Ayurveda. Mahatma Gandhi said this more than a hundred years ago. But his sentiment is relatable even now. Let us keep building on our achievements in Ayurveda. Let Ayurveda be a driving force which brings the world to our land. Made also create prosperity for our youth. I wish this conference all success, my best wishes to all participants. Thank you. Thank you very much.


Let's bring my ACL about three years ago. I'm trying to get rid of the q-coil and it's really amazing. Toward each labrum in my hip playing basketball within five to ten minutes my pain went down to five maybe even now it's around a three or four. Now I had a client come in today to use the q-coil for the very first time. Five seconds in she started to cry and she said the headache that had been weighing me down he's gone. Put anti-inflammatory frequencies on yesterday he got up I've never seen him heal so fast. My knee doesn't hurt as much anymore and you can feel like how powerful it is and it does really work. What's wrong with your shoulder because he was like sitting crooked and so I said oh we got to get you with the wand and started the the treatment for the rotator cuff. And I basically screwed my left knee. I started using the wand on my knees just to speed up which I'm getting better even even my physical therapist was telling me. I was gonna wreck. If I was sleeping on 70 in an American it's definitely like about two or three out of ten now so it definitely went down in a matter of ten minutes. I was in three accidents all of them were severe accidents and they had to put a metal implant for my shoulder in which left my arm impaired it's definitely already reducing pain I've only been using it for a couple of weeks. In the middle of the night I saw him shaking and sweat coming out and he was shaking with pain that's how bad it is. His sister who's a doctor wanted him to take surgery. Nothing what nothing worked for him. He couldn't carry anything and then I used a cheek collar and one month later one day he said to me I think it's working. He came home Tuesday afternoon and he was like look what I can do. I'm holding my hand in my left hand and as soon as it started I could just feel it like it goes everywhere in my knee. I was a 10. You're 10 out of 10? It's like a five. How long has he had this back problem for? 40 years. And then now he has no more pain. And he started cooking for me every single day morning and night he made up my bed and he asked me what I want next morning it transforms him.  Personality change oh my god. It's a very nice nice thing to actually get a result like that that it's cut my pain in half. It has and that's going from being heavily heavily sedated and intoxicated by prescription medications to not having any medication at all because of frequencies.


Thanks very much for coming. You can go ahead and switch to the deck. We're done with Andy temporarily, but leave his mic on and then Andy, you mute. And if you feel like coming and jumping in, just on mute and start yelling, okay? Sure. Okay. Let's go. All right. So there's Andy frozen down there mid-speech. This was supposed to be a nice little thing, but I had to kind of do a little bit of a video dance. We're here to build a Linux just for WebAssembly, Wasm, right? My name is Ross Gulachi. I'm a program manager at, well, I say program manager. I'm now a product manager, which means absolutely nothing in terms of change at Azure Core Upstream along with Andy in slightly different Andy is, well, I'll let Andy introduce himself in a second. So let's try and do this here. Uh-oh. We did not share audio, I don't think. So we're going to have to, do you have audio picked up on this, on this machine? Uh-oh. One moment. Yeah. It's over there. Apologies. I didn't think about this because I am not that good. And we'll try it again. Here. I'm going to just go push play and see how it goes. Hey, Ralph. Great to see you. And hi folks. I'm Andy Randall. I'm a principal program manager at Microsoft. Apologies. I couldn't be with you in person as I'm in Berlin, Germany right now. But we'll see if we can make this virtual co-presenter thing work. Right, Ralph? Absolutely. So thanks, Andy, even though you're still there, which is great. We're here because in yesterday and today because WebAssembly is pretty cool. And we like that. I'm not even going to talk about why WebAssembly is pretty cool because hopefully you're learning or you already know and are looking to discover new things. But there are still, because it's a burgeoning area, there are still lots of things that it's hard to do for your average, either developer or even people who are professionals but don't know about all the other work being done in the ecosystem. And so the whole presentation here is to help people discover some of those things because you want to find the stuff. You want to run the stuff. But in fact, even there's so much stuff that it is actually hard to discover. So we're trying to centralize that a little bit. If you can do that, you can spend your time building fun things rather than worrying about how you get it. Is it in the right state? How do you upgrade it and things like that? So that's what we're here for, right? And of course, there are how to ploy fleets and things like this. I feel like we've seen these problems before. If I were to get in a time machine and go back a decade to the early days of containers, I think we'd see a very similar kind of situation. Yes, sir, in 2013, Docker took this existing. Concept containers and really made them accessible. Yes, sir, in 2013, Docker took this existing. I'm going to let him run. Andy, I'm going to let you run, really made them accessible to developers for the first time, enabling them to build, package and deploy applications using a simple command line. In the context of the existing DevOps movement at the time, this really kicked off the cloud native revolution, the creation of the, the, the, the, the, the, the, the creation of the CNCF and the Kubernetes project to make containers deployable in auto scaling multi-node clusters. The criticality of this technology to the whole industry, right? Sound familiar? Led to the establishment of industry standards with the open container initiative, which alongside the CNCF ensured a multi-vendor ecosystem to really flourish. But even with these advances, containers still had challenges. In fact, just the same kind of challenges that Ralph was just talking about with respect to Wazen and deploying Kubernetes at scale was a challenge. So how do you manage a large dynamic fleet of machines with frequent updates, essential security patches, and, and why bring all the baggage of thousands of packages in a general purpose limits distro when all you want to do is run containers? What does that mean practically? What is a container optimized limits? Well, firstly, it's, it's a distro, which just has a very minimal set of components bundled in everything you need to run containers out of the box, but really nothing more. This has a lot of advantages in terms of reducing dependencies, all the things you've got to manage and your attack surface area, which is really important for security. The second aspect was an immutable file system. And this seems kind of counter-attuitive at first, because after all, in a, in a dynamic world, you want to be able to update things quickly and apply new packages and, but in practice immutability, by which we mean the OS partition itself is read only. In fact, there's not even a package manager. It's got a ton of advantages. It increases security because there's a whole category of attacks which modify the underlying operating system files, which are just automatically blocked. And it really is what allows you to start thinking of nodes in your cluster as, you know, cattle not pets in the old terminology. And what this enables, or another way of thinking about this is it's a, the provisioning model is declarative. What you define what you want on the node in a declarative config file, which is applied at the first boot. And what that means is that you can, you know exactly what's running on each node and you can reason about your fleet at scale, because you know if this node is a version X with this config, here is exactly what's on it. And lastly, one of the most important pieces here is the automated update mechanism. So when you've got frequent new releases coming out, security patches, etc., you want the servers to be picking them up, just like your smartphone does. You know, you don't really even think about the updates to your smartphone, it just automatically, either automatically updates overnight or it tells you, hey, there's an update, do you want to take it? It happens automatically, it happens seamlessly. You download the update, a reboot switches from one partition, the A partition to the B partition. And if that update fails, then it's trivial just to switch back. And if that sounds familiar, it's because it's also how Chromebooks work. In fact, CoreOS was initially derived from and inspired by ChromiumOS, an exact same update mechanism. So this model really quickly emerged as the best practice for running containers at scale. And so much so that pretty much every Linux vendor and every major cloud provider ended up building a distro like this. In fact, Red Hat, like the model so much, it bought the company, acquiring CoreOS in 2018, merged it with its own atomic host project to create a new distro, which slightly confusingly is also named CoreOS, but Red Hat CoreOS. And Google created very early on its own container optimized OS for GKE, actually very much inspired by CoreOS and derived from Gen2 and Chromium. And Amazon did the same for EKS with Bottle Rocket. And at Microsoft, we now have Azure Linux, which is now generally available for EKS as well.  But I didn't want to get more on the slide, but the key point here you see is that this is a model that really has gotten traction. Now in the team I work in within the Azure Core Linux team, we also work on a community-driven project called Flatcar, which is today the only direct descendant of the original CoreOS. So I won't tell you more about that right now, you'll be hearing more about it very soon and there'll be a lot more on it from Ralph. But first, so having heard some of that history from the container world, Ralph, how would you compare where we're at today in the evolution of the WASM ecosystem? Well, so thank you, Andy, for such a smooth presentation. That's actually our video flicker fault with the deck. So I apologize to Andy and to you. But we're going to use the same schema that Andy was talking about in terms of the ecological evolution in WebAssembly, right? And we'll start with the full developer OX, UX. We started with very limited compiler support, limited language support and various other things. And we've moved quite a bit in this category toward something like a full native experience UX. And I have to point out that even in Container Land, for example, the act of actually building the container is still not considered really a developer UX. The developer UX really still stops at the native compilation and making sure that that's all running, doing the debugging, and so forth. And then you have the package. And so there's still this kind of, we don't have what was a fully fledged IDE experience. And debugging, I want to point out, is not quite there. So I do want to say that this is kind of an orange circle and checkbox. We're making tons of progress, but there are still huge gaps in a really smooth developer experience. But I do want to also say that individual projects and companies have much more smooth experiences. It's just not widely shared yet. And in terms of the kind of vendor-specific things, there used to be in-browser-only implementations, and we're now moving toward general-purpose runtime environment. I'm going to call this a green. I would have actually, I believe that there was a vote on Preview 2 and Components today that was accepted unanimously. And so I actually should go and make that a little greener. Because with those kinds of standards, more tools, more environments, more runtimes, more languages will all be able to understand each other and use the genius, the knowledge, the embedded knowledge that's in the code in those languages already. So I think this is actually even getting greener right now. There used to be, of course, just Mozilla sandbox, Google sandbox, vendor-specific kind of things. But we're actually, like I just mentioned, moving toward industry standards. And that's not just the ability to do things outside the browser environment. It's also inside the browser environment. We already have good plans and know how to run various standards across those environments. I would call it a yellow right now. There's more work that needs to be done, but we know how it needs to be done, and that's really great. Finally, though, we still use general-purpose Linux, or general-purpose Windows, if you happen to do that. And the real question here is, if in containers we went move toward an optimized distribution, maybe we need to actually do the same. And that's what I'm going to show you. One way we might be able to do that today, we are going to build a Linux just for WebAssembly using FlatCar. And Andy talked about that just a moment ago. But we're going to talk a little bit more about the details, right? Why base an OS on FlatCar? Well, it's actually a really good way to do it. You've heard about what FlatCar is, what its heritage is, and so forth. But it's also community-driven. It's in process submission to the CNCF. It's widely adopted across the industry. It may not be the high-level distros that people are familiar with on the desktops, but the people who run operations in environments that are under heavy use in production, they do know about this and use it. It has a modular build system with system extension layers. We're going to use that today. And let's be real, we know it. So that'll be the last reason. So how do we make this real, right? There's a couple of abstract steps, and we'll dig into the physical steps. First of all, layers are good things. And so the first step is you got to create a layer for the tool you want to be in your distro, immutably. And that layer can be one tool, and here I'm going to show you lots of individual tools, each one in its own layer. And that's very useful because you say you want like, I'm going to show you like 15 tools. You can actually pull in the three you want. So that's why they're broken up. But when you get to production, you can make a layer with the three tools you're using, for example, if you wish to. So the second step is you're going to take those layers and push into some storage account of some form that you have access to that could be public. In the case of this demo and repo here, I've got public layers for you to consume right out of the box with multiple versions of as many things as I could compile before I fell over of exhaustion on Friday night. So that gets pulled in on initial boot. How? You're going to create an ignition file, which is a format. You can think of it as a first boot configuration. And it's going to tell flat car on the initial boot which layers are going to be built into this image immutably so that rolling forward when you boot, you only get those things. And it never changes unless you take steps. And we're going to talk about those steps. When that's done and it boots, it's fixed or baked. Then that is now an immutable image. Now for debugging, for use, especially if we're going to have a developer environment, you get to deploy neatly with QEMU. There's a really cool script trick. Works really fast on native Linux because QEMU is used there. I'm on Windows, which means I'm using WSL, which can be really useful for people, but it means I'm doing nested virtualization and it's a little bit slower. But it works fine. So it's very flexible. Anywhere there's QEMU. And hopefully the last step is to have fun. Just a word about layers. So I'm going to refer to Docker and the container ecosystem. If this doesn't make a lot of sense to you, grab me after or I'll be glad to back up and talk about layers and Docker and how that works. But I'm going to use the metaphor. And in Dockers, you build layers all in one file. It's a Docker file and you use a tool to take that file. It just builds the whole thing, all the layers down. Here, layers don't have to be just for containers. It can be just a file system artifact and it can actually be used to build one individual binary into something that's ready for a layer, like flat car. So let's say we're going to layer only with Wasm time. This is one of the recipes. Like I said, I've got as many run times as I could find on short notice before the flight. We're going to say Wasm time. And so if you take a layer with Wasm time in it on first boot and move it right in, the resultant image, which then becomes immutable, now has Wasm time already in user bin. In flat car, other container losses, mutable losses, you only have one user. You're essentially running as root, more or less. And that means that whether it's in user bin or user local bin, it doesn't matter. There's no Ralph home. Doesn't exist. So if you want to follow along with what I'm doing, just really quick, or if you're watching this after it's released on YouTube or whatever, this is my repo at Scolacci sys-ext bakery. Now this is a fork of the upstream flat car layer bakery, which doesn't have like four or five recipes. I've got like 15 recipes. All of which are web assembly related tooling and so forth. So now let's get concrete. What are we going to do with these layers? What do we actually do? Well, you're going to bake the stuff you're going to eventually eat. You need to bake the bread that you're going to serve somebody. That really means you're going to clean and download your binaries. You're going to create your new binaries, make sure that the build environment has what you want. You're going to put them in the system extension directory. And in that system extension directory, you're going to create the user local bin or user bin as I said, it doesn't matter because there's not multiple users here, right? And you're going to put your binaries into it and you're going to clean up any mess and you're going to create your raw layer file. That is the layer you're going to use. Now what's interesting about this is if you're familiar with Docker files, notice that one through five are pretty much that's what your Docker file is. So the only thing missing here from the Docker experience is that you know the from statement at the top of a Docker file. Now that is really a reference to layers that already exist. And so when you bake, you bake everything at once. In this case, you're doing the same steps, but the base file system, the base layer collection, is actually the flat car image you're going to deploy. And so those things already exist and you're creating a collection of layers that on first boot will be laid on top of that, rebaked into the final menu you've selected and that becomes immutable. That mostly makes sense. And if it does, because I don't want anybody to say it doesn't, that would be bad for my timing, right? The next thing you're going to do is create your layer file or raw file, okay? This is, if you notice, pretty much what Docker build does. The only difference is it's a layer and not the entire collection of layers, right? So the next thing you're going to do is you're going to take your baked goods, your bread or whatever, you're going to put it in the distribution truck so that people can consume it. You're going to upload your files to some endpoint. Here I have Azure Blobs, but you could put them in a GitHub repo, you could have secured endpoints in a private network. Like a lot of ways you can distribute this to your specific images when you're loaded. Notice that this is essentially pretty much Docker push, right? So the metaphors of what we're doing are actually using similar technologies in the same steps. The only difference is instead of building the whole thing first and sitting it on top of a kernel, which is what Docker does, you're actually building all the important stuff and choosing an image to sit those layers on top of. And that gives us a lot of power. So here's my menu for you right now, right? I've tried to collect as many runtimes. So I was chatting with Ben earlier. He's got some other runtimes available. Other people do. I didn't get to them. I want everybody to submit PRs with recipes for their favorite WebAssembly tools. I don't care where they come from. I'll bake them and see if I can host them. And as we go forward, the ones that become really solid and are used, let's move those up into Flakkar's bakery repository. So I promise to make sure that that gets done. You can see a bunch of runtimes. You can see popular runtimes. You can see app hosts like Spin. You can see tools like Modsurfer and things like this. Okay. So now you're on the other side. How do I consume this? Well, you're gonna need to choose the baked goods, right? You always serve other people first. We talked about an ignition file. I'm gonna show you what that is now. Let's make sure we got plenty of time. We do. And that's the thing that is the list of items you're gonna choose from your menu and set the table. Now, these are the details for setting the table. I'm not gonna rest on this, but this will be available. So this recipe will be there. This recipe is also available upstream in the Flakkar recipe repository. So what does these ignition files look like? I'm gonna, here's a simple one. Essentially what this means is I had to go get the image for QEMU, the Flakkar image. That literally is all I'm doing here, right? So those things are in the repo. So this is a very simple ignition file. It's already compiled out to JSON. You can author these in YAML and then convert them. So for those of you who love YAML, I'm sure it's the entire room, YAML is your preferred language. But you can see that what I'm essentially doing here is just saying there's a lunatic layer and it doesn't have any versioning. That's gonna be important when we talk about updates. And it loads initially a layer from this menu that I have in the sky. Now, it's always best to eat locally. As I said, I'm gonna use Windows and WSL. Linux, Windows, WSL, it's all the same process. The script I'm gonna use just grabs QEMU, creates a new VM and begins the boot process in the normal Linux way. But flat car is gonna do one thing first. What it's gonna do is first finish setting the table and serve the food, right? Now, do we want live demos or do we want, do we wanna risk a live demo? All right, I figured as much. All right, okay. Now, we'll pop this up a little bit, I think. We need to switch, do I need to stop? We need to switch to the live thing. So, I'm gonna go ahead and stop the slideshow. Is that what I should do? Huh? Yeah, I wanna make sure that everybody, no, well, everybody needs to see it up there. Because we flipped to, we're gonna try a live demo. And if we can't flip the AV fast enough, we're not gonna try a live demo, but we will. How do I know? Because I can see my screen, my monitor here, but I can't see it there. My apologies for not letting you know, we might fork the way the presentation went. Yeah, I wanted to mirror. Oh, that's all you needed me to do. I could have done that, yeah, that's fine. Okay, great. All right, let's bump this up a little bit so everybody can see. Right, that big enough? Okay, this is the list of recipes that I'm gonna show you. Not all of these recipes work because for various reasons I didn't finish all of them. So for example, there's an experimental wave runtime here. That doesn't work. I'm hoping that those involved in the wave project will finish off the recipe and give me a PR. I'd love to build that. The WebAssembly, the Wasm Edge doesn't quite work. It deploys, but I was gonna work with Michael and the team to get that one updated. So I'm hoping I'm gonna ask them for a PR. But everything else works fine. So if we go and clear that, we're gonna step back out to the Wasm Flak cards and we're gonna go to the developer experience. And the developer experience is gonna work like this. There is an image already there, but I'm gonna deal with that later. You can see I've got a couple of recipes. I've got a Whammer and Wasm Time recipe. I've got a Lunatic recipe. I'm not gonna build the Wasm Festival. It takes a little while on WSL. But who votes for Lunatic? Who votes for what? Who votes for Lunatic? Okay, there's two votes, three votes. Fine, you experimental people. That means I'm gonna do Wasm Time Whammer. So the first thing I'm gonna do is copy in that version of the flat car image right here. Right? And so now I've got that. And then I'm gonna go ahead and use this script, which is from, it's the script from upstream flat car. I'm gonna pass it in an ignition file, which is Wasm Time Whammer. And I'm gonna say, hey, just wire up the console. Oh, I'm gonna have to pseudo. All right, let's see if my cell phone can actually support this. Here we go. Now this should take about, in the normal case, takes about 30 seconds on WSL. Takes about 15 seconds on a regular Linux machine. You've already jumped in through Grubb. Now we're booting flat car. Right now, it's going up on the first boot to grab the layers I told it to get from the Azure Storage. This is just a public storage blob. You can grab them, do everything here. Here's where we get into the loop. So if the network is flaky, this holds up a little bit at this point. If you're on a good network, it just comes streaming right in. So I will not wait for long, but there we go. Now you have the joy of watching the boot stream. At about six to eight seconds, you'll see that it's close to, there you got the BTRFS. When it hits the EXT4 file system and amounts the file system, and then the layers are already pulled. So now we built the image with the layers in and turned it immutable. And we're in. Now, we did what? We did wasm time and whammer in the end? Okay, so now I should say wasm time version. And I've got wasm time, okay? And what's whammer? Is it I wasm? I think it is. Yes, it is. Okay, great. So I wanna just sudo rmf user bin wasm time. And the answer is no, you can't do that. We're fixed here. We're immutable. By default, this does not even come up with SSH capabilities. Once it's in, it's running. It is an appliance distro. And this is fantastic for sharing. It's fantastic for updates. It's fantastic for all kinds of things. And if you're gonna do a shutdown, you just do sudo shutdown. Now, power off, right? And we're done. Great, fantastic, all right? But notice, I've got a wasm festival, in fact, I've got a wasm festival repository here. So let's see where I am in my deck, right? I'm gonna make this professional.  So let's do this, okay? To make it professional, what we just showed you is, hey, one layer, two layers. I have a one layer recipe with lunatic. There is a wasm festival recipe in there. That recipe builds an image that has every single tool in there. And now, whoever needs to start using those tools can just grab the distro, they're good to go. And they can use that to test which version of which thing they want later on when they get professional. But when you get professional, you're gonna want things like updating it securely, right? How can I zero in on, say, spin or lunatic or wasm workers or something like that. And have only that or my runtime or my lab tests, my training, whatever it might be, you need that doing. To do that, you update, keep it updated with something called Nebraska. This is the open source, you might call it the update service that a flat car has. So you can update flat car nodes. It uses the Olmahawk protocol and the update mechanism from Chromiumos. It works both with the partitions, the core base image, if you will, and also with the system extension layers that we've been building. You can switch between A and B partitions, automate, update, roll back, even hot-swapping the base image out from under the applications, these layers, without actually the layers and applications really knowing about anything that happened. And you can do the reverse. You have fine-grained control over the fleet upgrade and you have monitoring and visibility. And this is all really, really cool, right? I like it. So, as we get toward the end of this, I wanna show you the more professional experience, right? And for that, I'm not gonna do this live. It's a little bit small, but I'm gonna go ahead and do the demo because I wanna make sure that we get our time taken care of here, right? For this one, let's see. I think I'm gonna copy this in. Oh, no, I've gotta skip this one because we wanna do back, back, Ralph, back. Nope, that's Dev Flatcar. Hey, I swapped out the wrong video. I like it. So we are gonna do it live. You ready? I'm gonna go back here.  Here, we don't have an image yet, so we can boot from scratch. Oh, yes. And better, yes? Okay. So we have, we're gonna use a recipe that only has wasm time, but what we're gonna do with this recipe, right, is we're gonna do this. Code wasm time. YAML. And so when we show this, what I'm gonna show you is, okay, that this recipe not only sets up a configuration for updating wasm time. It tells me where to find the updates, right here in the path, right? It also tells me what kind of formula to use to match updates both with a wild card for version and with a wild card for architecture. It goes ahead and downloads one initially, and it says that version initially is gonna be 10.0. And so the rest of this is going to be, this is the key part. It's going to update every single minute. So this is, I'm gonna go do this demo. We're gonna build one more time. This will be the last demo of the presentation, right? And to do that, we have to, let's make sure we got, yep. So we're gonna do cp, cp, bring in the production image. I think that's right. Yep, okay, great. I just forgot the dot. Okay, I got it because my naming is long, but my fonts are big, so forgive me. And we're gonna do the same thing. We're gonna do sudo, flat car, I, right there, wasm time, JSON, no graphic, and I don't know whether I did it. Yes, I did it. I couldn't even see me typing and I successfully filled it out. And so now we're booting a recipe that automatically updates every minute by hitting the repo and doing a match for architecture and version for wasm time. And this is where, this could be a secured endpoint. It can do any kind of authentication you wanna have. We're now testing out the cell phone network again. I hope it boots at the same speed. I do have a video that I could flip to and show you how it works, but I don't wanna crowd the next presentation if I can avoid it. So I'm gonna pray to the networking gods here for one more moment. Please make this happen. Hi, everybody. How are you? I'm gonna count 10 seconds before I flip to the actual. Ah, thank God. Phew, okay. And now the question is, how long does it take to bake the layers? Okay, it's hit the layers and is it going to take another 20 seconds? This is the joy of live demos. Now I gotta count for another 10 seconds. Okay, one, work last time. Four, five, six, seven, eight, nine, eight, 10, okay, fine. So what I'm gonna do is go ahead and find the video. Right, and let's see downloads. And there we go. And I'm gonna jump ahead, right? Ooh, that is the wrong one. I have failed you because I have made the wrong, whoa. Okay, thank you very much. I'd like some applause. That actually worked. Now watch what happens. If I do a was on time version, you start 10, okay? 10 is installed. Wait for system D, because system D, we're all one user, system D and me are both core. If update works, we should see system D go out, check the update spot and find it on this network, my cell phone. I really deserve this, don't you think? So what I'm gonna do is actually clear to waste time. It's still 1.0. And how many minutes are we willing to go over? Come, help me, help me networking gods. So I'm gonna finish this demo. Andy, are you there watching me be tortured? I am there, it's very entertaining, yes. Yes, oh, great, I'm so pleased. This is actually the last demo. We have a rampant. The rampant's you intended. Yeah, exactly, yeah. So this is actually the last demo. This is merely the network not hitting the thing. I'm happy to show you how it works. It'll probably work perfectly just after this, right? But this is the price of a live demo. Does anybody have any questions about how all this is supposed to work, right? If we, let me know if we get some console log streaming from DMessage, right? Cause that's really, that's what's going on here in theory. Any questions about Flakar? Andy, I have a question for you. So with an update mechanism that I'm attempting to demonstrate, the Nebraska process, is it possible to do all kinds of authentication solutions to reach that, not just in private networks, but like, can you do a pre-PKI dance and things like that? That is a good question. I don't think there's a whole load of different mechanisms for getting, for authenticating. Yes. Thank you. So the interesting thing here is that at very least this can all be in a secure private network, right, like, and this was HTTPS, so like you've got the server side authentication and so forth, that part is easy. And so I'll work with Andy and talk to the Flakar community to find out about all kinds of protocols that can be added and layered in on top of that. But the critical thing here is now I've automatically updated it. So this is a device now, immutable. This can be sitting anywhere, and if it's disconnected, it doesn't matter. It keeps running and nobody can change it accidentally. So there's no state drift here, which is critical. And then if it gets connected, it will on whatever you configure, reach out and bring in whatever the update is. So the update activity now belongs upstream in that repository, whatever the repository is that you're using, right? So that's the critical aspect. And I'm hoping, let's see if I can pop back up here. Nope, that's the wrong one, right? So I'm hoping, let's keep going. Nope, there we go. How to play with Flakar wasm. Clone the repositories. Please modify any of the recipes, right? Submit your own recipes. Do you have a question? Okay. Yes, that is exactly what happened. And even more interestingly, what it did is it came and dropped the layer in where the previous layer was. And since the actual binary name is simlinked, right? It then swaps the simlink to point at the version. You could SSH, you know, I'm like, that's my VM. So I can't even modify that simlink. It's the system itself that is modifying the simlink. From now on, if I boot with or without an ignition file, I'm just gonna get what I got last time. It doesn't even matter if you press a new ignition file. It will not reload anything. You get what you get, right? But you can do updates and rollbacks. That's possible. Yeah, in the corner. Yes, so raw files do have metadata in the normal layer fashion. I do wanna say this. Please push layers and recipes to my repository. I will bake them, test them, then everybody can use them for fun right now. And as they get more useful for people, I will submit the PRs back to the Flakart community and then you can jump into the Flakart community or you can submit them directly. Feel free to do whatever you like because it's purely open source and purely community driven. If you're researchers, if you're business people, if you're building POCs, your own recipes will work here. You don't need my stuff. Now, that was a good question about layers, like what's really going on. Let me show you what's really going on very quickly until the team kicks me out, right? Which is entirely possible. So if we look at Lunatic for the sake of discussion, right? You can see that this is pretty much a Docker file only in a bash form, right? And there is an algorithm, as I said, you're creating a, you're grabbing the binary you want. You're creating a system extension name, a directory. You're actually adding where you want. It's a deployment to end up being. And then you go ahead and after you, in this case I'm moving it right into that directory and then you clean up if you need to clean up and you call bake. You're baking an image. This is the script that bakes it, okay? So the answers to all your questions are in this script. If you look very carefully what you go down here aside from the configurations and architectures and stuff, this is the sweet spot right here, right? That's what's going on, all right? That's the sweet spot. And it's just a script. These are just standard Linux tools and you're building a layer that Flatcar knows how to deal with. But the metadata you're talking about is the magic is in the system extension directory. That has a actual configuration. So for example, the extension, the layer I'm talking about actually doesn't have versioning information or architecture information in it. The fact that the files do is something that I do. I actually copy that in there and that allows me to use the kind of regular expression type thing to grab a particular version and update it automatically. But the extension itself thinks it might be updateable. So it just, you build that as a generic name, wasm time, right? Lunatic, spin, anything else. And then you can host it and your file name is how you pull in the update in a SHA sums file. They're listed all there and the update checks that. Any other questions? So I'm gonna let Andy wait in here.  No, I'll just wrap up myself because really all I wanted to say there is I think we've had a lot of fun. So Ralph and I have just been working on this along with the flat car team over the last couple of weeks putting this together and just kind of seeing how it's all come together. I think it's really exciting because it is, as Ralph said, it's community driven. We feel like there's a need there in the Wasm community for something like this. And the fact that we can build this on flat car is just kind of a testament to the architecture that's being built there. So really looking forward to, hopefully everyone in the room here going and trying it out and letting us know where they want it to go. So thank you very much for coming. I really appreciate patience. Thank you to the networking gods for finally kicking in. I hate Ivan for having chosen the live demo version instead of the video demo version, but I think it worked out fine. I'll be out there in the hallway. If you've got anything, I will build layers for this all the rest of the day and push them up. So if you got something you want me to build a layer for, just come, it takes five minutes to build a layer. It's really dead simple, right? So just meet me out there, love to do it. Thank you very much. I appreciate it.


Coach, we talked about the team showing signs of maturity and growing. What did you see from your team when the Suns cut it to five, called the timeout, and you guys went on to run that third quarter? Yeah, you know, Mike, I think it was like we're growing up in terms of our physicality on the defensive end. I thought we, you know, teams are going to make a run in this league. That's a talented team. We, I think we, we took it calmly. We didn't panic. We were going to run, was going to be made and, you know, got out and got some stops. And then, you know, the ball started going in the basket a little bit, but really pleased with our physicality on the defensive end. What's been the biggest difference in your growth there on the defensive side of the ball? Yeah, just more active these past two games. You know, they had 20 turnovers tonight. You know, we talked about that in the off-season, improving our activity. But again, I think that's, you know, that's our mental maturation. I think it's our physical maturation. I think both of those things. I thought Ed Davis was outstanding.  So sometimes that's contagious, but he was, he was excellent. When you, I mean, when you're hitting, even on the offensive last, and getting second chance points, being physical on both ends of the court, I mean, I guess just how encouraging is that for you going forward and physicality shouldn't go into a slump. Yeah, no, that's great because we were nine for 36 from three, Brian. So, you know, one sequence in the first half, Allen Crab misses a three, chases down. I think we get two or three offensive rebounds. We end up kicking it out. And I think it's a Joe Harris corner three. So, you know, again, it's that, you know, you have nights where you don't shoot a well in this league. And we did all the other things to, you know, help push through. What the job Karris did in making, in making Devin Booker work on defense, but also making Devin Booker work when he was on offense. So I think the advantage we had, we had Karris on him, and then Spencer came in and relief. So we had two guys to throw at him. I thought they both were excellent. Karris was superb on ball bands, but I thought Spencer also, you know, came in and relief. And that's tough when you got two kind of six, six, six, seven guys that can defend the ball like that. It's a huge advantage for us. You had a couple of spots where they cut it to five in the third quarter and you responded and then they cut it to 10 early in the fourth and you responded. You think they're growing a little bit of confidence and maturity right there? Yeah, no, I think in the past we might have, you know, we might have, could have folded in a situation like that. So, you know, again, I think it's, it's, we're a maturing team where we're getting, you know, mentally tougher and especially on the road that can go away quickly a lead like that. So it's, you never feel safe. So just, just I see our guys growing in that aspect. It's encouraging. It's not, as an example, the rebounding isn't just coming from the rebounders.  There was one Shabazz went up and got one. Listen, we can't emphasize it off. We've done film presentations, analytic presentations. We're just trying to get them to understand how important it is because our effective field goal percentage defense we're top ten in the league. So we, we teams don't shoot well against us. That's, that's the truth, you know, right now. And we really got to, you know, plug, plug that rebounding thing. It's, it's, it's huge. So I thought everyone was trusting back tonight. We're going to need the guard rebounds. And of course having that Davis get 13 rebounds doesn't, doesn't hurt either. I think you were asked this before I got here, but just as far as the turnovers, the activity that it shows, they've carried over from Philadelphia. And do you think that it's kind of sunk in, that the message is sunk in with these guys? Yeah, I mean, I'd love that to be our identity a little bit, you know, with the speed and youth. You know, I think we're stronger. We're stronger physically. I think that helps a little. And I think we also trust our back line. You know, I think we trust Jared Allen. We trust Ed Davis to protect the rim. So that allows us to be a little more aggressive.


Hello and welcome to the Jenkins documentation office hours. Today is July 6th and this is the US edition. Today we have myself and Bruno Brockman. If Mark is does end up joining us will invite him in later when he comes but for now it's just the two of us so for the agenda. So, I know that we had the midterm presentations for Google summer of code just short while ago. Welcome. We're just talking about you. All good things I promise. And just going over the agenda. So, yeah midterm presentations just happened earlier today so there'll be lots more about that in the future. There have been some open pull requests of interest that we can discuss. I added a few more this morning, based on what I've been working on for the Java seven transition. Just a couple notes about housekeeping. Is there anything else that we should be putting on the agenda or anything that anyone wanted to add. If not, no worries. Okay. So, starting off so Google Google summer of code is well underway. And we've actually reached the midpoint of Google summer of code. And as a result today, we hosted the mid we, we had the midterm presentations for Google summer of code. It wrapped up roughly around 12 o'clock earlier today so very very fresh, which is great. And the mentors were asked to evaluate their, their work on GSOC for the contributors. And some of the questions that they asked themselves and we're part of the evaluation are listed here, really, just to get people to reflect on their actions their their connections and really like how can you improve from here for next year, if you want to continue to be a mentor. It's a lot of them are very straightforward questions, how do you communicate and how often when how did you help, how are you helping them track this so just really good insight to keep in mind for Google summer of code now going forward. And if I'm not mistaken, and Mark, maybe you and or Bruno could confirm the web, the presentations. The presentation recording it will be available layer and available for everyone to give a watch. Yes, correct. That's right. Beautiful. And anything that you wanted to share about the midterm presentations Bruno or Mark. Mark, go ahead if you have something now. Ashutosh did a great job demonstrating talking about Docker quick start. Thank you. Congratulations to Bruno as the mentor and I felt really good about the get lab plug in modernization presentation from harsh harsh Pratap Singh. So the two that actually I guess the third is the Jenkins.io rebuild. That one is for me the most scary because it's such a huge project, but it's making good progress. Yeah. And I was actually checking out the prototype site earlier that Bundy had provided and it looks really nice and clean and I like the presentation of the page and how everything's called out a little bit more like specifically I was looking at the installation docs and just really enjoying the fact that like the code blocks are color coded now so that they stand out. The notes are a lot more kind of a parent instead of hoping that they're noticed and like the text is always a little grayed out on the notes which I thought was interesting and the fact they're just regular text here but clearly signified is, is, I think a lot better and visually in terms of the documentation so yeah. So, Google summer codes and making great progress we're going to continue to do so we've got how many more weeks is it in total for Google summer code. I think we still have six weeks to go. I think so. Awesome. So, yeah, so that brings us right towards the middle and slash end of August. So, perfect. Great. Lots of lots of stuff to look forward to and yeah even if that alternative alternate build for Jenkins.io is a larger projects will be available to keep working on after the fact to just because Google summer code doesn't continue forever doesn't mean that doesn't that work stops. So, next, so some open pull requests of interest. There was one submitted recently by to new Sharma updating the administrative Jenkins on Kubernetes docs. I've gone through from a documentation standpoint and really more than anything else this is just requires review from people that are experts on grenades, or anyone that's more familiar with Kubernetes and it's an ounce then I would be. I think we've asked Davion and a couple other folks in the pull request if they'd be available to take a look at it and provide their feedback. There's anyone else that feels comfortable or so inclined to review the Jenkins and Kubernetes pull request there's still plenty of room for feedback and suggestions here. We'll be working with the news to make sure that this is organized and put together in a way that we can actually merge it and get it published on the page on the site. Thank you to the town news for this and this is a continued effort that he's been working on for a little bit now. So, just, again, really appreciate the work and the consistency that's usually been putting in on that makes a lot. It makes a lot me feel a lot better and a lot happier just having everyone working. So, there was one that Jeffrey Chen had submitted a while back for the best practices page. This just needs some more text and context to be filled in on it. It's something that has been that was being migrated from the Jenkins wiki. So, this does need a fresh little eyes some more view and potentially some help in finding any gaps and closing those gaps in function form function or any sort of updates that we've had between when it was originally written now. Yeah, that's one where I think I need to enlist help from Darren Pope, as one as a possible reviewer just to say, Hey, what should we say here and what other practices should we add the the concept of a best practices or preferred practices is inevitably loaded with opinion. Right. And so what you're seeing here is Mark weights opinion, based on things ideas extracted from the wiki page that was created long ago. And best practices or definitely something that users come to expect and get a lot of use out of and I mean at least my own experiences it's been it's always been very helpful so having something there even if it is opinions and suggestions, you know, it will get someone started and that's the best thing that they can do for someone. There was another podcast submitted on the scripting and security. This was actually one that was submitted a couple years ago, November 21, but makes created a lot of great content here and has gotten a lot of feedback and review from folks like Daniel back who are the security go to person for Jenkins or that like a lot of people have gone through and worked on this. This just needs to be updated and put together in with the comments suggestions everything applied. And some more of you of course by the security team there's most likely didn't change it since 2021 women's first submitted so once we have that. This is something that myself or Mark could work on because there is all this already existing context and content. So this is something that is going to be now on my radar going forward and I'll be looking at this to review and edit. And also on the script security page that we should be aware of Mark or anything that I should keep in mind as working on this. You described it well it's, it's a long ago attempt by Meg to create some something helpful for users and it's been through multiple reviews and probably yet needs more. So Meg doesn't have time or capacity to do further work on it. And so it's up to somebody else and Kevin you could pick it up I could pick it up etc. In any case I think our work on Java 17 is higher value than that for right now. Yes, of course. And speaking of so as part of the Java 17 transition. I'm going through the installation guides and updating the documentation as I can. And put we merged the Linux installation documentation so this now has a note indicating the change with the release of devian 12 that open JDK 17 is now the option the version being delivered and all of the corresponding paid parts of the Linux installation now include JDK 17. So I've gone through and tested this one in on devian and I was able to also get review from Mark and a couple others confirming that everything was working and correct. So, we've got that. And then I just also submitted an update for the Docker installation documentation. There was no hard and fast mention of Java 17 but I went through and updated the formatting. And some of this in text and some of the other I didn't change their content necessarily just cleaned it up so that it's yeah more in line with the guideline the documentation guidelines that we have set in the style guide itself. And I'm still going through and I've got other installation documentation, the job of upgrade requirements, etc. that I'm working on getting the transition finalize there and completed. Now, maybe a few months from now after GSOC will have to make another PR regarding the update, you know, the Docker installation guide, we may have a way to install it with less instructions, we'll see. Thanks to the Docker quick start got Docker quick start and everything. Maybe that's my hope. I don't know. It's just out of the blue will see. Yeah. No, for sure. And I was when I was reading through this earlier. I noticed that there was, it was stated that there would not be a need for the dind anymore. And so that would definitely change the instructions here so yeah, if it does come down to that we can absolutely. I can't promise that for each and every tutorial existing in the Jenkins IO, we will be able to do without Docker in Docker, but for the first five, I can promise this is the case for the other ones. We'll see. And then so the last note that I had here on the agenda for today is that mark will be out of office the next two weeks so the docs office hours Asia either will need to be hosted by another person if there is a volunteer or if not skipping those meetings so just something to put on your calendar keep keep be aware of this will. I'll be sure to bring this up again next week during the EU US office hours so yeah and there's we discussed it during Asia office hours last week and came to the conclusion that we just accept that the meeting won't happen. Okay. So, I'll I have the action item to delete them from the calendar if I haven't already done it. Is there any so that was what I had on the agenda for today is there anything else that we want to talk about or bring up or discuss here in office hours today. Just maybe about the June newsletter. The PR has been created it's not ready yet mostly because I did not do correctly my homework. I should read that tomorrow and we hope to get it merged on next Monday at worst. I'll be reviewing and going through it right now as well to get everything aligned so that any additional updates or changes that need to happen are not so time consuming. Yeah, and thanks a lot to all the contributors. Absolutely. Great. Okay. I'm really scared of everything I had for today. What will will end the recording here and the record it'll be available 24 to 48 hours. Thank you as always for joining and have a great rest of your day.


In order to collect items needed by domestic violence shelters and programs, Team Kentucky has partnered with Local Food Cities for their 16th annual shop and share to collect donations for Turning Point domestic violence services. The clients that we serve know that those donations came from their local community members and they feel the support of their community while they're going through the healing process.  You'll experience patient care that is specific to you with exceptional follow-up care that ensures your hearing and balance needs are being met. Audiology Associates at 1428 Northlake Drive in Prestonsburg. Donations will be taken up at the Pikeville Food City on Cassidy Boulevard and the Prestonsburg Food City. Some items Turning Point is in need of include non-perishable food items like soups and pastas, personal hygiene items like shampoo and diapers and housekeeping items like paper towels and liquid soap. We do provide everything in the shelter that the clients need so we provide all the food and hygiene items and all the supplies that you would need at home. We provide here for them in the shelter. Volunteers are needed for the donation event. If you would like to volunteer you can call<PHONE_NUMBER>. Donations will be taken from 9 a.m. until 5 p.m. at the Pikeville and Prestonburg Food Cities on Saturday, February 10th. For Mountain Top News, I'm Kelsey Fidele.


Lagos State Government generates approximately 13,000 metric tons of solid waste daily and to achieve the levels of efficiency required in managing waste in a city of the size. The private sector must be front and center while the government focuses on regulation and support by way of infrastructure and technical capacity. This was the submission of Lagos State Governor of the Nordic-Nigeria Connect High-Powered Conference on Smart City Solutions and Circle Economy held in Lagos. Plus, TV Africa Lagos State Government correspondent has more in this report. These two events engage Nigerian and Nordic private public stakeholders on smart and green city solutions for Lagos. The focus is on how to develop a circular and smart economy with a specific focus on waste management, green energy and transportation. Governor Babaji desangulu listed some of the efforts being made by his government for our greener Lagos. The private sector participation, which are largely citizens' faith focus, you know, so what we've done is indeed we've invested in areas that were used to support the PSPs which are facing, you know, the general public. We're building new transfer loading stations for this agency and we're also wrapping up existing composite facilities. We're renewing our waste management fleets and we're assisting a private sector with fleet renewal as we go along. The governor also helped on the need for a change of mindset among the populace, new habits regarding use and reuse and the immense possibilities of recycling. Saoulu also spoke on the wealth creation potential of waste. We're heavy users of plastic materials, so there's a lot of work that's ahead of us in terms of educating our public about the responsibility and responsible use of disposal of plastic to cite one example. So Loma has therefore been actively involved in redefining his remit, expanding beyond the conventional waste management oversight to sending and building a thriving waste economy in the States. Deputy Minister of International Trade Nina Vasculati told the Guardian that her first priority is on making the COVID-19 vaccine available to everyone. Nobody is safe until everybody is safe. That, I think, is the first priority for all of us to make the world a better and a safer place to live and to work and to co-create together. Or most importantly, Lagos is taking giant steps in becoming a smart city. Mr. Governor, let me already at this point congratulate you on that. One of the take-homes from the conference is that Lagos is open for collaboration and investment. From Lagos, love Ikuku Uyedukum for Plus TV Africa. Don't forget to hit the notification button so you get notified about fresh news updates.


Manufacturers are starting to put more focus on the environment, producing laptops with more and more recycled materials. Acer is a front runner in that regard and the Aspire Vero AV 1451 embodies it perfectly. The whole laptop is made from recycled plastic, which has a green tint and debossed logos all around, with Acer on the lid while the base has an Intel Core logo. The chassis is covered in speckles and has a rougher finish, which makes it very grippy. Thankfully, the lid opens with one hand and acts as a lever, lifting the rear end, for both cooling and ergonomics purposes. Due to the laptop's smaller stature, weighing only 1.5 kg and having a 14-inch form factor, the keyboard lacks a numpad. The keys have long key travel and clicky feedback. There's also a backlight. The touchpad is covered by ocean-retrieved plastic. The surface is smooth and has an embedded fingerprint reader, which doesn't affect the experience at all. The laptop has two full-sized USB 3.2 Gen 1 ports, one Thunderbolt 4, an HDMI connector, and a 3.5mm audio jack. The 14-inch Full HD IPS display is a great addition to this device. The viewing angles are excellent, so videos and movies will look great regardless of where you're looking at the notebook. It has good max brightness of 305 nits and great 2020-to-1 contrast ratio which is one of the best we've ever tested on a laptop. The panel has excellent creator capabilities, covering 95% of the sRGB color gamut and showing decent accuracy with the stock settings, which gets even better once our design and gaming profile is applied, you'll find a link in the description below the video. Only 2 per 100 people watching this video are subscribers. If you decide to just start following us, we'll be able to reinvest more in our laboratory thus making even more helpful videos for you. Thank you, you're awesome. The laptop gets very good battery life with its 53Wh unit and a core i5-1235U, lasting for 11 hours and 11 minutes of web browsing, or 10 hours and 56 minutes of video playback on a single charge. That wouldn't be possible without the most efficient Intel chips that Team Blue currently has in its Alder Lake arsenal. The U-Series comes with a high core count, with the core i5-1235U specifically beating its Tiger Lake counterparts, but still falling short when competing against the 3D rendering performance of AMD and its Ryzen 5000U series. The integrated graphics on the inside are ideal for this device, keeping power usage to a minimum while managing to deliver performance both in productivity and daily usage. You can also play some light games like Counter Strike Global Offensive with about 80 FPS on medium settings. By the way, you can subscribe to our new laptop media benchmarks channel, we've spent two years to test all the laptop graphics cards on the market, with all popular games, on all graphics presets. The cooling setup here is simple, with two heat pipes that connect to one fan and one heatsink. In the stress test, it does throttle, dropping its wattage from 55 watts in the short run to 28 watts at the 15 minute mark. Of course, this laptop isn't made for video editing, so that's okay. Comfort wise, the laptop is quiet, as the single fan can't produce a loud noise, despite trying its hardest. The hotspot has a low temperature, maxing out at 40 degrees Celsius, even after 30 minutes of 100% load. The teardown process is simple, check out our dedicated disassembly video. Upgradability does suffer a bit, with the memory being soldered onto the motherboard. Still, you can access the storage, through 1M.2 PCIe X4 slot that supports Gen4 drives. The Aspire Vero finally presents a quality offering for those who care about the environment and want to dedicate their laptop to the cause as well. Previously, such gimmicks would charge a pretty penny, but in 2022, the laptop is affordable, while not sacrificing anything of importance. If you want to see the rest of the tests and more details about the device, you can check out our in-depth review. The link is in the video description below.


Rafael Nadal vs. Taylor Fritz is the third quarterfinal for Wimbledon for 2022. Both players have had different roads to get to this quarterfinal stage. Fritz started the tournament off as the number 11 seed and would play fellow youngster, Moussetti. But this didn't bother Fritz at all. Winning in straight sets, 6-4, 6-4, 6-3. In the second round, he'd take on the wild card from the UK, Gray, and after a close second set would eventually prevail in 3, 6-3, 7-6, 6-3. In the third round, he would take on Mulchan, a player who was coached by Novak Djokovic's old coach, Marion Weider. And after an easy couple of sets, the third set went to a tie break with Fritz eventually prevailing in 3, 6-4, 6-1, 7-6. In the fourth round, he'd take on the qualifier from Australia, Jason Kubla. But Fritz had no troubles winning the match in straight sets, 6-3, 6-1, 6-4, to advance to the quarterfinals without dropping a set. Rafael Nadal started the tournament off as the number two seed and would play Serendola in the first round. And after winning the first two sets, Rafael would eventually prevail in 4, 6-4, 6-3, 3-6, 6-4. In the second round, he'd take on Barencus. And similar to Serendola, Rafael would drop the third set but eventually prevail in 4, 6-4, 6-4, 4-6, 6-3. In the third round, he'd take on the 27th seed, Senago. And after an easy first couple of sets, the third set was close with some controversies, but Rafael eventually got through 6-1, 6-2, 6-4. In his fourth round match, he'd take on the 21st seed, Van Den Zanshel. And after doing it very easy in the first two sets and a half, in the first two and a half sets, Rafael would eventually prevail in 3, 6-4, 6-2, 7-6, to advance to the quarterfinals. These two guys have played twice before with the head-to-head split at 1-1 with their recent meeting at Indian Wells, with Fritz getting that win in the final. If Fritz is going to win this match, he needs to serve well. He hasn't dropped a set for the entire event. He's the only guy in the quarterfinals who's not dropped a set. So he's going to be full of confidence and with that win against Rafael at Indian Wells, he's going to have to use those tactics and keep his head cool if he's going to beat Rafa in a bigger match. If Rafa's going to win, Rafa just needs to serve well like he did against Van Den Zanshel. Very, very good serving from Rafa, free points, and really has gotten better and better as this tournament has gone on. So he's going to have to be serving his best because Fritz is the hardest opponent he's played so far. This is going to be a fun match to watch because I think Fritz has a legitimate chance of causing an upset, but I'm going to go with Rafa. I think Rafa's going to win this one in 5 sets and get to the semifinals, but let me know down in the comments below. Who do you think is going to win this quarterfinal clash?


Green tea. Green tea. Oh My god So this is going to be one of the most important videos I've done So stick around and I'd love to know your comments afterwards If other people hate you that's obviously, you know, that's part of life, right?  Not everyone can like you and what you do. However, the big challenge lies when you hate yourself Okay, and the theme that always comes up for me is The challenge people have with this concept of being enough Give me three words like I'm not enough I'm not enough and the more I thought about this is I've honestly thought about it throughout the day today and I'm thinking when we have thoughts like that We need to dissect them We need to try to understand them and and put some meaning behind them and challenge those thoughts because to say you're not enough that has some very deep meaning to it Like just those words. I'm not enough.   Enough when do people say enough, you know But when you're getting I don't know getting your wine poured somewhere or have a glass a waiter or a server pour you a drink and Okay, that's enough. You know, that's enough. That's that's enough water. I'll be okay with that much water Okay, that's enough. I don't want to drink too much alcohol or else. I'll be hung over today or the next day When you're when you're frustrated or angry. It's like, okay, I've had enough. That's it I've hit my limit that is all and What happens when people?  So let's get that out of the way Because you can't compare to other people because their concept of enough and their threshold for for pain and and their motivation for success is Completely different from yours completely the difficulty about this whole video is I just said it's completely subjective So I don't know what your enough is. I don't but I want to ask I want you to ask yourself a question If you were enough What would that look like? Ask yourself that if you if you tomorrow you could have anything you wanted and your life would be perfect Would you still wake up and say I'm not enough if you had your dream car your dream job your perfect family Would that be enough at that point because I have a feeling that even if you got all you wanted You'd still have that underlying feeling of I'm not enough and When we want to dig really deep into that what you'll have to do is challenge your own belief system Let's see. Okay. What does enough mean for me if I actually graduate with this degree and I get an awesome job and I'm making a decent impact in the world Is that gonna be enough No, of course, it's not gonna be enough because I'm gonna need to be the CEO of this thing to make a big difference Okay, but no that's not even gonna be enough because you know to make a big difference I need to I need to join this company and do this But no no no that wouldn't even be enough because you know There's all this this policy and this and that and this and that I need to start my own business And I need to change the world that way. Yes, then I'll be enough Okay, okay, but then I want to start a family. Okay, so if I start a family, I'll have a kid Okay, then I'll be enough. I'll have a wife and my child. No, that's not gonna be enough because you know one child I want at least three. Okay, when I have three children and a wife That's gonna be enough and and I'll live in truck. No, I don't want to live in Toronto. That's not good enough Okay, I'm gonna move to California. I want to live in LA. Okay, that'll be enough. Okay, okay Do you see where this is going? No matter what you do It will never be enough So what can we do to challenge that? I want to hit you with a perspective right now And this is the way I think about it. The way you're living right now the way you're existing right now Is enough in itself By chance, it's a miracle that we're all here.   I guess the last thing would be For some homework if you if you all have some free time and want to do a bit of homework, especially if this thought Continues to bother you and And just like a splinter just it won't go away and it's kind of in your head all the time first thing write down some unique things about you Now I'm not saying I like to play basketball a lot of like a lot of people like to play basketball No, right down. Is there something unique? about your shot If you like to paint is there something unique about your painting style? Things like that.  I don't want to hear it. Okay, not not to sound You know not to be angry there, but there's no way you haven't achieved anything I don't mean you need gold ribbons on your wall Trophies from from the Olympics. No, I'm talking about did you pass a test? Did you run 2k? Was that your goal like what if you achieve this can be did you get through the whole like Season four of house of cards or season five whatever it is. I don't know something I know there's a lot in there as far as achievements and the third thing Pick up a hobby Learn something new suck at something for a while and then get better at it That feels really good and then you you put some purpose and meaning into into something and maybe that's what's missing sometimes is You don't feel you're good enough because maybe you haven't stuck with something long enough to really see results Because I know if you're learning an instrument or learning a new skill, you know Whoa, and then you plateau hard and then it's really tough to get into that second stage I completely know that because I've been playing guitar for way too long and I'm not that good so That would be a very interesting thing to write down Write down and and figure something out figure out a hobby Something that you want to learn can be a language an instrument a new sport anything and there's your homework I just want to say you are good enough. It is a miracle that you are here When that thought comes in your head, I'd like you to challenge that Take care guys Here's what would be so cool if everyone just comments, right? And all you say in the comment is I am Enough type that out. It will feel so good because you're telling the truth Okay, you are enough and that's enough


So most of my time at First Richardson so far has been in the development of creating a new space for new faces. We opened our new facility in January of 2016 and since that time we have seen many new faces come through. And the words that I continue to come back to as new faces come in, those doors is trust and truth. And the problem with that is that we often trust people that look like us and act like us. Yet the truth of the gospel is that we believe in the body of Christ and that metaphor and image means that we're not alike. We don't see things the same way and we don't act the same way. And for the body of Christ to be effective and functional, we can't all be alike. And so I continue to feel called to create space for those new faces because that's how we are functional as the body of Christ. Well I didn't grow up in church and I started going to church when I was a senior in high school and into my college years and I went on the invitation of friends just really on their elbows. And I remember all the questions that I had and how I felt at church and really what it is to be new. And so I think about that whenever I think about the congregation I serve and even when I get a phone call from a wife and a mother who says that her husband is an atheist but he's willing to come to church with them and so I think about the questions that he might have and how does it feel to him. And I even think about the young adult who came to me once in a day and said, I decided that it was time to come to church because whenever I became an adult I needed a church and now I'm an adult but I have no idea how this works, I don't know what the Bible is and what should I do. And so I think about those people when I think about new places and new spaces and new faces. I think the primary way I feel that God has prepared me to gather new faces in new spaces is by giving me the privilege of being the pastor of the Feast Community. For the past three years I've served as the pastor for the Feast Community which is a weekly worship service with the special needs community. About three years ago I felt inspired and convicted by the Holy Spirit to start this service and I've seen this idea of new faces and new spaces manifest itself in two ways of the Feast. First is individuals who for whatever reason were unable to attend regular church on Sunday morning now are able to come back into the local church or maybe even come to the church, local church for the first time with their families and friends and worship every week. The second way I've seen new faces be brought into new spaces is that the Feasts were all about empowerment. Individuals with special needs read scripture, pray, lead music, singing, signing, help with communion and offering and in all these ways I'm seeing that new faces are not only being brought into the local church for the first time or back into the local church again but they're being, new faces are being empowered in new ways, in new spaces within our worship service so it's really exciting to see that dynamic occurring. I think for me God has prepared me in two different ways. As I think about preparing new faces for new faces, the two things that I've been taught is to be patient and that if we really are intentional about building new spaces for new faces that we'll be patient enough to really do it right when we start to develop and start to make new spaces. The second thing is never accept failure and to always keep trying. Sometimes it's okay that we don't always get it right the first time but then we learn from that and we do it better the next time but we never stop trying, we never stop trying to change. So growing up I always felt really drawn to different age groups so I remember distinctly in high school I was really drawn to older people in fact I used to go to really cool scrapbooking conventions with people that were like 40 years older than Iowa so I was super cool and I've just always valued people older than I was but as I grew up I always really valued younger people and I was always drawn to student ministry and so I feel like in my lifetime I've always been looking around the table to figure out as everyone represented it and I would like to say that I had always been looking for new faces and I kind of got really content with who I knew who I was comfortable with and I think in the last couple years I have realized my privilege and I've been really challenged by different voices to make sure I am looking for the new faces and really make sure everyone's fully at the table I think we've kind of tricked ourselves thinking that everyone really is welcome and we haven't done a super good job of that and so I feel like God has been really preparing me and molding me to look outside my box, look outside my world into places, into people that maybe I wasn't always comfortable with or didn't feel like I had a lot in common with but realized that they very much need a seat at the table and how together we can do really great things and really start to look like the Kingdom of God Well I think that God has maybe by nature an Includer and so that means in any setting that I'm in I'm kind of always looking to the edges to see who's not there who's missing or who's not participating fully or who's not always kind of being included whether that's in a just a youth group setting or a church setting or in the neighborhood or society I'm kind of always, I'm just geared towards looking at the edges and seeing how God is leading me there I hope that God continues to use me despite myself to work for and to strive for full inclusion of those with special needs and disabilities into the life of the church we're doing really well on some levels but we have a ways to go I just hope that God continues to give me the insight and the courage and the clarity to work for inclusion and also just obedience to follow where God is leading me Well one of the things I love is to help people really discover who God has meant for them to be and that could be through a vision statement or it could be how it's expressed in their careers and really how they live out their faith I think so often that we just live life and we go from one decision to another and think about the boxes we need to check and I love when people really discover the vision that God has and the calling that God has for them and I think about when I do premarital counseling and I talk with the couples and say that your marriage is not just about you being happy but it's about you being a blessing to each other and a blessing to the world and how might you bless other people through that and I was even working with an older couple and they were coming to the end of their retirement and professional years and they were talking about all this extra time that they had and offered up to them well how might you bless other people as you come to the end of your careers you could be a mentor for a generation that's looking for mentors and you have opportunities and extra time to volunteer and I could just see in their eyes how excited they were as they begin to catch a vision for this new phase of their life and for me that's about helping people discover who they're meant to be so I learned really early on in ministry actually in children's ministry that God was not calling me to have all the answers that God was calling me to be faithful and I want that to continue to be lived out in different ways whether it is sitting at the hospital bed or talking to someone who is struggling in their faith or talking to someone who is even given up on church God doesn't call me to have all the answers God has called me to be present and to be faithful that's one of my hopes my other hope is to have a ministry that is about a resilient faith that's the story of resurrection we are all broken and we all will stumble and have those moments in our lives when we feel like everything is coming to an end yet the good news of our gospel in Jesus Christ is that we are called to have a resilient faith to get back up again and that death does not have the last word not in this life or the next I think it's tempting in ministry or in any career to want to be successful and for me it's tempting to want to have everything that I touch grow and be super vital and be the most important thing that's ever happened in that church but I don't know that I'm necessarily called to be successful and called to be faithful so my hope then is by being faithful to that gospel that people's lives will be transformed and that we will begin to realize that this family of God that is present in heaven can be made real on earth and that we can all be part of that no matter our age or race or creed or background or orientation whatever it might be we are all part of this family and meant to do this together I've realized in the last few years as I've been leading a congregation and spending more time with people is that people don't really want super flashy polished ministry or leaders that have it all together I think there's been a hunger not only in the church but just around the world to have leaders that don't separate themselves so much and so what I've realized is I've been able to offer myself as vulnerable and transparent and authentic and I think people really find that refreshing people really love when I share what I'm going through what challenges me what I have a hard time with what I don't understand and inviting them over into my home for dinner or calling them on a Saturday say hey let's get our kids together go on a play date or inviting them over to watch college football on a Saturday I think there's something about being accessible and realizing that as pastors yes we're set apart but how are we really with our people that we're leading and so showing that we are with them and we are for them and that we're grown alongside of them I think has been the biggest success I guess in my ministry and I hope that carries me that I never forget that I need to be with the people and not to be so confident and make sure that I'm not so set apart that I'm not accessible I think for me the way I hope for God to work through me is to help me to be a really great leader and pastor to every church that I go to as we celebrate this year 50 years of the Anatomythus Church that we work together to remain united as the Anatomythus Church and I hope that my hope is that God will continue to work through me as a leader no matter where I go to help maintain that unity