Hello and welcome to the next talk. It will be about Klick. My name is Kupp Pfeiffer. Some of you who know me still think I'm the main developer or spirit behind Klick. That's not true. I was just blocking a lot about it and I helped Simon a little bit with the work. Simon Peter is the main developer of it. So maybe you want to say something. Hello, can you hear me? Yes, great. So how many here have ever heard of Klick before? One. Okay, a bit more than one. Five. Has anyone ever tried it? Two. Okay, great. So it's very important that what we are showing you right now is not what you see on the actual website at the moment. We're showing you the next version Klick 2, which is currently being prepared and there is a SVN for it, but it's not what you see on the website, just to not have any confusions on that. So basically I started Klick in 2004 and everybody laughed at the crazy idea in the beginning. They told us you don't understand what you're doing. And now it has changed a bit, but let's look into it. What's the situation today in packaging? Well, every distribution is its own world, basically. You have all the different distributions, as you know them, and they are all one system each. In fact, applications and the system are melted together. They are all the same. They are managed centrally by the distro. And as you can see, every distribution is its little world, including both the base system and the applications. What's wrong with that? Well, nothing, as long as you stay in your own world, this model works very well if you use what comes with your distribution. But there are some complications and I want to just mention a few of them. What if you want to test a latest bleeding edge version of some software that does not come with your distribution? And you also don't want to risk to break your system, of course. What do you do? Well, usually you go to some download page and if you're lucky you will find packages for your system that you're running. But in this case I do see three distributions, but mine doesn't happen to be among them. So what do I do now? Two, now maybe I have found this application. I have installed it on my system and now I decide I want to try out a new distribution, want to try out a new system. What do I do with the applications? Well, basically I have to download everything again, do it all over again. Having a business background, I think time is really money and a simple switch of your base system shouldn't require you to re-download all the software, to search everything again and install it again. So a distro switch shouldn't really require you to get all the applications again. Imagine a world where you download some music files of the NetMP3 files and as soon as you download them and as soon you start using them, they get melted into the system and are becoming part of the system. Clearly no one wants that. A music file just runs on top of the system and you can move it around as you like and I believe software should be the same. Maybe you want to use OpenOffice, the stable version, but you see this great next version upcoming and you want to give it a try. Without risking that something breaks. You want to run both in parallel. Well, if I want to do that currently, I probably have to ask an expert. What does he tell me? Something like this, which I, being a rather non-technical person, don't necessarily understand, but I sure can type it and look what happens and usually it looks like this. Some obscure errors doesn't work for me most of the time. Or maybe you want to use an application on a USB thumb drive. As a matter of fact, I'm running around with lots of these. Everyone of these has a different distribution on it and I want to just put some add-on software to the thumb drive. Currently, not so easy. Well, Windows can do it with some help. It's called portable applications and it's getting quite an uptake at the moment. If we look at macOS, it can do it out of the box most of the time. And Linux, good luck. Or, this is the classic problem. What do I do if I want to move an application to the trash? Uninstall it. What do I do? No, I mean completely. Including all the sillions of dependencies and libraries and other stuff that got installed together with it. And we'll do questions in just a few minutes. Well, if you did not use what was part of your distribution, if you went outside of the package management of your distribution and you installed just some random stuff off the net, you're pretty much out of luck at this point. And you can never know where the stuff went and how to get rid of it, at least if you're not a very technical person. Okay, so maybe this approach here where the distribution contains both the base system and the application in one block is maybe not the greatest model of all times, at least not for all users and for all users. So, here's a suggestion we would like to make. We really think it should look like this. You have different base systems and the applications run on top of those. The base system, the distribution being centrally managed by whatever tools the distribution provides. This is basic libraries, stuff that the end user typically doesn't care about as long as it runs. And it should be managed just like it is managed now by the distribution. On top of that comes the end user software. And we think the most important aspect of this is the clear separation between the two. So, you have the base system, but on top of that you have the end user applications which should be even easier to manage by the user himself. And the users should also be able to manually do something with these apps. So, this is really the critical part of what click really is in essence. It's all about the very clear separation between the base system, which we don't touch, which comes with your distro, and the applications we put on top of it using click. We call this application virtualization. Maybe you're familiar with other virtualization approaches. Usually an entire operating system is virtualized. This is not what we are doing. We just virtualize the file system of one single application and we can virtually run it at native speeds. So, there is no large downside to this. Well, a traditional package, if I install an application, looks somewhat like this. It puts files all over the place. As a matter of fact, package managers were invented because no one could track these anymore. I don't know where the stuff ends up. By the way, something similar is known as DLL hell to Windows users. Click does it very differently. We have the base system, the platform, and we just put in one single file per application. One red dot contains all this application needs to run. So, this is really the most central aspect of this talk and of click. Please, if you want to remember just one thing, this is the thing to remember. One application equals one file. This is what we are all about. By now, you probably ask yourself, what are they doing about the dependencies? Well, the dependencies are either part of the base system, that is, they come already with your distribution, or they must become part of that one file that we create. So, I think we have some lag in the animations. Now, maybe it helps to restart OpenOffice. This is a bug we discovered while working with all these animations. Somehow, you need to restart it. Okay, once again, so everything that's needed to run the application is either already there or we put it into that single file. Let's hope that we can recover here. Here we are. So, the dependencies. This scheme has some advantages. I want to go very quickly through these. First, obviously, one file, one application, is a very simple concept. Even new users can understand it immediately. Very simple. Second, when I have an application in this one file form, I can easily take it and put it on another distribution. It still runs. So, no re-downloading of the same stuff over and over again if you're using more than one distro. Third, multiple versions of applications in parallel. It's absolutely no problem to have five different versions of the same program running without requiring the user to do anything special. You can also take the one file, put it on a USB thumb drive, and it just happily runs from there. So, no need to copy it over and copy it back or something like this. Just run it right from the USB thumb drive. And finally, if you want to get rid of the application, you simply take the one file and put it into the trash, and it's all gone. I hope nobody uses trash. There are some more. You can't mess up the base system since we don't touch it. The scheme actually saves disk space. This is the question that comes up all the time. Isn't this adding to file sizes in an insane way? No, it is not. Since we are using a compressed file format, and this oftentimes offset the additional libraries and stuff that we have to use. To give you one concrete example, if we take OpenOffice, it's about 250 plus MB if you install it regularly, and if you do it with click, it comes down to 120 or 130 or so. So, no, it's not a waste of disk space. Of course, such a scheme also lowers the cost for independent software vendors who now have to produce just one package instead of multiple packages for all the distros out there. This is a cool one. You can also run applications in a jail. That means that everything the applications tries to write into your system gets jailed and gets redirected so you can take the settings along with the application. So I can't just put Firefox on my USB drive, but I can also take all the bookmarks and settings and everything with me. And finally, this is perhaps the most important one, no root writes required. And there are some more. You can figure them out if you try click. So, maybe we do a short demonstration. So, we type in here, click, and we take late three as a sample application, just press the run button, and now we clicked a bit too fast. Okay, do it once again. So, click, play three, press run. I now get some information including the download size and if I want a description and other details, I can look at what goes into this package. But for now I think I just leave it there and I just press OK. Now it's downloading. And boom, the application runs. It's really that simple. Now notice, okay, we are quitting it now. It asks for some feedback. Since we are providing packages for so many different distributions and systems, we are interested in where it runs. So, after running an app, you get a feedback dialogue. Notice this new icon on your desktop. It is not just an application launcher icon, but in fact it contains everything. It's the single file we talked about. In this case, 2.1 megabytes, so not too large. Now notice what did not happen. I did not add any repositories. I did not edit any cryptic config files or such. I did not need root writes. I did not have to enter any password. And I did not change my base system in any way. Implementation. Let's talk about how this stuff works. The single file you just saw is basically a standard ISO file like you use it for your CD images and such. And it contains in a compressed form everything the application needs. That's not part of the base system. This one file, you don't download it from the web as a complete file. No, instead, it's created locally on your machine using what we call a recipe file. This is a simple XML file plus some binary ingredients which can be Debian files or RPM files or any package binaries that are already out there, already existing. And what the click client then does, it takes the recipe, it takes the ingredients and it cooks up this red file on your machine. Now, such a recipe, what does it do? What does it say? Go to the Skype website, look up what's the most recent version of Skype, take it, download it and make this single file out of it. This is the clear text of a recipe. Not using pre-produced files has a lot of advantages. For example, we can use commercial applications that are not easily redistributed. We can just use whatever binaries are already provided by the company themselves. We don't redistribute anything, basically. Also, we can use the existing mirror infrastructure. We don't need special download servers for click. Instead, we use the packages and the mirrors that are already working and are already out there. This also allows for instant updates. Whenever Skype updates their homepage with a new version, it's there instantly. Also, we believe using this scheme increases trust because you can exactly see where your binaries are coming from and that they are coming from the original author, a company that may be trust or an open source project you trust. We developed this XML format together with zero install and we share the basic structure of this file so that in the future we can easily cooperate with the two projects and create either what zero installed us or what I just explained, the single file. And you can also do it. Here is an example. This is the XML of a recipe file. And as a matter of fact, you have just to fill in some very basic information such as name of the application, a little summary, the download URL, and you're basically done. Here we have done it for you. And of course, you can add to that recipe. For example, we can have a digital signature and some other things. Let's do a quick real-time demonstration. So here I want to package a little game called Xphere. All information I need is basically the name of the application plus the URL of some binary package that already exists. In this case, I want to use a binary package that's already on my disk. And here I have a blank minimal recipe. Now I will just insert the missing information, so the name of the application goes here. We can add some little description. It goes here. And I take this URL. In this case, it's just one file, but of course, if it's a more complex application, you could have more than one file. I have now saved this, and I will call click and give it the path that we have here for STEM recipe XML. And it asks me whether I want to download, in this case, copy it over and run this recipe. Of course, the description is empty, but if we look into the ingredients here, we can see the path I just entered. Now, let's run this, and here we go. On the fly, the click client converted the stab file that I put into the single file. And as you can see, it's really easy to do your own recipe files. Anyone knows how to defeat XFIL? We don't have the time to play the game right now, but he's giving some feedback now so that we know it worked on Ubuntu. If we have a good network connection, it might work, but we don't wait for this. Let's go back to the presentation. So, who writes all these thousands and thousands of recipes if we want to provide a reasonable broad range of open-source software? We don't have the time to do it, so we use something that already exists, apt-get, but we use it in a different way. We don't use it on your local machine. We use it on the server, and the server calculates all the dependencies and writes these little recipes. Here is an example, KDE SVN, a bit more complicated. All the dependency resolving is done server-side, so without even touching the recipe manually, we get a working recipe that's calculated to a common denominator of what we expect to be part of every system on the desktop out there. So, once again, recipe plus ingredients make the one file, the compressed application image. And this compressed application image actually looks like the standard Unix file system structure. We don't want to reinvent the wheel. We are using the structure that's already there. We just apply it on a different abstraction layer, a different level, that is not per system, but per application.  It's being mounted. The image is being mounted transparently over the base system so that the application sees the base system plus everything that's contained in this single file. And by the way, we do this on a per application level, so if you have two applications installed by click, they don't see each other. Only what is contained within this image sees its image, so they can't interfere with each other. Fuse does this for us. Fuse stands for file system in the user space, and it allows us to mount these application images without needing root rights. First of all, we mount this ISO in user land, then we also mirror the entire base system into the same mount point. Finally, we overlay what's contained in the image again to the same mount point, and then we switch there with a fake change root so that to the application, the result looks like a system that not only has the base system but also everything that was part of the one file image. So, how portable is this? We're using Fuse, and Fuse is really available for most Unix-like systems. We currently only implemented click for Linux, but it's well possible that someone comes up and says, hey, I want to have it on one of these, so it should be possible. There are also some user space programs and kernel modules involved, but since I'm not talking about Fuse, I don't want to go into the detail there. Next, we use a tool called fake change root, and this really is a user land change root implementation that makes it possible using LD preload for the application to see the entire system as a root file system when in fact it's not, when in fact it's mounted somewhere under temp something, but we do a switch there, and so the application thinks that's the main root file system. We do not emulate some special files such as DEF and so on for security reasons. We can also rewrite pairs, right, that I already explained, no, we can also rewrite pairs for writing so that as soon as an application wants to write somewhere, we redirect the write so that we can put it somewhere else, and this is actually cool, I want to show a demo. Quotes. What do we have here? So, here is our application, I just started it, a new file system that's mounted, Fuse ISO, it's now mounted, and as soon as Quote closes the application again, the file system disappears. So, on the fly, real-time mounting, here we go, it's mounted again, we close the game and the file system is gone. Yeah, something is still missing for a full application virtualization. We have the base system, the read-only stuff, but now we want to do something about the user data, the read-write stuff, and that's a writeable layer. We put it on top, and this re-writeable layer takes anything the application wants to write and redirects it to a directory called app-data, in this case. Fusion ISO does it for us. Again, this is the same procedure as before. I don't have to go through everything again, but the critical part is that now we mount a second layer, read-write, which then redirects all the writes. It's based on Fuse ISO. We added some functionality to it. I don't want to go too much into the detail here. Instead, I think we have another demonstration. Now, right, if I now launch an application, I can choose whether I want no-chale at all, that's what we showed before, whether I want to redirect the writes to the entire system, to the home directory, or just to the configuration files. A little demo here. Here I have an application, leafpad, and I create a folder that has the exact same name as the application, but ends in .data. Now, when I launch this application, I can type something in, oh, here. The application started in .chale. This just shows me that writes are redirected now. We put some text in, and now try to save it to, let's say, the root directory. And remember, we are not root. We are just a regular user, so we normally couldn't write there. So it's now saved. Let's close it, and actually the file went to this directory. It's not in the root directory, but in our directory here. So we open the application again, go to Open, and sure enough, there it is, in the root directory. Here's our file. So, a lot of people ask about desktop menu integration. We didn't do that in click version one, but the upcoming click two will register downloaded files with your desktop so that they appear in the desktop menus if you wish so. Here's a component called clickD, which is a little demon, very low overhead that runs in the background and checks if you add some CMG files, some compressed applications, and if they are there, the menu gets updated. It uses these standard desktop files and integrates the application into the desktop. What about command line applications? Well, they work right as you expect them to work. As a matter of fact, you can take this application image, rename it, and put it into somewhere on path, user, local, bin, for example, and then you can just launch the application as you're expecting it, and you don't even notice that, in fact, it's working in a totally different way. Here are some challenges. Problem. Which binaries should we take that run everywhere? This is really a tough question since if you take a binary that was compiled on a new operating system and you want to run that on an older operating system, usually it doesn't work. So what we really would like to have is back ports, recent software compiled on old systems, because these binaries would be ideally portable across all the different distros out there, even if they are not the most recent ones. Another problem. If you try out Plik, you will notice most apps will work as expected, but some won't. And this is simply because most recipes are automatically generated, which usually works quite well, but not in every instance. So if you encounter that, you're welcome to fix the recipe. It's usually just one line, what you have to adjust and then it should run. Another problem. I hope it's not a problem anymore. We made quite some progress on this one today, together with the guys from the OpenSUSE Build Service. We are working on providing nice packages for all the commonly used distributions so that it's really easy to get the client itself running, which you need not only to get your files, but also to run them. Of course, this project is not just ours. We took a lot of inspiration, a lot of ideas and code, from a lot of projects and people, and we want to thank some of them. It starts by Apple, who first, at least to my knowledge, puts software in disk images. It goes through ISO. Knoppix was a very important inspiration. They were the first one who made it popular to run an entire system of an ISO. We now take this to the application level. There are some others. Probably most of you will recognize them. So it's not really our invention. We just took a lot of good ideas that were already out there. And with this, we would like to invite you to get involved in the project. This is a great team effort. We have various people working on different aspects, but some spots are still open. So we are looking for someone to create a nice native KDE frontend, for example, or RPM packages. We made some progress on this today, but if someone thinks he can produce great RPMs, please come and see us. Also, of course, we need lots of recipe, writers, and quality control. So if you want to join the project, you're welcome to do so. With this, we are now at the Q&A session, and I think there was one question up front here. Long time ago, Mike is coming. Hello. Okay. Basically, what you're proposing is a glorified version of static linking. Static linking and dynamic linking is a debate we've been having for decades. What you've also got is it's great on your machine there, but if you take, say, an LPC that's got a little bit of RAM, a little bit of disk space, not an awful lot else, you can't really afford to have 600 copies of G-Lib and GTK that you would have if you installed, say, some of the known stuff. You're also running to the problem of if you don't have all the memory there, because you're going to end up with 20 copies of GTK loaded. And then you've also got the great problem of what happens when I take it out of my 32-bit laptop and plug it into an ARM machine or a SunSpark or something. Okay, so this is three questions, really. The first one was about how does it relate to static old linking? That's not what we are doing. It's compiled in the standard way using shared libraries. All we do is we bundle those into one file that is mounted and as soon as it is mounted it behaves just like regularly installed libraries. So it does not mean that you have to link everything in a static way. But you then get all the downsides of static linking and dynamic linking. I've got Firefox and Mozilla. Both of them seem to depend on libnss, I think it is. So I don't have to have two copies. This is true, and it relates somewhat to your second question, which libraries end up in the compressed files. Is it really GTK over and over again? And that's not the case. We do not include any basic system libraries that are shared by a lot of applications. We just include those libraries that typically just one application or a few applications need. So GTK we would expect to be present in the base system. Not every machine has GTK on it. That's correct. Then you cannot run GTK applications unless you use your distros package manager to install first GTK and then click the application. But click will tell you what to do. So you've got the same dependency hell as before? No. We take it one abstraction level higher. We do not check dependencies on a individual file or on a package level. Instead we check it on a framework level. So we ask ourselves, do we have GNOME? Do we have KDE? Do we have MANO? But on this aggregated level. Questions? And the last one of portability between platforms. Great point. Since as you saw, we thought about these issues. We haven't implemented anything like it yet. But principally you could do two things. You could create specific images for every operating system. But that would not be so nice, of course. You can also put all the different architectures and operating system binaries into the same ISO. And this would then somewhat be similar to a Fed binary known from Apple. And we can do that. It's not implemented yet, but we think clearly in this direction. Okay, you can think about click also as a tool in your hands where you can build your own portable applications and bundle in it what you want. Like, you remember now the one application one file thing. What I've done is five applications into one file as well. Just click will have something where you can run it with a prompt and it asks you which one of the ones which are included will... Do you want to run? Like, for instance, if you want to package K-office but have access to the individual applications or similar things. There was a question. Well, I believe if I have one application like him or something and I change a photo. Then it's in the overlay of him, right? So if you have... Like local data, the application data which are in the right well portion of the image. Like I say, I'm going to use him. Then they are saved in the image. So they're not visible from other applications. Is that right? The application that runs from this image will see everything that's already in the base system. So if you have a GIMP version already locally installed and now add another version using click it will overlay. So if the same version exists in the ISO, it will take this. If it doesn't exist, it takes what is in the base system. If I want to use one file from two different programs I should make sure the file is in the base system and not in the application data. That's true. That would be ideal but usually we, as I said we follow the one app, one file approach. So there you just have to make sure that in writing your recipe you assume the right things to be on every distribution and this is a lot of magic actually. We are following roughly the LSB for that and we get on frameworks such as Mano which just require them to be installed in case you want to do a Mano application. Another question. I once used click one the first version and it worked fine for me. So why did you come up with a second version? What was the reason? Sorry, I didn't get the question. What was the reason for a second version? Oh, okay. Click one was basically a proof of concept. What we did in click one was we did not overlay another layer. We just took the binaries and patched any hard-coded paths they had so that they could run from any location. This worked in most times but it did not work in others and so this is a much, much cleaner implementation. Next question. You talked about optimization because of compressed ISO so you don't use that much HDD space. But what about the overhead of decompressing all those images and eventually writing back to it? That's CPU overhead. So you're interested in the overhead we produce? Yeah, basically. Because HDD space is cheaper and cheaper nowadays and sometimes it's better with life, basically. Well, we haven't done really scientific testing on the overhead we are producing but from day-to-day usage it seems that the overhead is not noticeable in the real world. One more thing what you ask the differences between click one and click two you can read a lot of details in the interview the POSTIM organizers did with us and published on the website where we go into the differences between click one and click two. Okay, any more? Something that is really a problem on macOS X by example, the click system is really based on the same principles is package management and software updates using a normal central packaging system you update your whole system and the thing I think really awful on the mac is you have to update every package manually how do you think click could solve this problem because it's also security related So automatic updates work best for the applications you just be updated for stuff in the base system core libraries and so on but I'm not so sure whether the user actually wants automatic updates of Firefox or OpenOffice most of the time the user wants first to check out whether the new version really does what was expected and that's why in click we want the user in charge of the add-on applications that being said it would be possible to create a updater application that checks with the web server, the click server which application is updated and then would automatically download it that would be possible, we haven't implemented it yet because we think it's so simple just one file that you manually can manage that you don't really need a full-fledged package system, but it would be possible here you have said that the ESL LD preload to create your user level change route but LD preload is famous because it's easily circumventable because it's just an environment variable I think this does not protect your user from malicious software we didn't say it's circumventable we didn't say it is not circumventable so yes, if you are using a package you could package something which does evil to your system but that you can do with RPM or depth as well on the other side you use fuse in the kernel which is not really user level because you need to add the possibility to use the device changes the real mount table of the machine trying to use click in a multi-user environment where tens of users try to install by click their application you end up with the mount table with hundreds of items I think there are more modern techniques like system call system call capturing like VOS or like use of Linux so you can take the system call that access the file system and you can create a virtual mount and that's and a virtual, the same you can do for CH route in such a way is this not circumventable because you don't the kernel we've designed it in a modular way so that if you have a concrete idea on how to do that we should talk and we would then implement it we would just exchange this change route environment by what you propose okay, no question about code here so you could probably install and use the whole thing in a virtual environment with no machine, right? with no machine no machine? he knows so my good question is so why don't we give every pupil out there his own no machine instance and teach them how to use click we don't have all time of the world so we have to do something but if you want to tackle that you are invited to help us I would definitely try to tackle that so I had any teachers in here who would go for a whole instance for every pupil here at school any teachers here? no, wrong conference I'm sorry, but I try okay so thank you very much for coming, we are still here if you want to discuss some more about click we'll be outside thank you


