 And as much as I did not like using macOS for 30 days, I hate using Windows even more. It did happen that I received internal criticism. And people still felt like, oh, KD copied Windows. No, we've been doing that for like five years. And honestly, the current Breeze team, it's not bad. Like it's legible, it has good contrast. It's very usable, it's just what I think. So I just wanted to say that Plasma 6 is coming, finally. And a very important detail of Plasma 6 is that we haven't decided to just do a Plasma 6 because we thought, okay, it's been enough time since Plasma 5. Let's just do something new. But rather obviously, QT released a new version of its toolkit, QT6. And since we rely a lot on QT, we decided to create a new Plasma to go along with a new release of QT. But at the same time, given that we were kind of forced to make a new major release of Plasma, we thought, okay, what do we want this new QT Plasma version to be? And we kind of discussed this and decided some things months and months ago. And just now, finally, we're getting some results and seeing how that things we decided are actually translating into real code. So I was really wondering, since your channels is much bigger than mine, and people when Plasma 6 are released are very likely to go to you to hear about the latest stuff. What do you expect Plasma 6 to go? And what do you think QT developer should have at this point decided as their goal and targets for Plasma 6? Okay, so I'll try not to call or my answer too much with what I know of Plasma 6. I'm going to try to talk from the point of view of like, I don't know what's in there. And first, I think it's a great thing to have made like a major release, like separate from the usual cycle, like not forcing you yourselves to have a four-month release cycle for this one. I think 5.27 is a great, is that a great stage right now? It's really stable. It works well. It has decent Wayland implementations. Like it's a good base for people to wait until Plasma 6 happens. Now for Plasma 6 itself, for me personally, I think what should be the focus or what should have been the focus since development already started a lot is probably like just spending the time to refine things further than what 5.27 has done, because I think 5.27 and just the whole KD5 series was kind of constrained in terms of what you could do, because well, it has a lot of baggage and people are expecting regular updates. With Plasma 6, since you're already porting to QT6, you have the opportunity to rework a lot of stuff. And so what I would expect personally is just a lot more polish, not necessarily more features, because I think KD has virtually everything anyone could ask for. Maybe the only thing that you can't really do with it is sort of a basic Mac OS dock, because you can kind of replicate that with a Plasma panel, but it doesn't exactly work in the same way. That's about it. So not necessarily more features, but just more polish, like finalizing, completely finalizing the Wayland transition, making the Plasma desktop and Plasmoids a little bit less finicky to place, to align, maybe unify the visual style of a lot of Plasmoids, which can be very disjointed, like if you try to place them on a column on your screen, none of them will have the exact same width and stuff like that. Just generally a lot of polish and you can take the time to do that. And you can basically bring KDE at a level that I don't think it has reached before, not even at the 3.5 series. Now the second thing is not necessarily a Plasma thing, it's more of an application thing. We've seen the GNOME app ecosystem completely explode in terms of number and quality, and I wish KDE had the same kind of vibrant ecosystem. KDE has a lot of cool applications, but you don't see the same number of smaller utilities that look really easy to use, that really follow the guidelines of the desktop, and I think that could be an opportunity as well, but that's not necessarily linked to Plasma. And in fact, that is very similar to what we decided. Especially it was, we discussed that in the past we haven't had a history of major releases that were like super stable and people were super happy about. In fact, I know of developers who started contributing to KDE Plasma because a major release was like pretty bad and they hopped in 12 out. And we wanted this to be completely different having something that is very stable out of the box as soon as it's released. And we didn't quite look for new features. And even though we knew that, I mean Plasma 6 is one year from now, people are going to make new releases, new features that's just gonna happen. And you mentioned the dock. I do agree with that. And currently my plan, there is already a complete redesign of the panel settings. We do have to change it further because of technical stuff. And I would like to add a button that allows you to make it a dock, just a button, which wouldn't be an additional feature compared to what we have currently. It would just make it floating at the center with the task manager and not filling the whole screen. Yeah, sort of like something you could do manually, but doing it in one click instead of having to place everything yourself. Yeah, just making it easier and more streamlined. That's kind of the goal. And I do agree with the GNOME application ecosystem being a target, like a goal for what we have to do. And it's what we're and are trying to do with Kuregami. A lot of things are switching to Kuregami. And very soon, a couple of days, we are going to have a new suite in Kuregami for email contact and calendar and to do, which is pretty cool, I think. Is it based on the calendar app? Yes. Basically, the calendar app grew so much that it decided to split into multiple smaller apps. That's cool. It's an awesome application. I think it's one of the fastest growing KDE applications. And you started the whole thing saying, ignoring what I know of Plasma 6, what do you know of Plasma 6? Let's see if I can remember everything I talked about in the past like 10 news videos. Obviously, Wayland fixes, making sure the applications don't crash when the compositor crashes. So that was a big one. They're switching to double click by default. There's a revamp in the settings page, I think, we're moving some buttons to the header of each settings page instead of having like a double row of buttons below. There's a revamp of Dolphin settings, search fields in various apps. What else did I see? A complete rewrite of the widget system, as far as I understand it. What else? Yeah, better integration with icon themes and sound themes was also a thing. From the top of my head, those are the big ones that I can remember. That's already quite an impressive memory. When you write those videos and you record them, you basically read every news article five times. To be fair, I did like obviously a lot of video Plasma 6. I've also had a talk at KDE Academy, and yet I still have all of my notes there with all the changes I wanted to mention because I'm going to forget otherwise. The thing is we have two major different branches of development, one of which obviously we have a lot of stuff that goes underneath that the user won't see, obviously. But stuff that is noticeable to the user is changes in the default and new feature-centered designs. As far as changes in the default, one good example is the double click by default, something I fully disagree on. But what do you think of that one? What team are you? I think it's a good change because that's what most users are used to. But when I use KDE, I always use it with single click. Currently, I'm on GNOME. When I use GNOME, I use double click. But when I'm on KDE, I don't know why. I'm just used to single click on KDE, and it works for me. But I think for most users, double click is more what they know. We had to switch to double click especially because a lot of distros were changing our default to make sure it was double click. We're not even deciding the default anymore. Distros are doing it for us. We had to switch. My personal prediction is that we're going to switch back as single click as soon as the rest of the industry realizes that it's better. But another thing we wanted to do is to try to have some changes in design that are default changes, so very easy to do. But that could distinguish us visually from other desktops. And one example of that is using the floating panel by default. Did you see that? What do you think of it? I think it was quite controversial. I think it's really good as well because for most people who are going to discover KDE, it's going to look better. Because let's be honest, it looks better. You can't argue that a fixed panel stuck to the edge of the screen looks better than something that flows with rounded corners. You just can't. It looks better. And I'm not just saying that because you developed it. But it's a great look. And people who don't like it, it's a right click and one toggle to check. It's super easy to revert it if you don't like it. But I think for new users, it gives a more striking appearance. And honestly, when you're going to see something like Windows 12, I would be very surprised if their taskbar wasn't the exact same way. Instead of using the whole of the screen, it would be centered and floating. I'm pretty sure they'll do it. Yeah, that kind of worries me because if we try to make the taskbar floating to visually distinguish from other operating systems, and then Windows 12 is like floating taskbar. But I mean, if we are first, we can kind of say, hey, copy this. Yeah, exactly. Well, that was also the argument like when Plasma 5 was released and the change in the breeze theme and the Plasma theme, it was new. It did not look like something like Windows 10. And then Windows 11 came and just basically looked exactly the same. And people still felt like, oh, KDE copied Windows. No, we've been doing that for like five years. Yeah, always happens. There's a lot of like when Windows used our slogan. Oh, yeah. Yeah, that's true. Yeah. We saw that and it was like, oh, Windows. I've heard of that already. Do you think there are other simple changes that we could do to distinguish visually from other desktops? Well, they would probably be changes for the sake of being changes and not necessarily super usable. But yeah, for example, having a different window button layout, like splitting the buttons like you would get the window controls, maximize and minimize on one side and the close button on the other one, much like very old versions of macOS, for example, close on the right, but everything else on the left. You could have a very different theme. I was sort of expecting for Plasma 6 a different breeze theme. I know it has been revamped relatively recently in the in the Plasma 5 cycle, but I would have liked to see a different one. I think the icons really hold up pretty well. But I think the general theme for the apps feels a little bit flat, a little bit dated in my opinion, but that's very subjective. So yeah, but these would be changes for the sake of changes, they wouldn't necessarily bring much usability in terms of how things work. So I think honestly, KD's strength is not necessarily looking so different than other things out of the box. It's more that you can make it look very, very different if you want to. True that. I will admit that there are some issues where basically all KD developers or almost all KD developers use the default theme with the default settings. And because of that, most third party themes do tend to break over time because we are just testing, we are not testing them. So, but that's definitely on us. Yeah, and you couldn't test all of them. Like if you had to test every default theme and every quantum theme, like you would only be doing that. And it's not exactly your job to do it. So yeah, usually we have like a couple of themes that are meant for testing purposes. Do you know of the fluffy bunny theme? Yeah, it's wonderful. That is the theme that we usually resort to when we have to test something. It's pretty funny in the video recaps that I do about it. Regarding the theme revamp, that is actually something that a lot of people coming to KD asked for. Very often people would join the visual design team. And the first thing they would say is, let's do a big redesign. Let's do everything from scratch. We can't quite do it for a variety of reasons, obviously, mainly main power. And we often had to say, like, these are great ideas, but we can just cannot do something like that. And I usually have had to say in videos, like, it's very good that you want to join visual design team and contribute. The first thing that you do should not be to say, let's do everything from scratch. Like, when you join a project, try to slowly. Yeah, you pick a screen that looks super dated or is eligible and you try to revamp it. So it looks like more legible and better laid out. But you don't jump in saying, let's redesign the whole thing. Because first, you don't have any credibility in the team. So who knows where you're coming from, what your ideas are, what your experience in UX or UI is. And second, obviously people want to do that. But if they haven't started on it, then maybe it's not just because they like the ideas, probably because they like the time to do it. Yeah. And we do actually have a lot of things that are being redesigned from scratch within the Breeze theme, which is a lot of different small things. Well, obviously we improved it in the Breeze itself, the theme a lot over the Last Releases. We have, I think, half of an idea, which I don't know if we're going to follow up on that, but we kind of have half idea to change the name from Breeze to something else to actually say, okay, we did change a lot of things in the Last Releases and we want that change to have a name. But other things that are coming are completely redesigned sound theme as an example. And obviously that required having an interface to change sound themes, which we should soon have. And I will admit that most people I talk about this sound theme with like Plasma has sounds. I didn't know that. Well, they are. Yeah, when you plug in like a laptop, like you get a sound notification, I think some notifications also have sounds, pretty sure. The critical ones. Yeah. And I think when you boot up, no, maybe not, maybe not at startup. I think not. But there are not many. But honestly, you don't want your desktop to bombard you with sounds all the time. Like, yeah, for important things, cool. But yeah, don't send me a beep every time I receive one single notification because that's going to drive me nuts. Which fonts does like do which fonts do out of the box for some reason? I'm really annoyed by that actually. Especially when you like in a group conversation and all of a sudden people wake up and start talking and your phone starts beeping like crazy every two seconds. It's horrible. Yeah, I couldn't get rid of the notification sound of my phone. Eventually, I just set 100 milliseconds of silence as my notification. And that works. Yeah, that's a good workaround. And there's a lot of things happening with colors as well, because in 5.25 we introduce a lot of colorful features. And they look awesome. I like the window tinting and the accent colors in general. They look really good. Yeah, I totally agree. So what I did for Plasma 6 is create series of tasks that were like, can we please enable all of that by default? And luckily, people were like, no, for different reasons for each one. As an example, I really wanted accent color that changes depending on the wallpaper. So dynamic accent color and other developers rightfully were like, we can't change the colors of the elements every time the user changes the wallpaper that might distract or confuse them. And I can see that happening. And secondly, I wanted window tinting. So tinting with the default blue color every window slightly. But that also didn't get much traction. But we did decide on tinting the headerbars. So the idea is that by default blue, because that is the default accent color, all headerbars should be like the tinted blue. That is another reason that we are working on that isn't complete yet. And honestly, the current Breeze theme, it's not bad. Like it's legible. It has good contrast. It's very usable. It's just that I think the changes that happened in the like starting from I think 5.23 or 5.24 or something, like with the with the different colors for hovering over elements in menu stuff like that, all those changes were cool. But they were perceived as relatively minor in terms of visual changes. And so for people who've been using Katie since the start of the Katie five series, the desktop hasn't really changed much in terms of how it looks. And that's not necessarily a problem. But I understand why people would want it to evolve like more drastically than what's already been done. But but it's a good thing. Like it works. It works. It doesn't look old. It's not like it's Windows 98 or something. Yeah. I do have to agree that I say yeah. And I haven't used any other theme in years. So can't really compare. There's another which is why really we are focused on a slightly slight improvements like slowly making it better and better even for Plasma 6. There's also a Ken Burnett who redesigned all the icons of Dolphin. So all the folders, main types and such. So now the new folders that ideally should be that have to be in Plasma 6. Otherwise, I'm going to be very annoyed at myself much more rounded actually and friendly looking. So hopefully that is another thing that will slightly improve a breeze. And that's a good approach. Like instead of having a complete rework of everything, just touching up a few details that you feel are suboptimal or have aged worse than the rest. It lets you iterate and see what works. And then like if people love the new folders, I haven't seen them, but the rounded folders, maybe you can like redesign a bunch of other icons in the same sort of rounded style and go from there. And if people absolutely hate those icons and everybody thinks like it looks childish or cartoonish or I don't know, then you can move that back and go back to another style. So that's a good approach to design. What we are currently deciding now that we are closer to the release of Plasma 6 is when actually to release Plasma 6, because we don't have any kind of date as of right now. Do you think that we should go for like further in the further way, but with more testing or should we because it's been quite a while since the last Plasma release. Are people getting I would say yes, I would say push it as much as you can. Well, not like three years, but if you need more time for testing, push it a little bit because if the goal is to provide a very stable, very solid first version of Plasma 6 and not repeat some mistakes from earlier versions of Plasma where the initial version of a new series was pretty buggy, then I think it's better to have more time for testing. Like people already know that it's not going to release like in October or November. So if it needs to be pushed to January, February, March next year, I would say do it because it's always better to have something that is really cool out of the box, really complete. You have all the features you wanted, all the new design touches, very good stability for most use cases, then having something like, okay, you guys are getting impatient. So we're going to release it. And now everybody has a bad first impression with it because like, I don't know, multi monitors is broken for some reason. And then everybody's going to think, oh, Katie is so buggy. I'm never using that again, even though it's fixed in the next release. I would say push it if it needs more time. Yeah, I do think that a lot of people will try out Plasma 6 for Plasma with Plasma 6 for the first time in quite a while to decide if it has improved enough since the last time they tried it. So I do look at it as an occasion to show that Plasma has really improved in the last years. Yeah, and in a more logistical sense, if you ship a half broken or at least one major use case kind of broken and you say, oh, we're going to fix it, then you have the chance of distros still shipping your older release instead of the new one, which means that now you have split your user base between Plasma 6 and Plasma 5. And I don't think that's great. So yeah, I would say give it as much time as you want. 5.27 is a very good platform for people who like KDE. And judging from the comments on my videos, like people are excited for Plasma 6, but they're not like impatient in the sense of, oh, if they don't release something in the next two months, I'm out, I'm moving to something else. So I don't think there's two, I don't know if that is the same as the experience that you might have as a member of the KDE team and the developer. But me personally, when I talk about KDE, like people are excited about Plasma 6, but they're not saying like we need it right now. No, that's good. Well, as a member of KDE team, most people I talk to are also members of the KDE team and they know how to use the beta of Plasma 6. So I mean, I live on Plasma 6 already, so I'm not particularly eager to have it released. I can use all the features anyway. And another thing we have to decide on, and I'm actually quite interested, and I'm throwing a lot of the decisions we are making onto you because I'm really curious to see outside and is the release schedule. So currently we do three releases every year, so one every four months, which has some issues. As an example, it's very hard to align with these two release schedules, which are often a couple of times a year. And also it means that the time between we are done with the release and we are going to publish the release is very short, which is a problem for promotion. Like the promo team requires a bit of time to know about everything that has been done and write an announcement to videos and such. So we are considering switching to a slower release schedule, which would also have its own issues. As an example, you make a change, I don't know, in January. If due to stuff, it's the wrong time, you might have to wait even seven months to have it actually released to users. So there's a bit of benefits and issues both both ways. What do you think of that? Well, I think the two releases per year schedule is pretty good. Sure, it means that you're going to have to delay some features if they are not ready for inclusion. But I think it also means you don't have to follow like Katie had some kind of tick talk release cycle, like you had one with a lot of new features. And then you had one with a lot less features, but a lot of bug fixes for the new features that were added. And I think this can give the impression sometimes that Katie is not very stable, because if you start using Katie on a release that is bug fixes, then you have a great time. But if you start using it on a release that is majorly features, you might have some problems. So I think if you have more time for each release to polish it and make sure that all the bugs are well, all the bugs, you can never fix all the bugs. But most of the bugs and the most annoying ones are fixed. Then I think it gives a better impression. The ideal way, but I'm not sure that's doable would be to have like two releases per year, in my opinion, of course, two releases per year, and having some way to deliver some new features in the middle of a cycle. Like for example, if you have your release in February, but your feature has been started in January and will only be ready like two days after a feature freezes something, maybe having a way to include it in a point one release during the cycle is good. But at that point, you're also cannibalizing the new features for the next version. So it's not easy. I think I think it's better to stick to being close to distro releases, because ultimately, unless you have like, unless you want to push Katie knee on heavily as the distro for Katie, then you kind of depend on them. So you have to have most recent distros ship your most recent desktop. So I think it's the better approach. It has drawbacks, but I think it's best. But what do you think of Katie neon random question? I love it. Every time I need to try something on Katie, I run neon because like it's like it's an Ubuntu base. I know this by heart. Like, I know all the tools. And honestly, it's been super stable for me. The user edition never had any problems with it. You speak better of Katie neon that most Katie developers have talked about to neon about, you know, maybe they use the testing or unstable versions more. Because me personally, when I need to test the latest release of Katie for one of my videos, I obviously use like, I think it's the testing or the unstable. I never remember which one is the right one. But but I use one of these, which obviously like your testing primarily software, it's going to have problems. But like the user edition, I would personally pick it over something like Coulomb to, for example. Okay, that's good to hear. Obviously, it sadly doesn't quite. I cannot share that because I did have major issues with Katie neon sadly. So we would like to try something new with Katie neon, how it's done. Maybe visit on something else, this sort of sort of things, but nothing is ready to talk about it. So I will stop with Katie neon. One thing that we can do if we decide to switch to a couple of releases every year. And that would be nobody has told me don't do this yet. So I'm going to say that until somebody does is we could ideally align our kitty plasma release exactly on the same day as the GNOME release and have some sort of desktop party. This would make my life miserable. So please don't. And I think it might be badly perceived like, oh, they're trying to overshadow the competition. Let's call it that. I think it's better if the dates aren't perfectly aligned honestly, because yeah, you're basically dividing the attention of everyone between two things that they might have been interested in. But yeah, if you want to do that, like, sure, why not? But it's going to make my life very hard. It's true that mine as well. Obviously, I was curious to try that one time because it is true that it might divide the attention, attention between the two. But what we tend to see in Katie promo is that whenever you have more announcements on the same day, they tend to have a much wider audience, they reach a much wider audience compared to splitting them over time. So I was kind of curious to see maybe just trying out. I think a good case for doing that would be maybe if you have some kind of major collaboration with GNOME, I don't know, like the Katie team and the GNOME team work together on some kind of standard, let's say for accent colors or whatever, and both releases ship with that support in it. Maybe that's a good thing. Like, okay, yeah, we worked hand in hand. That would also put to rest the debate of Katie versus GNOME because people always fight online about that. But every time there's a new release of GNOME, the Katie team is like, hey, congrats, guys, it's awesome. And the same way, I mean, yeah, maybe it's a cool idea, but please not every time. That was a send a strong message. We tried to do that with the Apple's falls of GNOME. That was pretty funny. We really organized with GNOME to make sure to have really wanted the message to be stop doing like desktop wars. Yeah, you can compare desktops to showcase what's different, but like, what's the best? Well, Newsflash, nothing is the best for everyone. So that's why Windows is so bad, because it's trying to be good for everyone and it only succeeds at being mediocre for everyone because you can't please everyone with one single interface. It's impossible. Yeah, I received Windows computer just a couple of days ago to test it out. I boot up Windows 11. It's horrible. I hate it. I'm currently working on a I used Windows for 30 days video, like I did like the macOS video. And as much as I did not like using macOS for 30 days, I hate using Windows even more in the end. It's just it's horribly designed. I hate it. Are you using the very latest release of Windows 11? Yeah. Yes. So everything is blurry, which I like and also to me quite laggy. It's very laggy. And I've got ads everywhere in my start menu. Like I even got some weird banners in the file manager saying, Hey, use one drive in office 365. Like, why are you showing me this in the file manager? Like, it's an ad for your services in your OS. I paid for the OS when I bought the computer that you don't have to show me ads that you have my money already. Stop it. Really. And I got to say, I understand when people say that plasma, when you start customizing things feels a bit unstable or unpolished, like you if it's everything is as is by default and you don't touch anything, then usually it feels quite stable. Shouldn't break. But if you start customizing that, yeah. But I got to say with Windows, I got the same unstable finicky sensation when like popping up the overview they have, which comes from the bottom and just Yeah, it's kind of stuttery. It's not smooth. Like some of their gestures with touch pads, they're not one to one gestures, which completely baffles me like you do. It's like a keyboard shortcut. Like you do the gesture and then the stuff happens, but it doesn't move with your fingers. Come on. You have like, how many developers do you have Microsoft? Like, can't you do that? It's weird. So many things are just badly integrated. Well, let's not digress about Windows, but yeah, it's truly awful. Yeah, it's cool. And well, you mentioned just, sir, let me mention one thing at a very hand just to say because I'm quite proud of it. The one thing that I'm working on for Plasma 6 right now is the new overview. I don't know if you saw that. So it is much, much, much, much more similar to GNOME's overview compared to what we had. And it has the overview itself and the grid view all in one effect. And you can just cycle between the three or you can just toggle one. I quite like it. It's everything is one-to-one gestures. You can switch one-to-one desktops whilst in the overview. I think it's, I'm really proud of it. Yeah, that was the last remaining issue I had with Katie on laptops. It was like, I think it was a forefinger gesture up for the overview or something. And you had to do forefingers up again to get out of it, which in terms of positioning of elements feels weird because you brought it up. So to exit, you should bring it down, not re-bring it up. And if you had configured a forefingers down to open, for example, virtual desktops and trying to exit the overview would automatically move you to the virtual desktops without any transition and it felt weird. So I'm super happy that this is something that is being worked on. It's awesome. Yeah, it's true that you pointed out gestures are, I think, I'm really happy that we have them now and I think they're really good. But how they have been implemented, I think they're a bit of a failure story of Katie because they were half of implemented by one contributor that just did half of the stuff and left it there. We did include it into the release when it was clearly half baked. I didn't really like it or use it. And then for Plasma 5.25, finally somebody came to finish off this stuff and we finally actually talked about the fact that we had one-to-one gestures for real. But still, there were remaining issues such as this one, which is obvious. Like why would you have to do three fingers up again? Yeah, it's a small thing, but it's a bit of a disconnect. And I know I'm super peculiar about this. People on my YouTube comments always tell me who cares about one-to-one gestures. Like, Linux Mint has gestures, you do the gesture, it does the thing. Yeah, but it does not feel good to use. If you do this, lift your finger and then it happens. Nothing has moved with your finger. It's actually jarring and not helpful. In terms of user experience, it's not a smooth user experience. One-to-one gestures. If you're doing gestures, don't do them if they're not one-to-one. Just use keyboard shortcuts. It's the same thing. Yeah, I totally agree. I do have to point out, because I try to be honest as much as possible, the bug that you're referring to, the four fingers down to exit overview has been fixed by Alish, not me, before I started working on the... Actually, the day I started working on the new overview. So credit where it's due. I did not fix that. That said, when I present Katie and at the same time, I'm a Katie developer, sometimes I worry that it might seem like I'm doing some stuff that I'm not doing. Yeah, you sort of feel like you're taking credit for other people's work. It never came off as that for me personally, when I watch your videos. I never feel like you're presenting things like, hey, look what I did. It's more like, look what we did. So I don't think people think you're taking everything for yourself. It did happen that I received internal criticism between KD developers for some stuff that I did handle incorrectly. So it fought on me. So I really try to be careful on that. That said, that was actually kind of everything I wanted to say. But if you have any questions about the development of Plasma 6 that I can answer, if you have any... Well, I won't ask when does it come out, because obviously we talked about this. But yeah, no, I don't have any questions specifically. I'm just glad to have those weekly blog posts that are published to see what is being worked on. And even some technical details, which are really cool to learn about, like how icon themes have been changed slightly in Plasma 6. I really enjoy reading about this. And yeah, it will be ready when it's ready. And as soon as it's out, I'll start using it as a daily driver, because I want to see how well it works. And I've been wanting to move back to KD for a while now, because I like switching. But I'm not going to switch to 5.27 if 6 comes out in like four months, because yeah, what might as well wait and have like a real big impression of KD at the same time when Plasma 6 is out. That is the pressure to KD developers to make a product that works perfectly. Yeah, nothing is perfect. I don't think I've ever used a Linux desktop that is perfect out of the box and has zero bugs, like not even a proprietary desktop. Like my experience on macOS has been riddled with issues. There are bugs everywhere, stuff that doesn't react, stuff that doesn't show on hover, tons of problems. And Windows, same thing. Like the taskbar is a finicky beast. It bugs out a lot on multi-monitor setups, which you'd think they have this down by now, but apparently not. So it's not a problem if you have bugs. Like the problem is if you have major bugs that affect 70% of the user base, I guess. Nice. So that was everything from me. And thank you so much for tuning in. I hope this was interesting for you as well.