 Yes, I am about to recommend to all of you a distribution that removes the sudo command. So let me repeat that Vanilla OS 2 has no sudo command. That is quite interesting and it was announced by the project using the title sudoant, which for enough sudoant. So I'll get to sudo, but let me give some context. I'm talking about Vanilla OS 2.0, code named Orchid, which is not released yet. The team, however, is very active in telling us everything about the in-progress work and I'm here to report to you that it's super interesting. So let's talk about it. Vanilla relies a lot on immutability, which as a general idea disallows changing system files to keep your system stable and the same throughout different installations. That brings some issues, such as what if you need to install a system package or what if you need to update, which necessarily requires system packages to be changed. So let's start with updates. Previously, Vanilla used the package manager in an isolated and atomic environment, basically creating an overlay on top of your system first, using APT to apply the update there and then if everything went correctly, the overlay is applied to the system. This is no longer the case in Orchid. Now the package manager is never used at all actually during the update and you instead download at each update the entire image of the updated system, making your local system an exact copy of the reference one published by Vanilla. Of course not all of the target image is actually downloaded, you only download the difference between the previous system and the new one, but the result is the same. And this is quite useful as it makes the system 100% reproducible and faithful to the tests that Vanilla did before releasing it. This however raises the question, what if I need to install a certain driver or package thus changing the system image I'm using. Now we'll get drivers which you can install in a graphical and effortless way, but let's say you want to install a system package. You can do that through the command apiroot package at each top as an example, followed by apiroot package apply. The apply command will create a local image a bit like a fork and this one will be kept up to date with the latest version of VanillaOS as well. Okay, but what if you really want to change the base system? Let's say that you don't like GNOME and I mean who does? It was at this moment that he knew. He fucked up. This is a joke. And you want to install KDA Plasma. This requires a lot of changes. So what Vanilla recommends in this scenario is to create your own image based on the Vanilla one, but changing all the stuff that you need. There is a standard called the open container initiative and you just have to follow that standard. To make that easier though Vanilla created a tool called Vib or Vanilla image builder, which makes it easier to create OCI images. There's recites and modules and I won't get into the details, but Vib creates something that looks kind of like a flatback and then compiles that into an OCI image that you can use into your Vanilla install. But what if you hate Debian? Because of course as we covered Vanilla or KDA is actually based on Debian. So interestingly enough, the project is quite modular and provides three different OCI images to users. The first one is called a stop. It's the one that you will download normally and contains everything I've talked about. However, the desktop image is based on the core image, which only contains the core components of Vanilla OS. And the core image is based on yet another image called Pico, which is just a minimal version of Debian. So basically they take Debian, remove everything they don't need, like Sudo. Publish that as an OCI image and then add core components. Publish that as an OCI image as well. And then add all the rest of the features and publish that as the main OCI image that users will actually install. Thing is, it's really easy to just kill Pico, take a different distribution, make an OCI image out of it and then reapply core and Vanilla OS images on top of that. And thus the system is really meant to make it easier to swap out the distribution it's based on, which is really cool. And as I've mentioned, you can also swap out the desktop image for something you've made custom with Vib. So that it has such that it has a different desktop or a specific setup that you like. So our kit is flexible, even on the other way around, you should now be able to see why I think there's great potential here. Of course, it won't be of any interest nor potential if we're unable to install our applications and such on it. So our kit has two tools that you will use to install and remove stuff without even touching the system files. One is called APX and it's meant for developers and the other is VSO, which is presented as a system package manager. So let's start with VSO, which by the way stands for Vanilla System Operator. It allows you to install three kind of packages, Debian packages, Nix packages and Android packages. The latter is probably the most exciting one and of course it uses WeDroid under the hood, meaning that you get native performances as WeDroid is not a virtual machine or anything like that. The apps are just as integrated in the system as everything else and you can install or remove them through the Vanilla's UI. Debian packages instead are not actually installed as system files, you know, that would break immutability. Instead, VSO creates a system decontainer, which is deeply integrated with the system and uses, surprise, the Pico image that I've talked about earlier on. So the application or packages aren't actually installed in your system, but they're installed in this sub-system that's still based on Vanilla OS Pico OCI image. And this keeps installing packages simple and intuitive, but if anything goes wrong, you still have a completely stable system to just kick out the VSO thing. Switching to IPX instead, stuff gets more exciting, though, or how IPX works in Hockey is that it creates an environment that can be based on any Linux distribution. It does this through stacks, basically. Stacks are made of a base Linux distribution and a list of packages. You can create your own stacks by changing the distribution or the packages, though there are many stacks out of the box. Then you just tell IPX to create a new sub-system using that stack. Then that you can enter it and do basically whatever, even installing stuff that wasn't originally in it. But if anything goes wrong, you can always throw it back to the stack. So basically you can use DNF or Zipper or any package manager of any distribution. And you can customize exactly which packages you need from each of these sub-systems and they will directly integrate with the base Vanilla system. Which, come on, come on, come on, come on, you pussy. That's cool. That's cool. And of course, on top of all of this, they also decided to remove sudo. At least this is for the base system. Obviously, you can still sudo around inside the sub-systems. Since Vanilla aims to be as stable as can be, you will now have to use PKexec for any kind of super user action you need to take. PKexec is actually quite similar to sudo, but it involves Polkit, which allows for a finer green control of running apps like defining rules and such. So it's sudo, but with more controls in place to make sure everything is fine. This is because the idea really is that you should interact with the base system only using the commands provided by Vanilla, or just don't, and live with the sub-systems that integrate with it but are easier to kill if anything goes terribly wrong. All of this, mind you, is extremely technical stuff that happens mostly behind the scenes. But the sheer focus on making sure that Vanilla has just works always makes it a super compelling option for, in my personal example, installing it on my special other computer. Because she's really not into the technical stuff, and if the operating system dies, then she just rolls back to Windows, meaning that the operating system should never die. And it did, just a few months ago, due to a bad KD Neon update, which I had to fix at 3am. That should never happen. And in Vanilla OS, it wouldn't have happened. But of course, if I want her to use Vanilla OS, it also has to be user-intuitive enough for her to use it. And starting from the installation process. In fact, Vanilla is now using a completely new installer back-end they wrote, called Albuus, which now supports looks to encryption as well. Albium reads a JSON file containing an installation recipe. I just cannot pronounce this word. Recibe? I don't know. And just sets up the operating system. Meaning that it's really easy to work with it as a developer. Meaning it's really easy to create a good front-end for it. Vanilla OS comes with a super nice installer front-end by default. But if you do want to swap GNOME for something else, and I'm not gonna make any desktop suggestion of course, then Albuus makes it super easy to go ahead and write a new installer front-end that uses the toolkit that's gonna make the whole thing feel native with the desktop. What if any of this goes wrong? What if you run a command on the terminal whilst half asleep and somehow you just kill Vanilla OS with it? Well, even if you do that, Orchid comes with a recovery mode with a lot of options in as saving your OS. You can reinstall Vanilla OS whilst preserving your apps and personal data as an example, which is already impressive in itself. But recovery mode also gives you access to disk utilities, a rescue shell, a web browser to copy-paste the commands from some help forum, obviously. And it repairs the file system using fsck, thank you. All of this with a nice click of a mouse that everybody can understand. So yeah, what can I say, I am impressed. About that. I did manage to get all of Vanilla OS developers or almost everybody on a live stream, which is going to be as the time of recording this Friday. And I'm not sure if this video is gonna be published before or after the live stream, depends on the editing time. But if it's published before, then this Friday, this Friday, you can come to the live stream. If it's published after, you can just go to the videos, check out the live stream and it's one hour long, probably, if everything went correctly. So you can just learn about Vanilla OS in depth and learn everything that you want to, you know, discover about it because sounds exciting. We don't have the new update yet, but I just talked about it for 15 minutes. So before I go, let me tell you about the people that actually make this whole thing where this whole thing is, you know, the videos, the key involvement that I have and the podcast, everything actually possible. So it's these people on my left and right. And generally speaking, I do have a goal for each month of 700 bucks to actually, you know, make a living out of it, at least make this whole thing work. And so if I'm able to reach that, that would be awesome. So if you have some tips, some spare changes, some money, some money to give me, then that would be awesome. I do have like Patreon, Ko-Fi, PayPal, LibrePay, anything. And I do give some benefits to people donating through Patreon or Ko-Fi, such as, you know, posts, posts and podcasts, these kind of things. I haven't done any in like a month because I was super busy. But now I'm back. I'm going to start again. I promise, I promise. So that was it really. Thanks everybody for following. And what can I say, like good luck Vanilla OS with this very nice system that you're developing. You can really tell which part of the video is scripted and which one isn't right.