Good day, fellow investors. I read many comments about stock market crashes and how you're waiting for a stock market crash. I thank you for the comments and leave always a comment. I'm always happy to read it, but I might not disagree on the waiting for a stock market crash because I think that over the very long term it doesn't maximize your investment returns. And in this video I'm going to explain why I think so and why a strategy of being a little bit more aggressive, not waiting, does not timing the market, but having time in the market I believe will lead to higher long-term investing returns. Let's start. So I don't like timing the market because you are timing the market and you are assuming that you can forecast where will stock prices go, that you can forecast what will the economy do and that you can forecast what the Fed will do with interest rates and everything that comes along with that. Warren Buffett always says I can't do it, I cannot forecast what will happen with economy, what will happen with the Fed, what will happen with stock prices, so why would we think we could do it? So that's one. And then timing the market has also proven in the past not as a good strategy because you never know what will happen, what will happen next, which leads to speculation, greed, trying to outperform not on investing but on speculating, which is a very very tough thing to do. If we just look at the drawdowns of the SAP 500 over the last 45-49 years you can see that okay there is always volatility but there are only a few really really deep drawdowns. So intra-year drawdown wasn't 34% in 1987, 20% in the 1990s but then a lot of just small, small declines up to 11%, then two big down declines in the 2000s, the dot-com bubble, then a huge decline for the great financial crash and then the last one was 20% recently but you can see that it's very difficult to pick okay when am I going to buy. If we look at from this perspective many that were expecting bigger crashes 20, 30, 40, 50% as we have seen in 2009, 2001 they missed out on huge opportunities to buy and they missed out on huge opportunities to get the amazing returns that many of us got over the last 9, 10 years. Now I am relatively fully invested now, I have been little invested at the beginning of the year because I did great in 2018, the biggest, largest position I had got acquired so that was the only reason I also made the video why I had a lot of cash then I wanted to finish my research, go on with my research and now I'm pretty well positioned in my portfolio. If you check my portfolio that I started in May 2018 where I started with 10,000 I add 1,000 monthly I'm not now a few thousands up on something of about 25,000 invested so that's very very good and that's the key that shows okay even if the markets are expensive you can always find the value here and there that will give you good investing returns and I'm going to further argue that's better to be invested because let's say that you make 15% for three years your total cumulative return after three years is 52% even if there is a decline of 40% yes you are down to down 9% from your initial perspective but add a few dividends add something and you will break even but as we have seen in the drawdowns 40% declines are really really rare and if you don't invest if you're waiting for those you might miss on much much bigger opportunities if you do 15% over seven years then whatever crash might happen whatever might happen it doesn't affect you because whatever happens you are still positive and then again if we look at the drawdowns of the SAP 500 over the very long term you can see those declines those dips as very very small points in time so it again involves huge timing skills that very few have to buy really really those dips and then again something to help you okay Sven if you are saying that we can't tide the market what we can do it's very simple you invest based on the return from the business when you're happy with the return from the business that's it I'm currently researching REITs here is just the initial table of what I'm doing and this is just approximate measures to see where to look deeper but a lot of REITs in this case healthcare REITs offer returns between 7 and 12% over the long term per year when you add the dividend when you add the growth when you add everything what they are doing we are talking high single digits low double digit returns over the very long term and now if you have a portfolio we can time the market we don't know what will happen when in interest rates but what we can do is okay this REIT is very stable a quality REIT 8 quality healthcare REIT great real estate great tenants great tenants coverage low debt with tenants low debt with the REIT and it's giving me 8% when I add the dividend and the growth and you say I'm very happy with 8% getting from my investment returns over the very long term then you say at this moment in time I'm buying this next quarter next year something else might be cheap this might not be cheap anymore then you buy that something else and that's also my focus I try to focus on as many stocks that I can cover from various sectors and each month when I add a thousand to my portfolio that I allow to compound over the long term I try to buy what is now the cheapest and what gives me a satisfactory expected return in the double digits that's what I focus on so that's my focus and that's something you can also do and the only the only reason when you don't invest is when you have nothing to invest because you can't find the individual investments that are worthy so Warren Buffett has his 100 billion in cash but he has that cash because he couldn't find the big elephant to shoot and he is waiting he does the 10 billion Occidental or Anadarko deal or things like that buys Apple they bought Apple because not because the stock could go up or down they bought Apple because they were happy with at initial 12% that got later to 8% as the stock increased but they were happy with that return so if you focus on the returns and not on what the market can do yes as we have seen a drawdown can always hit you but over the very long term your portfolio will compound compound compound so that any drawdown or stock market crash will not be significant over the very long term so if you want to maximize your long-term investment returns subscribe to this channel of course thank you but if you want to maximize start buying businesses look at the business yield over the long term buy that business when you are happy with their return from the business not from the stock don't be greedy don't try to time the market just take advantage of what the businesses are doing reinvest the dividend if there is a crash check my stock market crash video because you will understand that if there is a crash your long-term returns will be even higher thank you for watching looking forward to your comments and I'll see you in the next video


