 Over the past year i3 window manager has been my absolute favorite window manager and I Still think that i3 is my favorite and I'll probably return to it someday, but I'm kind of on a Review streak if you will I'm currently using q-tile and I've been using q-tile now for about three weeks Maybe a little bit longer So what I wanted to do today is compare these two I've used q-tile long enough to kind of get a sense of what it's all about and how to configure it and How to write it and all this stuff and I used i3 for a very long time So I feel like I can do a pretty good job of comparing these two So that's what we're gonna do today now before we jump in I should say that I'm not going to declare a winner out of either These two these are both excellent window managers and if I were to give one piece of advice out of all this I would say try them both while it may take up some time to do and to configure both of them I would say try them and that's going to be the easiest way to discover which one works best for you But if you want to know some more information, let's go ahead and jump in to the comparison So we're gonna start with i3 now when it comes to i3 i3's installation is fairly easy I3 the regular version of i3 at least is available in most repos on almost every distribution So you'll be able to install it with your package manager If you are looking for a variant of i3 specifically probably i3 gaps That's going to be a little bit more rare when it comes to being in a repository if you're using arts You'll be able to download it via the a you are if you're using something like a boon to you're probably going to have to Build it from source if you're using fedora, you can get it from a copper repose So if you're just going to use the non gaps version, you're gonna have a very easy time installing it If you're using the gaps version, you're gonna have to work a little bit harder for it Personally, I always use the gaps version just because it's better to have the option to use gaps and then Not use them then to not have them in your i3 and then want them later on if that makes sense at all now i3 is a Manual Tyler basically what that means is that you decide where the windows going to spawn next So as you'll see in the b-roll, you'll see that each window Spawns in the same direction until I press a key binding which causes the windows to go in another direction basically this allows you total control over where a Window is spawned when you open it in terms of configuration i3 is configured in what I call a user readable configuration file and What I mean by that is that it's not Configured in a coding language per se. It's not coded in C or Python or Haskell or anything like that It's very much its own type of thing and it's very easy to read and easy to configure No matter your skill level so things like declaring Workspace variables things like declaring key bindings stuff like that all that stuff is very easy to do Very easy to kind of suss out as to how it's done One of my personal favorite things about a window manager is the workspaces and with i3 Workspaces are done incredibly well. You can decide how many workspaces you have an i3 You can have as many as you want all you have to do is put them inside of your configuration file and then Put corresponding key bindings to each of those workspaces inside your configuration file Now obviously you have to have keys for those workspaces and those key bindings available to you So eventually you would probably run out of keys because there's eventually going to be You know a lack of combinations that you can use but that's going to be a lot of workspaces You'll probably never gonna need that many personally. I use 19 workspaces. I know that's a lot but in i3 19 workspaces work really well for me and I've talked about workspaces in i3 in another video I will link that in one of the cards above me one of the most customizable parts of any Window manager is the bar now unlike something like BSPWM or Xmone ad i3 comes with its own bar It's called i3 bar and the default way of putting Widgets or modules or whatever inside of that bar is called i3 status I three status is fairly configurable. Most people don't really use it, but it can be done I've also just done a video on i3 blocks Which is kind of an upgrade super version of i3 status which allows you to do quite a bit more in terms of customization a Lot of people who use i3 ditch the standard bar all together and use a third-party bar like poly bar or tint to or EWW or something like that and one of the great things about i3 is that it really does a good job of Allowing you to use whatever bar you want to use most bar support i3 There are several third-party bars that only support i3 things like lemon lemon bar and bumblebee bar and things like that Most of those bars like I said were either built specifically for i3 or do a really good job of Supporting i3 out of the box and i3 itself Obviously is very easy to configure with a third-party bar. You can simply remove the standard Default bar by commenting out three lines in the standard configuration file and that just turns off the bar And then you can run whatever third-party bar you want in whatever manner you're supposed to do so The next thing we should talk about is community when it comes to community and The community surrounding i3 i3 has a very large community because it's one of the most popular window managers And what this means for you is that if you need support chances are it's going to be very easy to get support Or at least get answers to your question also and this is something that I find Very nice the developer of i3 is very active within the community and often answers the questions themselves So if you are having some issues with i3 or there's something going on that you need help with chances are you'll be able to go to places like reddit or Certain discords things like that and find the help that you need and because the community is so large You're probably going to get a fairly fast response Of course adding on top of that is the absolutely Excellent documentation in my opinion i3 has the best documentation of any window manager and I'm showing this on screen right now It is a very Condensed a codified documentation it's all in one place and It's very well organized and the best part about it in my opinion is that it's non-technical and by non-technical I just mean that it's not written for developers if that makes sense you can be a just a random Joe Schmo off the street Read the i3 configuration file and understand basically everything in it perfectly fine. I know that's the way I've been I'm not a developer and even when I was just beginning in Linux just beginning with tiling window managers i3's Documentation was very very easy to read and understand the final thing that I want to talk about in i3 before We get into some pros and cons is that i3 does have several variants So I've already talked about one of these i3 gaps basically that's i3 just with added gap support There are a couple other variants as well The biggest one out there is probably sway sway window manager is not a fork of i3 But it is very closely related in that it uses the same configuration file sway is basically i3 But with the Wayland compositor so instead of using xorg it uses Wayland and If that's something that you're interested in trying out that Exists it and it does use your i3 configuration file So if you have an existing i3 config file you can use that inside sway and you want to start over from scratch The only place that's not Absolutely true is with the bar sway does its own bar thing and you kind of have to deal with the bar there Separately than you would in i3. Let's go ahead then and jump into some pros and cons of i3 window manager So starting on the positive sign the first one and I think that this is probably the biggest pro is that it's configured in a user-readable format and basically why I think that this is so big is because it enables people who aren't developers to dive right into a configuration file and Tweak to their hearts content it's really really simple to get started configuring and ricing and all that stuff with i3 and If you compare and contrast that to something like q-tile It's much easier to get into i3 simply because you don't have to know Python You don't have to know Haskell or something like you wouldn't X monad You can just dive right in look at the documentation and even if you don't look at the documentation You can kind of figure out just Reading the configuration file what things are going on there Another pro is that i3 has excellent third-party bar support now It doesn't mean that you can't use third-party bars with q-tile. You can I'll talk about that later But with i3 it's very very simple. It's very simple to disable the default bar So you can just disable the default bar plop in poly bar or whatever and it just works And because i3 is so popular most of the bars that you'd want to use with i3 have i3 support So you're not gonna have to worry about your Workspaces not showing up or not being functional things like that and that's definitely a problem with things like awesome window manager and X monad where those really weren't built for poly bar at least and You'd have the same problem with some other bars as well when it comes to those other window managers with i3 Third-party bar support is fantastic The third pro that I want to talk about and I've already discussed this a little bit is that they have excellent non-technical Documentation which means that you can dive in not know anything about a coding or programming language and pretty much understand every word That is in there and be able to come out on the other side knowing Basically everything there is to know about i3 window manager and the final pro is one that again that I've already talked about because i3 is so Popular it has a very large community that means that you're going to be able to find support very easily in any number of places And if you have an issue you can go to these places and find the support that you need It's not as niche as cutile. So while you can get support with cutile There's plenty of people there in the community that are willing to help you It's not quite as large as the i3 community and your response times may be a little bit shorter in i3 Than it is in cutile. So despite me being a bit of a i3 fan boy I am also going to name some cons. So the first one is that it's non extensible So because it's configured in a user readable configuration file You're constrained to what you can do with that configuration file Everything that you can do in that configuration file has been coded for you. It's all included right out of the box There's nothing there that you can add on top of that without knowing some programming language or Some scripting language at least to kind of extend it yourself. There's no patching like you would find in DWM There's no adding stuff to the actual configuration file because it's not in a coding language. It's just Pre-configured for you the options that it has are the option that has it's not going to have any more than that ever The second con is related to that is that it's not configured in its native language, which means that you're reliant on the Options in the configuration file that were coded for you You don't have access or at least easy access to the code all that stuff kind of happens in the background instead you're using this user readable configuration file and It just kind of means that you have less control over everything so if That bothers you if you're not interested in using a configuration file that is kind of more constrained Then i3 may not be for you The third one is probably the biggest con for a lot of people and that is that it's a manual tiling window manager A lot of people do not like manual tilers. They prefer to have a dynamic tiling window manager like Qtile and It really does come down to a matter of taste Which is why at the beginning I told you to try both of them manual tiling just Doesn't really work for a lot of people simply because they want to have it set up so that there's a layout Available to you that has a more readable function than just things popping up along the window One by one by one and only changing that late out with a actual user intervention So a lot of people prefer to have things like auto tiling enabled with i3 There's a script that allows you to do that But that's an add-on extra and it's something that they've done through like a bash script But for most people who just use vanilla i3 or i3 gaps You're going to have to deal with that manual tiling aspect of it and that's not for everybody The last con that I want to talk about is one that's not really a con I don't think and that is that they use some really weird key bindings out of the box The biggest one and the biggest example is that they use Jkl semicolon for the movement keys now if you've used them or you're used to using other window managers You know that's a little weird because most window managers use hjkl Which are the Vim keys but for me personally it doesn't seem weird to me even though I always change it to the Vim keys if you just think about a little while your Hands on your keyboard if you're using QWERTY are are supposed to be on at least if you're using touch typing You're supposed to have your key your four fingers on jkl semicolon That's the reason why they have that in the configuration file But it's easy to change so I don't really consider it a con you just go in there and change it to the Vim keys And you're ready to go. It's not that big of a deal. So that is i3 Let's go ahead and jump in to Qtile So the first thing that you should know of course is about installation installation is Astonishingly simple for Qtile. It's in almost every Repository you can think of there are no extra variants that you have to really worry about when you install it Just installs now obviously There is the whole idea that sometimes depending on what distribution you're gonna be using You're probably going to be using an older version of Qtile But for the most part that's not going to be that big of a deal as long as it works You're gonna be happy and you can if you want the latest and greatest and you're not using something like arch or something You can build it yourself It's fairly easy the one thing that you should know when you do download Qtile Is that you're probably going to be downloading a whole bunch of Python libraries? Which is not that big a deal because you probably have a whole bunch of those on your system anyways But whereas i3 is written in C So you're not gonna be downloading a whole bunch of libraries there because you're gonna have a whole bunch of C stuff on your computer Anyways with i3 you're probably going to be downloading a whole bunch of extra libraries Which means you're gonna have some extra dependencies there and you're gonna have to kind of worry about that Especially if you're building stuff from scratch Unlike i3 Qtile is a dynamic tiling window manager Which as you're seeing in the b-roll that's showing right now Basically means that there is a given profile Layout that comes by default and in the case of Qtile the default layout is called master stack Basically what that means is you have one large window along the left hand side and then a small stack of windows the more you open them up on them on the right hand side and Qtile does have other layouts that are available to you probably about 12 layouts actually I'm not sure if that's the right number, but a fair number things like floating monocle Reverse monad things like that where you have Different layouts that you can kind of choose from depending on what you prefer Like I said by default is the master stack layout and Basically the dynamic portion of this just means that everything is set in a Layout for you You don't have to choose where the windows are going to spawn next if you're in a certain layout You know exactly where the next window is going to spawn in terms of configuration Qtile is configured in Python So it is highly useful And I'll talk about this more in the pros and cons for you to know some Python in order to get into this now That being said if you don't know any Python It's not insurmountable that you can actually jump into this and learn how to configure it I don't know hardly any Python at all And I was able to get in there and kind of understand what was going on within a couple days We will talk about the documentation here in a few minutes, but it is fairly easy to get in there and and kind of Muck around and learn enough to the point where you can rice it and configure your key bindings as long as you emulate What is there? You're probably going to be just fine and as you use Qtile for Any amount of time if you stick with it, you're going to learn some or at least enough Python to know how to do certain things So things like adding in scratch pad support and stuff like that is fairly simple But you kind of have to know that it's there in order to do it So it is configured in Python and that means that you're going to have to follow the rules of Python so you're gonna have to put commas where they need to go you're gonna need to put brackets and Things like that where they need to go. Otherwise, you're going to get errors. So Because it's a programming language, you have to follow the rules of the programming language Now one thing to say about that is that Python is a fairly forgiving coding language if you make some mistakes it's usually fairly easy to spot them and Qtile set up in a way that Most of the time you're it's going to tell you exactly where you've made a mistake So Qtile is configured in Python and that is a big difference from I3 Which is again in a user readable format like with I3 Qtile will allow you to use basically any number of workspaces that you want The difference is is that the way the configuration is done For your workspaces or groups as they call them in Qtile is that each Workspaces named what I mean by that is that by default you have workspaces one two three four five six seven eight nine Okay, those are the workspaces each workspace has a number as its name and the way that it's configured by default is that The name is also corresponding to The key binding that you wanted to have to have so for example if you wanted to have a workspace called workspace a you could do that you could define a workspace a and Because you've assigned it the letter a that would also be the key binding so the names and the Keybindings kind of go hand-in-hand. It's a little confusing and it's not something that you're gonna have an easy time adding more than like 12 workspaces simply because it's hard to Find new keys that aren't taking up by other stuff. So that was my personal problem I wanted more workspaces, but all my key bindings are kind of taken up So that was my issue with that One thing that you might want to know when it comes to workspaces is that names and labels are not the same So labels are what's going to appear in the bar Names are the names of the workspaces that correspond with the key binding So that can be a little bit confusing. You might want to check the documentation for that So moving on to the bar the bar in Qtile is highly configurable And it does come standard out of the box You do get a bar out of the box that appears along the bottom just like it does in Qt in i3 And it does have some built-in widgets that are already there for you ready to go I think the time is there. I may be wrong in terms of that, but the way you Configure the bar in Qtile is done inside the Qtile configuration file config.py and You Basically choose what widgets you want to use so each thing that resides in the bar is a widget So for example in the b-roll you're saying now Along the left-hand side you see the groups or the workspaces That's one widget and then you in the center I have another widget and then I have a whole bunch of other widgets on the right hand side Like weather and stuff like that each of those things is called a widget The greatest thing about the Qtile bar is that there are a ton of built-in widgets that you can just use They're well documented. They have excellent options for almost every Widget that you want to choose and because there are so many of them You probably not going to have to deal with creating your own ever there are just a there's At least two dozen probably three dozen widgets that you can choose from just built-in ready for you to use You just put them in your configuration file in the manner that you're supposed to and it works just fine And I find that great simply because that's not the case with every bar out there Some bars you pretty much do everything yourself. So the fact that You can do pretty much whatever you want with this bar is really nice You also have the option for a vertical bar if you want So if you want to have a bar that runs up and down you can do that and most of the widgets that are available To you will also work in vertical mode. The next thing we should talk about is the community now Qtile is not as popular as i3 at least when it comes to the number of people who Take part in discussions about it on like reddit and stuff whatever So I don't have like any firm numbers But you can kind of tell that i3 is more popular because you're seeing more rices and the communities on reddit And other places are a little bit bigger that being said in the time that I've used Qtile I've had not a problem at all at getting response to my questions when I've had them So like the Qtile subreddit you just ask your question. They were very helpful over there Even though the community is not quite as large The next thing that we should talk about is documentation that kind of goes hand-in-hand with the community the documentation for Qtile is Fantastic it does have some downsides, which I'll talk about later But in terms of having a central place where you can find all the documentation Qtiles documentation is fantastic Basically anything you want to know about Qtile is there and well documented There is a lot of text there that explains what's going on how you're supposed to do things It does for the most part give you examples of how things are supposed to run Especially when you're talking about the bar and stuff like that. It does have examples, which is nice They're not always the most useful examples. So you kind of have to get into the flow of how the Code for your widget and stuff that is supposed to work once you get a hang of that the examples make a hell of a lot more sense So the documentation is fantastic I would not say that it's as good as i3's documentation, but I'll talk about why in a few minutes So the last part before we jump into the pros and cons is the variants So the chief variant or these the only variant that I actually know of is the Waylon variant of Qtile And that comes pre-installed every time you install Qtile. So when you install Qtile from Your repositories or if you build it from scratch or whatever You're going to get the x11 version, which is going to be the default version and you're going to get the Waylon version Now in terms of performance on the Waylon version, I can't really speak to that yet. I haven't tried it much yet so I don't want to Put any any opinions out there and just be completely wrong So it just know that it does come available to you if you want to try it So moving on to the pros and cons of Qtile and as we did with i3 we'll start with the positive stuff Because it's configured in the language that it's programmed in It's easy to extend so if you know Python you can basically do anything with Qtile that you want to do You can do things in any number of ways you want to do and because again It's configured in Python if there is a library of Python that you want to import and do something with you can do So obviously again the ability to extend this relies on your knowledge of Python So if you don't know anything about Python, you're not going to do much extending of Qtile But you obviously can learn Python or at least learn some Python and have the ability to extend it It's kind of like DWM in this aspect where DWM is coded and Configured in C and if you the more see you learn the more Extensible DWM becomes it's the same thing here only instead of C. We're looking at Python The next pro is that it has excellent scratch pad support now This is not going to matter to everybody it matters to me because I love scratch pads but Basically a scratch pad if you don't know is a Extra terminal that kind of lives in a hidden workspace that you can bring up whenever you want and do stuff in and then The scent then send away it just stays running and obviously it's not just a terminal you can put anything on scratch pad that you want and The best part about the scratch pads in Qtile is that if you kill them They can come back you don't have to restart Qtile in order to get them back And that's the biggest downside of scratch pads in I3 whereas if you kill it, it's dead You can't get it back. You have to restart I3 So while they both of these window managers have scratch pads built in to them And they're very easy to implement in both cases I put Qtile's support of scratch pads a little bit ahead simply because they're a little bit easier to use but also simply that they are Respawnable, I suppose that that's the best way to put it if that's even a word probably not But anyways scratch pad support excellent in Qtile The next one is something that I've already talked about is it has an awesome and highly extensible bar It has a ton of widgets available to you So basically you can do anything with this bar that you could possibly conceive of Personally in terms of a default bar I think that this may be the best default bar of any window manager It beats I3's default bar by miles in most ways at least simply because the I3 bar by default is a Little bit harder to configure simply because you have to download another configuration file and deal with a whole bunch of scripts That you may not may or may not know anything about So with Qtile's bar because it has a you know a huge widget base You can just pretty much plop anything in there that you want You can just carry on with your day and on top of that you can do a vertical bar if you want There is better support for click events and things like that inside of Qtile bar than there is in the standard Qtile I3 bar so the bar in Qtile I think is much better now that being said of course with I3 most people use a third-party bar And once you open up the market to a third-party bar the bar is pretty much equal themselves out in the end of the day So the bar in Qtile fantastic the fourth one is Excellent documentation just like I3 I would say that Qtile is probably has the second best documentation of any window manager out there It's really very good But the downside and we're kind of dealing with a con here is that the documentation is very technical So if you don't know any Python, you're gonna be in a little bit of trouble It's not impossible. I don't want to say that but if you don't know any Python it's going to be a little bit harder to Navigate through the Qtile documentation and this is especially true if you want to do something But you don't know how to do it and that's usually the time you'd go seek out the Documentation and the reason why I say it in that way is because if you go to the the documentation try to search for something That you want to do and the only way they've described how to do it is in Python And you don't know how to search for that particular way to do things in Python It may it's just a little bit harder to search for stuff when you don't know what to search for If that makes any sense at all. So it's not like I said, it's not completely unusable a lot of times they'll have just a plain English description of what they're doing and In fact, they have that in a lot of places it's not in such a way that where how you search for that might be equal if that makes any sense at all like the How you search for it is going to be in layman's terms where how they describe it is going to be in Developer terms and those things might not mesh the last pro is that it has a built-in Wayland Version and you just get that you don't have to go download it. You can just use it if you want to and that's really nice It's probably not for everybody. Most people are going to just deal with the XORG version, but The Wayland version is there. You don't have to worry about adding an entirely different window manager to use Wayland Moving on to the cons the first con that I want to talk about is the adding scripts the bar is Hard it's not something that I thought would be true, but it is hard So if you want to use your own bash scripts in the cutile bar It is possible as several people have shown to me, but it's not as easy as I had expected to be I thought there'd be a widget that you could just use this is hey Here's a but here's a script put the output of the script in the bar I figured that's the way it would be but especially given with the number of widgets that they have I figured that there'd be a widget like that, but there's not so that's the first con and that's really a me con like That's just something that I noticed that affected me But if that's something that is important to you like you've if you've used Polybar for a long time and you have a whole bunch of your own scripts And you want to use those scripts inside of cutile bar It's not as easy as I is you would think it would be in order to use those The second con is that pycom acts up in cutile now I have talked to several people who have not had this experience but I had this experience all the damn time and that is that pycom just crashes in Random situations and the biggest situation is when my screen goes blank Usually when I'm sitting here recording just staring at the camera my my screens will go blank Which is there's what they're supposed to do, but when I come back Pycom is just freaking the hell out and for no reason I have to kill Python in order to get to have my screens Not you know like flash at me. It's really really weird and I don't like it at all I'm not I'm positive that this is a pycom problem, but that being said this does not happen in i3 So I don't know if there's some weird interaction between pycom and Python that's going on there or what's going on But if you use pycom as your compositor, you may discover that you have some issues there. It's not Unusable. It's just noticeable The third con is something that I've talked about before is that it's easier to configure cutile If you know some Python and the reason why I put this as a con is that if you are a brand new Cutile user and you don't know any Python You're gonna have a harder time configuring this than someone who knows some Python So it's not like I said at the beginning of this section Insurmountable if you don't know any Python, but you're going to have to be willing to learn You're gonna have to put some effort into it in order to get from the point where you're just staring at the configuration Follow in pure horror to the point where you know at least mostly what's going on Which is kind of where I started like I looked at it like this is not as horrifying as Haskell But it's definitely not see which is what I'm most comfortable with so That's where I started and now I'm here three weeks later I know quite a bit more Python than I did before still not a developer of Python so I'm not gonna claim that but I've definitely learned quite a bit in these three weeks and I think that most people could do that as long as they're willing to put the effort in the next con is that Cutile has an inconsistent way of dealing with errors So when you have an error in the configuration file You were never gonna know whether or not cutiles going to load into the default configuration tell you hey You're in a default configuration. Go find that error on your own or you may if you're lucky Get a notification that says hey, this is the error This is the line that there is on go fix it and it's still actually using your configuration files So all your key bindings work the problem that I have here is that you never know which one of those situations You're gonna find yourself in sometimes your configuration files going to break completely and it's going to revert to the default configuration file Sometimes you're gonna get lucky and you're gonna get that notification now The thing is is that if you don't have a notification is Damon running so something like Dunst You're always going to get pushed into the default configuration file and the default configuration file is Not easy to use especially if you've gotten used to using your own key bindings So you'll definitely want to look up the default configuration File key bindings if you find yourself in that situation fairly often so You'll want to know how to restart specifically Cutile without having to shut your computer down and all the way back in In order to get things to work again That's the way I was at the beginning because I had no clue what the default bindings were and every time I got there Or every time I had a you know an error It just went to that default configuration file and that was a pain in the butt once I installed Dunst I got the notification error much more often And that's nice That's a really good way to fail and like I said most of the time it will give you the line number of where your mistake was The problem that I have is that it's not consistent right sometimes you're even once you've installed the notification Damon And you get those notifications sometimes still sometimes you're going to fail completely and go into that default configuration file I wish there was some way that it would just was more consistent and the last con that I want to talk about and this one is Probably the biggest one out of all of them is that Qtel is very very highly maintained and Usually that's a really good thing and it is a good thing I like that the developers are very involved in making Qtel better the problem that that comes with that is that when you get an update to Qtel it often breaks stuff and Usually this happens with the bar and widget and stuff You they make up change with one of their widgets or whatever and that just breaks the bar and usually when the bar breaks The whole thing breaks and that means that you have to kind of pay attention to what those updates are bringing along to you So that you know if you have to make any changes to your configuration file The thing is that if this was just like one time it wouldn't be that big of a deal But pretty much every time they do an update for Qtel I'd say probably about 50% of time I suppose I guess is the real like if I had to guess I'd say about half the time they do an update Something is gonna break So that's definitely going to be something that you have to kind of keep in mind And it's not that big of a deal as long as you kind of pay attention to When you get an update and then you know to go check the change log and see what's going on because they'll tell you when they push along a System breaking change. It's just you kind of have to seek that information out So those are the cons of Qtel now when it comes to comparing these things together Again, as I said before The best solution for pretty much everyone is to try both because they're both Really different when it comes to workflow because that one's manual one's dynamic and Which one of those things that you like is really going to depend on your experience with both of them You really have to try them. I can't tell you hey manuals better automatically. I used to be able to say that I used to be able to tell you hey manuals the way to go Because it gives you the absolute most control over where your windows are just gonna spawn I used to be of that opinion I don't think that anymore. I think that it's more of a personal choice a lot of people can't stand manual Tyler So they all prefer Dynamic Tyler some people really don't like the dynamic tiling way of doing things and prefer to have total control It's you know, your personal experience is going to decide which one of those two that you like So that means you should try them both. I think that's the best solution So I hope you guys some good information out of this video if you have comments or questions or any that kind of stuff You can leave those in the comment section below you can follow me on Twitter at the next cast You can follow me on mastodon or odyssey those links will be in the video description You can support me on patreon and patreon.com slash the Linux cast just like all these five people Thanks to everybody who does support me on patreon. You see you guys are all Absolutely amazing people. Thank you so much for your support without you the challenges would not be anywhere close to being where it is right now So just seriously guys. Thanks for your support. It's just thanks. Thanks. I'm here for watching. I'll see you next time