Welcome to day three of the DHIS2 Digital Annual Conference. Today we kick off with a plenary session on DHIS2 and the Health Information Ecosystem, where we look at how DHIS2 fits into the larger ecosystem of digital health platforms, and we'll also discuss issues of system integration and interoperability. After the plenary, we'll start our parallel sessions that look at interoperability and the use of DHIS2 in key health areas, as well as sessions on LMIS use cases and DHIS2 as a data warehouse, HIV and non-communicable diseases. We'll also have an extended session on DHIS2 for education, updates from ongoing deployments of DHIS2 to support inclusive and equitable education for all. And we also have a selection of parallel technical sessions and expert lounges today, including integrating tracker and aggregate data, DHIS2 extensibility, predictors, program rules and LMIS. You can join the experts lounges and networking sessions on gather. Remember, you can find all the info on the sessions on our SCED page and read about the presentations on the community of practice. We look forward to seeing you at day three of the conference.


I shut down completely before a fight. Clear my mind completely. I don't think about anything. I don't think about the opponent. I just think about what the mission is and the goal, and the goal is to win. It's not a physical meaning to anybody like a belt. It's, you know, that emotional standpoint of saying, I'm better than that guy. You know, I'm better than that fighter. If you think about it, you got M-O-S's. From Rangers, SF, to tankers, to artillery, to military police. You know, we're all going against each other. You know, who's the baddest man or woman out there. Finish her! Finish her! It's okay! It's okay! Everybody knows when they come in here that this is a competition. And it's not football. It's not hockey. This is actual fighting. And it takes a lot out of you. BFC Dennis, in his fight, the opponent was punching him in the ribs. They didn't look like they were doing any damage at all. Dennis went to slap him in the face twice in a row and the ref called that a tap. There's nothing you can say to a fighter right then and there when a call like that happens. You can't condone them. You can't do anything. No matter what you say, they're just kind of shutting you out and they have all the reason in the world to complain about it, but there's nothing we can do with it. It breaks my heart. It honestly does. It just tore me up. I could have gone way beyond this tournament. My coach told me before that I was going to take top six and that I could make number one a match that lasted no longer than a minute. It definitely sucks when I put everything into this. It definitely feels a little awkward because I know that I should be here and not just fighting for third or second and live for number one. It's a little hard to look at the belts and the medals but I'm still excited for the other guys that are fighting but it still kills me to be on the outside with them. Find yourself, look, find it, take them down. 16 shifts that are going to go through. As soon as you take them down, you're in guard. You're in their guard. You have punches now. Punch a few times, posture. Punch them to keep them down. Break guard, pass, get inside control. Keep breath, keep breath. And let it out slowly. Right? We've been here before. How many times have we been here? Twice? What do we get? First place. What do we get all our top six weeks? From last year and to actually get first this year means a lot. Just the hard work pays off.  It just wasn't conditioned enough. Can't win them all. You have to leave it out there on the mat and they learn that. They learn that there's nothing that you can do after. It's all what you take out and put out on the mat. It's a learning process. It takes time. It takes devotion to the sports. Superman got beat one time.


We got a bunch of great kids, they're grinders. They work hard every day. We don't got great numbers, but like I say, they're great kids. They come to the weight room every day. We struggle in a couple of games, but we've got four wins now, and things are starting to click. And they're in and watching some video right now. And I think they're starting to feel a little bit of confidence about themselves. I have two wins in the district right now, and we're getting ready to really get challenged here this week. Leslie County, they're ranked in all the polls. If you look at the AP poll and the Cantrell ratings, they're in the top 10. So we've got our work cut out this week going to Leslie County. And then the next week, Allen Central, they're ranked and everybody's talking about them. But our focus today is on Leslie County in this week. But last year we started out a district play, one in, I think we beat East Ridge and lost to Leslie County and Shelby Valley. But this year we're starting out 2-0 in the district and going this Friday, going up to Hyde and playing Leslie County. So it'll be tough, but I think we'll do OK.


You may have caught golf fever this past weekend watching Brooks Kepka win the US Open for the second straight year. It's been almost a decade since the 2009 PGA championship came to Hazeltine the last time an event was held in Minnesota. But today rumors finally turned into reality and the PGA Tour is coming back. Today the PGA Tour announced that next year begins a seven-year agreement for TPC Twin Cities to host the 3M Open. While the dates of the tournaments have not yet been announced, you can expect it to be either in July or in June. The last time the PGA Tour made regular stops in Minnesota 49 years ago, making the work needed to bring the tour back all the more worth it. You felt like giving up, but the place deserves it. Minnesota deserves it, 3M deserves it. The course has hosted a senior tour event for the past 25 years, but some changes will be needed to bring the course up to PGA Tour standards, starting off with tightening the fairways and lengthening the course. It's a very good course, but when you take it to the PGA Tour level, the competitiveness needs to go up. The dates will be finalized in the coming weeks when the PGA Tour announces their full 2019 schedule. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. And welcome back once again to theCUBE. We are here live and open in this open source conference, Red Hat Summit 2018, here in Moscone Center in San Francisco. My name's John Troyer. We are coming to the close to the end of the day three of Red Hat Summit. Catching all the live coverage on thecube.net. Great to have with us our two guests here from UPS. Innovation Award winners here at the show. Gentlemen welcome. So Mark Falto and Dan Severi. So welcome folks. So we're going to talk about your journey to using OpenShift, how you guys picked it, what you guys stood up. And as we were just kind of, I saw you on stage, I saw the on stage story. And as I was just talking to you now before we went live, I'm just so impressed by the time to market, time to value that you guys were able to achieve you and your teams. Which if you think about it is really, the fact that this is a real story and it's not just a marketing example, right? It's really great. We're living, and sometimes I wake up and I say we're living in wonderful times in 2018. But so Dan kind of set the stage for us.  You're one of the folks that helped bring the system in. You were already Red Hat Linux users. But like what were you looking at as you were trying to make this decision and what were some of the drivers to bring OpenShift in-house? Well we knew we wanted to go cloud. But we weren't sure whether it was public or private. So we felt that in order to start to transformation to cloud, we should really focus on private. These boundaries to get that up and running. And a way to get, modernize our applications to be cloud ready. So that was the goal when we set this up. We had a very tight timeline. We had applications that wanted to go cloud. So we made the decision. Management was knocking at the door? Management was knocking at the door, right? So it was a matter of just, what do we want to do? So like anything, we viewed a number of different private cloud solutions. And we really liked OpenShift because of its flexibility, its open source capabilities and the fact that it was quite a stock of containers which was our container strategy going forward that we wanted to use. Was this the beginning of your container strategy? Had you been using them before? No, we haven't been using them before. We just made the decision prior to making the cloud decision that we wanted to go containers and dock with the containers we wanted to use. Right. So you do some sort of evaluation. You say, this seems like something worth happening. In the olden days, we'd go off and you'd do some sort of POC and you'd spend a couple months doing that and then you'd look at it and what are we, toy projects? You guys went into action. So can you talk a little bit about that in the timeline there? All right, so we made the decision in late fall 2016 to do this. My team runs all the infrastructure architectures so we work with the applications to design new architectures for them and basically we started working with Red Hat on success criteria that we established for the product and then once we got through that, we had started having really sessions with Red Hat and using a collaborative DevOps approach with everybody in your organization who'd be affected by this private cloud we're putting in. So Mark, our InfoSec folks, our networking folks, we were on a very tight timeline. We had an application wanting to go quickly as possible and they wanted to be up and running in like the late spring, early summer timeframe. So it didn't give us much time. So a lot of work and effort into figuring out how we wanted to architect OpenShift for not only to be operationally successful for us but from an application perspective. So it was important that we do this in a collaborative manner and get everybody's input in doing that. Yeah, that's something that's going to be interesting to dip into, right? Because the speed that you can't just turn on speed like that. As I've been kind of jokingly referring to, right? You have to turn into kind of a DevOps and an agile organization even at the infrastructure layer. So Mark, so you know, within a few months you've got OpenShift up and running. Now you got to put some apps on it. These are net new apps. You have all your existing portfolios still having to run. But so, yeah, what were you looking at putting up there and kind of how did you approach that in terms of cloud native practice? Our strategy was to take net new applications. We were trying to find app teams that we thought had at least a sophisticated enough process that they could take on the automation that we really wanted to drive with the platform as well, right? It was not just containerization but the transformation in dev process that came with that, right? So it's get a pipeline in place, understand how to use Jenkins, the plugins that are necessary to make that happen. So you need the right app teams that are ready to take that on. So we had an example application as part of our Edge initiative called Cyp, which that team that we thought was ready to take this on and it was the only way we were really gonna meet their timelines too. So we worked with them for a number of weeks and not just us but we also had Red Hat partners helping us too to really build out the automation for them, pipelines, get everything, an example running for their complete automated pipeline. Right and so this kind of, this guy can you describe a little bit what it does is a little bit of a, it's a business line app to help managers do some decision making and some planning. Yeah, it's a decision assistance application for supervisors at hub facilities where we move packages. Okay, so real business impact before they had, I don't know what they were, either papers or there. Mostly it was manual processes and it wasn't like the speed to market. It was, the information wasn't real time. So Cyp was all about driving real time decisions in the field. Right, so must have had an immediate impact then. So it sounds like you were up and then also within a few months. Yes, yeah, yeah. We can, I mean we were able to get at least a pipeline going within weeks for them and that demonstrates the capacity to get yourself to production, right? And then they're in production within a number of months after that, a couple of months after that. That's, yeah, that's great. And I'm assuming you'd be able to revise it and kind of improve the functionality sense and that in some other apps. Was that a big shift for you and your developers to kind of get to this stance of frequent releases and a pipeline? Yeah, yeah, it's a huge process shift. It's a cultural shift for app teams. They have to, they have more capability from the infrastructure than they've ever had before. So they now have tools to deliver much faster than they're used to. So they change their team structures to help us facilitate that. They bring in Red Hat or other consultants to help them backfill their skill sets. So it's a big transformation, yeah. Nice, nice. Now I wanted to explore a little bit. One word you hear a lot here, hybrid cloud, multi-cloud, you've been hearing that. We've been hearing that a lot this week. This particular app runs on-prem. Right? Don't talk about this. Yeah, and let's make sure we get right. On-premises. On-premises, right? It runs between two days of dissenters. I get extra bonus points for that. But as a portfolio that you have to manage your IT department and infrastructure, UPS does take advantage of different clouds and different code running in different places as well as SaaS and everything else, I'm sure. Can you talk a little bit about the portfolio? Sure, so we have both, we have a wide variety of, as companies launch UPS, you can imagine we have a lot of IT solutions. So we leverage all of them to our benefits. So we have past solutions in the cloud, a lot of analytics stuff we'll do out there. And we also have a lot of SaaS solutions that we use to do different various works across our organization. So we are using cloud in multiple ways. Our next journey is hybrid cloud. How do we do that? How do we take open shift now? Because what we have is a situation where we need a lot of processing power for what we call our peak season, Christmas of course, right? So, but when we size today on on-prem, we size for that peak season. So the challenge for us now is how can we use on-prem for say nine months out of the year, then expand into the cloud for peak season, reduce costs and then drop that environment down after we're done with peak season to really drive us really efficiently from a cost perspective. Right, right, right. And obviously, open shift is going to be a probably key element to that. It is a key element.  And do you really, it seems like this was kind of a corner turn for your engineering organization.  I would say so, both from an infrastructure perspective, the biggest thing when you run a common environment, which we do in open shift in other common environments, you have no control over how the applications affect one another. With, for us, what we like about open shift, it gives us that capability. So application A doesn't step on application B. And I think for us, it just made our lives a lot easier. And from an operational perspective for that. Right, it wasn't about the tool, but the tool helped enable the processes and then that yielded the time to market, time to value. Yeah, and from an app side, I mean we, building these new architectures really requires containerization, requires the automation. So we can't, we can't attack, you know, the proper microservice patterns and practices without really, without open shift as a platform underneath. It's foundation, yeah. And I think I like the stress, the fact that it really was all of us knew we had to get something done, and we all came together. There was no, there was no, the silos were immediately broken down. We knew we had a mission to get through, we knew we had something to get done in a short period of time, and we just came together in such a strong, collaborative way of driving the solution. Well, that's great, and congratulations. Innovation Award here at the show, it's been a great week here at Red Hat Summit. So, Mark Falto, Dan Savarese from UPS, congrats and thanks for being here on theCUBE. Well thank you, John. All right, well we are here live in San Francisco, we are finishing up day three, we'll be back after a short break in all of our live coverage of Red Hat Summit on theCUBE.


Punishment in the classroom, is it correct or not? Since we should appraise students, we should punish them as well. I do not believe that the decision, of whether or not to punish is up to us. Therefore, discipline is a key to success for both teachers and students. Thus, once we deal with a bad conduct case, there are strategies to use to overcome it. The Code of Conduct The main purpose of a Code of Conduct is to make things better whenever possible, otherwise, it could not bring positive changes. We exert punishment with regard to a disciplinary Code set up by school authorities. Therefore, the decision of establishing that Code is out of our control. In effect, we are mainly seen as performers. School authorities may argue with teachers when a Code is not conveniently followed. Reasonably, we have to keep in mind that teachers who do not apply a Code of Conduct may face disciplinary action. That is to say, we are also punishable. Certainly, teachers could never accept to lose their jobs for concealing a misconduct case. Report Although teaching is one of the most respected jobs in the world, there is no proof that it can be done without difficulties. Indubitably, a school must be an area of knowledge seekers, but not a spot of troublemakers. Knowing that it is vital that we act on time as soon as possible whenever confronted with misconduct before it gets out of hand. A good class environment requires mutual respect between teachers and learners. We must inspire our students, but we will never find an excuse for being lawbreakers. We should not favor a group of students to the detriment of another group too. It will always be in our benefit to promote good rapport which is inevitable for the sake of everyone. Physical punishment Naturally, young children are known for being noisier making fun of others. Furthermore, they are not bored playing or talking when they should be listening. Once in a while, young students might go further for stealing, skipping class, bullying so on and so far, causing disorder in the learning environment. As soon as possible, we must act without delay by talking to the concerned students after class. Another solution is to summon a meeting with their parents to discuss the issue. Teachers should never make a decision in a hurry. If the first attempt does not help, we implement a punishment as a last resort and with regard to the code of conduct. For example, the students at fault can water the school garden after class, clean the classroom for one week, denied the recess, or even barred from attending school for one day, among others. Any physical punishment should be banned. One strategy may work for one student and not for the other. In this case, it is up to teachers to make an adjustment. We also must remember that overstepping our prerogative might put us in troubles. Are you ready to teach English abroad? Dealing with a disciplinary matter is one of the most challenging tasks in the teaching job. The difference between the student's background can generate problems. In every situation, we must prefer discussions to punishment. It is not obvious that all punishment can work. So we must always have a plan be ready for implementation. The sooner we react, the better the strategy works. Speak with an ITTT advisor today to put together your personal plan for teaching English abroad. Send us an email or call us toll-free at 1-800-490-0531 to speak with an ITTT advisor today.


Ukraine's massive ammo deficit, greatest danger to NATO security, Armageddon is considered inevitable. Two weeks of NATO drama have somewhat overshadowed Ukraine's deteriorating battlefield position as Western politicians and media focus on the ever-present danger of direct conflict between Moscow and its trans-Atlantic rivals according to Newsweek. Kiev's forces are struggling to hold the long front line in the south and east of the country against continued and at times frenzied assaults. Units are increasingly short of manpower and are still being denied the Western ammunition and advanced weapons Kiev says it vitally needs. Recent interventions and a significant intelligence leak from Western capitals, though, have focused on the prospect of NATO troops operating within Ukraine and prompted fresh threats of nuclear war from Russian President Vladimir Putin and his Kremlin allies. French President Emmanuel Macron first raised the proposal of deploying NATO troops to Ukraine in training and advisory roles. In his denouncement of the plan, German Chancellor Olaf Scholz revealed that French and British troops are already thought to be in country. This conclusion was then echoed in a recording intercepted and leaked by Russia of senior German military officials discussing Western support to Ukraine. The greatest acute danger is still from the front lines in Ukraine. One European diplomatic official who spoke to Newsweek on the condition of anonymity as they were not authorized to speak publicly said when asked about the prospects of Russian escalation. The ammunition deficit is massive and Russian pressure intense, they added. The West is paralyzed by fear. So far all the red lines we've crossed have not brought the Armageddon we're so afraid of. A second European diplomatic official who also requested anonymity to speak candidly suggested to Newsweek that Moscow primarily wants to exploit alliance concerns to further deter Western aid to Kiev. I doubt you can change Russia's calculus just by sending trainers to Ukraine, they said. I'm sure the Russians are well aware of who's doing what in Ukraine the diplomatic official added. Ukraine needs ammo and air defense. That's where the immediate focus should be. The German government has delivered a civil defense risk analysis report to the Bundestag outlining one of the likely scenarios of a possible conflict between an unnamed aggressor and NATO based on lessons learned from Russia's full scale war against Ukraine. European pravda reported this. According to the report, Russia's war against Ukraine has confirmed that modern warfare combines classical and unconventional operations, the latter including cyber attacks, disinformation campaigns and sabotage. An aggressor attack, hybrid and or using the full arsenal of modern armed forces in all dimensions on NATO territory is therefore a likely scenario. The report says the report's authors then outline one of the scenarios for such an attack emphasizing that it is only one of the possible scenarios and not specifying what the other scenarios envisage. This scenario divides the conflict into four phases. Phase one lasts for several years with varying degrees of intensity and involves hybrid influence by the aggressor, espionage, cyber attacks, sabotage and attacks on vital and defense facilities and critical infrastructure. A key feature of this phase is that the hybrid influence is conducted covertly and cannot be immediately linked to the aggressor. Phase two lasts several months and involves the deployment of aggressor forces on NATO's eastern borders and the deployment of NATO deterrence forces in response. The hybrid influence continues but becomes more intense and less covert. Phase three which lasts for at least one year involves open military aggression against NATO territory, selective attacks using conventional and non-conventional means including against targets in Germany as well as possible disruption of satellites in space. Finally during phase four the aggressor's troops break through NATO defense lines into Germany. A full-scale armed confrontation in space is also envisaged. The scenario assumes that this phase ends with a ceasefire agreement no earlier than a few months later. In the report the German government proposes that this scenario should be used as the basis for building a civil defense concept and that the relevant agencies can model further sub-scenarios for more effective defense. It was previously reported that the Bundeswehr is drawing up a new comprehensive operational defense plan for the first time since the end of the Cold War taking into account the lessons learned from Russia's full-scale aggression against Ukraine. Russia prepares for China's invasion. Military rehearses use of nuclear weapons. The Russian armed forces have reportedly rehearsed the early stage use of tactical nuclear weapons in a conflict scenario with a major global power according to leaked information from Russian military files outlining preparations for potential Chinese aggression. A threshold for the implementation of tactical nuclear weapons appears lower than ever publicly acknowledged by Russia. The cash comprises 29 classified Russian military files spanning from 2008 to 2014. Criteria for potential nuclear responses range from an adversary's invasion of Russian territory to more specific triggers such as the destruction of 20% of Russian strategic submarines armed with ballistic missiles. Despite the documents dating back a decade or more experts assert their relevance to contemporary Russian military doctrine. Training materials depict scenarios wherein the Russian Eastern Military District simulated various incursions by China. Such exercises offer rare insights into Russia's view of its nuclear arsenal as a cornerstone of defense policy and its readiness to deliver a first nuclear strike under certain combat conditions. One exercise outlining a hypothetical attack by China notes that Russia dubbed the Northern Federation for the purpose of the war game could respond with a tactical nuclear strike in order to stop the South from advancing with a second wave of invading forces. The order has been given by the Commander-in-Chief to use nuclear weapons. In the event the enemy deploys second echelon units and the South threatens to attack further in the direction of the main strike. The document says, In a separate training presentation for naval officers unrelated to China, broader criteria for a potential nuclear strike are outlined, including repelling an adversary's landing on Russian territory, targeting units responsible for guarding border areas, or countering an imminent enemy attack with conventional arms. The threshold is defined as a combination of factors where losses incurred by Russian forces would irrevocably lead to their failure to stop major enemy aggression, a scenario deemed critical situation for the state of security of Russia.


Humps, bumps, swales, wispy grass Anything else Luke? Firm greens, firm fairways, rolling fairways, bunkers Look at that, look how nice that is Look at this, that's pretty damn good isn't it? I'd better go in at the golf shop What iron did you use? Five. What iron did you tell me to use? Cheers, bud. Give me that Best thing from two of that Come on then, we'll give it to you Very nice Make the greens at Castle Rock are pure mate, aren't they? They're solid, absolutely just, love them I've got a lot to say really, I'm quite content here I love Ireland You love this, don't you? It's a sunny day in Ireland, we're on the golf course So this is part of a media day at Castle Rock, it's on the Monday The open obviously starts on Thursday I'm going to do a bit of the practice days as well Right, switch over to, we're not playing stroke one here How nice is this? Switch on, haven't we? Yeah, yeah, you've got it mate, you've got it Oh, Louie, wow That was a good time for me to press the camera on, wasn't it? Oh, the shape on that What did you say to stroke one at Castle Rock mate? It was all right, yeah Hopefully I can just get on the green and two putty Oh, he's done that Two good t-shirts mate Yeah, really good Take that Look, I don't even want to know where the ball's gone You can see where it's gone That is a smile, isn't it? That was a good strike That was a great shot How do you feel to be in Ireland? Oh, lovely I mean, Ireland is 23 degrees, it's not a breath of wind Yeah, it's not the island we would think of really Take it though, it's better Oh, what a strike, beautiful Purely, bit of a kick Now, we're playing this media day but we've ended up just being a two ball at the minute so I need, we're on nearest to the pin and I need photographic evidence of this shot, Lou Well, need what? That's easy for you to say Oh, isn't it well yet? Yeah, I've just played four really good holes there or five, wherever it is Anyway, come on Playing 206 to the flag, proper par 3 That's a beautiful strike Now, you've pureed it You'll pick that one up, I would think That's pin I as well I can see the marker at the moment, it's front right There's a chance that might be to the flag Is it really? We need to leave it on Nearest to pin I've clubbed him So, he's got the best excuse in the world I can't hit it, I hope this goes pin I because he's hit it pure Oh, it's long It's your fault mate, I can't believe it That 206 to the flag mate, that's carried That's carried, so you can one bounce and it's up into that bank So basically it's your fault though really What I ended you use? Five What I ended you tell me to use? Cheers bud So there's mine Clubbed myself to perfection Hit a great shot, run down off here And then listens and takes advice No good That is enough I stayed with you rather than the ball then That was great technique out of there Just popped it up nice and neat didn't you? Well if you see the bounce I think we can just pick it up That's it Look where I am away, thanks for the club by the way That's it, I was just mocking how you listened to everything I say Right, come on Lou, let's see the birdie Be nice I'll say this, you think that's going to be a tough one to Well we'll see Well 206 pointed into 10 feet That's not bad Bit of a swing on this I think I might be wrong Lou I thought you were in there as a pin I can't believe that I hope it's just quite a man Oh don't say Have you called him? Yeah, yeah, yeah For anyone who knows you're quite tall aren't you And you just didn't have a chance at Not the best of lies was it 18 told as well Not the way you want to finish around is it It's not the best years we've had Ah that's quality Super shot that Right, we have just arrived in Port Stuart Golf Club It's day two of our little trip to Ireland But this is a special day because we're about to meet Literally a golfing legend Who are we meeting? We're meeting This man Turn the shoulder Turn the shoulder and move the weight Look at that When you hit him like that This is how you walk to the next In Kentucky in America And I win the tournament three times in a row So now I go to the press The guy says to me He's driving the ball better What do you like about your driver? I said well the grip this The kick point is here I've got it set with a slight draw It's flatter and I said I did say that I said And there are 40 press guys there If I had to choose between this club And my wife I'd miss her The next day's headlines in the paper So I go to the gym and I come back And my wife hiding in the cupboard And I walk in the bedroom And there's my driver on the bed With a note You've chosen your new mate I won't be at the gate I went to Japan and I watched these little men They stand like this And they've got a man over here with a brick And he's hand he goes With his hands Now they're no knuckles They've broken the hand a hundred times So there's just a wart So they break the brick Now they say to the guy Watch this Speedo They sort of put himself in the river And he's like And there are brick shatters Two bricks You think you're seeing things I said to the man How do you get such speed Do you get over your shoulders And this was when I was a young man He said no From here Here Shoo Shoo Just rotation there Shoo But you see when I'm rotating You see how my weight's going forward Look Shoo That's the ideal swing Rotation with your weight going forward Right so you've arrived First day in the open So this is the Tuesday This is one of the practice days obviously I'll just show you a little way around But I'll tell you what The first hole They're going to be teeing off from back there Into that little grandstand And that's where they're at in What a great opening All that is We've got Henrik A bit of beef there Molonari Molonari been the gym mate He's looking a bit To any old tight skintop there You got one of them It wouldn't be the first thing I bought From the merch store Comments down below Do you want to see me looing in there Skintight Molonari like Look it's programmed for Dishonbo swing How steep is that How steep that is Now what about the finish That's not your That's not your normal finishing position is it That is weird So this machine is set up for Dishonbo swing So it replicates where he would be with that That is so weird That's incredible They changed it up for a different player every day I think tomorrow they said it's Tiger Woods But I think the Dishonbo thing is perfect Because that is so different Where he is in the top of his back swing It's so strange How weird was that Wow Incredible That is on both sides of the swing Yeah it is What's happening on the follow through It's so different That's incredible In Dishonbo You've got to have a go Because you'll never be You'll keep your arms as stiff as you can Well that's how it feels when you're in the top of here Even at set up A few legends here today I've got one stood alongside me Willie Gregg from the Harbour Bar in Port Royal Correct It's all going on down there this week We're blessed We've got It's the 19th green tea You call it You know It's official And the bar's all decked out Completely decked out with all bits and pieces Of gulf and paraphernalia or regalia But the world's gulfers are there And we've been garing And Mother Nature's going to be good to us She's shining on us So our little bar Turns into a massive bar We'll be there tonight I'll see you tonight You can see the videos down there And we'll see you down there I'll be there tonight Pleasure Pleasure I prefer to get soaked I prefer to get soaked Come on, don't be done No It's a little bit miserable today at the open I'm not the best way to start Let's hope this goes off a little bit between now And some people, otherwise It won't be a great watch on the television And it's not going to be too good for spectators either It's fair to say the bars And eateries are a lot busier today So as a people It's incredible this is practice day On the Wednesday And it is absolutely heaving here That royal poor rush