Some snap versions of programs are just as fast as their apt and flatpak versions. However, many snap version programs are not even close, such as Steam.
Agreed. Flatpak seems less random when it comes to performance in comparison to Snaps.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Some snap versions of programs are just as fast as their apt and flatpak versions. However, many snap version programs are not even close, such as Steam.
It’s not so random, Snaps hate ZFS as your primary partition, you mix those two and your in for a bad time.Agreed. Flatpak seems less random when it comes to performance in comparison to Snaps.
It’s not so random, Snaps hate ZFS as your primary partition, you mix those two and your in for a bad time.
The other side there is when building the package, compression algorithms play a huge role in startup performance and there is not a one size fits all, the high compression formats designed for older hardware or IoT with limited memory tank performance, but lower compression algorithms and ones with lower ratios work much better.
Most use gzip or xz for compatibility and high ratios but you can improve performance greatly by using lzo, the trade off there is a lower compression ratio on small and medium sized packages. But as the package size increases they all eventually reach a degree of parity where their differences become negligible.
Dev kits also play an important roll, Mono and Electron for one reason or another create terrible Snaps packages even if you do everything right, it has something to do with node.js and building the runtime environment.
Update:
I’m told it might not be ZFS itself but an interaction with Zsys. As that is what facilitates the nested ZFS systems that you inevitably create when running Snaps on ZFS. I said to them that if you need Zsys for compatibility then ZFS is still the root of the problem. Then we got killed by bugs and the subject changed to where the F was Steve with our cover.
hijack,With the advent of Flatpak, many developers simply adopted the Flatpak standard as it's universal across distro's, as opposed to packaging the application to suit individual distro's. TBH, this isn't a bad thing, and Flatpaks are simple to install.
The only way you're going to get the latest software out of the Ubuntu repo's is if the software is packaged as a Snap and actively maintained by the developer. If you want the very latest version of whatever package you're running, best to avoid the Ubuntu repo's. With the advent of Flatpak, considering most packaged distro's can access Flathub, the problem of outdated software in your distro's software store is quickly becoming a non issue.
EDIT: You can even get Wine in a Flatpak now, which is fantastic. When it comes to my Linux desktop, I tend to go for a mix of Windows/MacOS:
hijack,
how do you put your icons at the bottom centre like that? Probably something easy I am missing. Using KDE6 plasma right now and I think its amazing. Big change form cinnamon that came default on Mint. I generally run XFCE, but even this beats it. imo.
I decided to download latte dock. Probably fairly similar.Right click the bar, there's a way to configure that in one of those menus.
I don't remember exactly what it's called, need to grab my laptop, but what you're looking for is literally just a few clicks away.
hijack,
how do you put your icons at the bottom centre like that? Probably something easy I am missing. Using KDE6 plasma right now and I think its amazing. Big change form cinnamon that came default on Mint. I generally run XFCE, but even this beats it. imo.
I decided to download latte dock. Probably fairly similar.
Turns out I have KDE 5.xx, not 6. I couldn't really find any information about using it on mint.You create an additional floating dock located at the bottom of the screen and add the 'Icon's only Task Manager' widget.
Latte Dock isn't actively developed anymore, you will have problems with Latte Dock. Latte Dock won't work under Wayland.
Using Latte dock now on Mint 21.3 with KDE5. Usually I can choose Wayland when I pick a DE at the login screen, but with plasma I don't get the Wayland option, so no harm no foul.
Need the plasma-workspace-wayland package, which isn't default on kde5 I guess. I find it's a bit buggier anyway, but that may be specific to my hardware/drivers.Usually I can choose Wayland when I pick a DE at the login screen, but with plasma I don't get the Wayland option, so no harm no foul.
YeahAre you still running Mint with KDE Plasma as an additional DE?
Cool! I'll try after I'm done this raidNeed the plasma-workspace-wayland package, which isn't default on kde5 I guess. I find it's a bit buggier anyway, but that may be specific to my hardware/drivers.
Why? What happens?Wayland's just not there for me yet, I tend to stick to good 'ol X11.
I tried using ZFS on my SSD and that was a big mistake. It works, so long as you don't put a custom kernel like Xanmod. In the end it wasn't faster than EXT4 and I ended up reformatting the drive to EXT4.It’s not so random, Snaps hate ZFS as your primary partition, you mix those two and your in for a bad time.
The other side there is when building the package, compression algorithms play a huge role in startup performance and there is not a one size fits all, the high compression formats designed for older hardware or IoT with limited memory tank performance, but lower compression algorithms and ones with lower ratios work much better.
Most use gzip or xz for compatibility and high ratios but you can improve performance greatly by using lzo, the trade off there is a lower compression ratio on small and medium sized packages. But as the package size increases they all eventually reach a degree of parity where their differences become negligible.
Dev kits also play an important roll, Mono and Electron for one reason or another create terrible Snaps packages even if you do everything right, it has something to do with node.js and building the runtime environment.
Update:
I’m told it might not be ZFS itself but an interaction with Zsys. As that is what facilitates the nested ZFS systems that you inevitably create when running Snaps on ZFS. I said to them that if you need Zsys for compatibility then ZFS is still the root of the problem. Then we got killed by bugs and the subject changed to where the F was Steve with our cover.
Wayland is the future but it just recently started to get support from other projects. I know Wine just added Wayland support, and Cinnamon is just getting started on it. It's so fresh that even in benchmarks it isn't faster than X11. Which is strange that Hector Martin who works on Asahi Linux for Apple Silicon was demanding people to stop using X11. The is the problem with the Linux developers in that they all have the best way of doing something, but it usually results in a less functional machine. I'm sticking with X11 until Wayland has proven to be 100% or better than X11.Wayland's just not there for me yet, I tend to stick to good 'ol X11.
Graphic glitches, things are just missing on screen. Wayland is also not great on Nvidia, though it does work. Xwayland allows X11 applications to work on Wayland but it's not fast. Games run slower on Wayland vs X11.Why? What happens?
Wayland is the future but it just recently started to get support from other projects. I know Wine just added Wayland support, and Cinnamon is just getting started on it. It's so fresh that even in benchmarks it isn't faster than X11. Which is strange that Hector Martin who works on Asahi Linux for Apple Silicon was demanding people to stop using X11. The is the problem with the Linux developers in that they all have the best way of doing something, but it usually results in a less functional machine. I'm sticking with X11 until Wayland has proven to be 100% or better than X11.
ZFS is a great software level raid solution if you are running multiple spindle drives. ZFS is highly optimized for mechanical disks and those optimizations and checks are useless for SSDs and NVMEs and more often than not the commands send to them will just burn the solid state options.tried using ZFS on my SSD and that was a big mistake. It works, so long as you don't put a custom kernel like Xanmod. In the end it wasn't faster than EXT4 and I ended up reformatting the drive to EXT4
The problem with Wayland is that it's essentially broken by design. Applications essentially don't have control over their own windows. Sure, it's all in the name of security, however if you have Malware on your system - you're already pwned. Devs could have enforced no control over other process windows, but instead they chose to go full retard.
Even window positioning is a mess. I run multiple virtual desktops, with applications limited to their own virtual desktops. Under X11, I boot and everything is where it should be, under Wayland I boot and everything is lumped into the one virtual desktop.
I'm sticking with X11 right up until the bitter end, every time I've tried Wayland there's been some showstopper issue preventing me from using it, and almost all of those issues have nothing to do with the fact that I'm running Nvidia hardware/drivers. Furthermore, because Wayland is the compositor and not your WM - It's not like you can just switch WM's and everything will be roses.
/rant off
The "ZFS for everything" religious phenomenon has been an interesting one on the timeline of modern computing. Off-topic, but ZFS is pretty much inescapable for anyone that's tried researching improving or expanding their storage. Just about every online guide, forum, youtuber-that-knows-just-enough-to-be-dangerous preaches it as the One Tool for every storage job, and often knee-jerk dismiss anything else in a discussion. And not always because they took the time to truly understand how it works under the hood, but because they themselves heard it from someone else, or equate safety to popularity.ZFS is a great software level raid solution if you are running multiple spindle drives. ZFS is highly optimized for mechanical disks and those optimizations and checks are useless for SSDs and NVMEs and more often than not the commands send to them will just burn the solid state options.
ZFS should display a warning that says:
*not recommended for solid state storage options.
Next to it on the selections menu during install.
Wayland on AMD is damn dream. I moved my nvidia card to the HTPC/Family Gaming Room and took the AMD card and put it on my office computer since I primarily run Linux there. Ever since the switch it's been a dream. Update after update, program after program no issues. Even GPU sharing with KVMs runs without issue. To each their own but the only issues I used to have dealt with screenshots on Wayland. Other than that nothing to report.The problem with Wayland is that it's essentially broken by design. Applications essentially don't have control over their own windows. Sure, it's all in the name of security, however if you have Malware on your system - you're already pwned. Devs could have enforced no control over other process windows, but instead they chose to go full retard.
Even window positioning is a mess. I run multiple virtual desktops, with applications limited to their own virtual desktops. Under X11, I boot and everything is where it should be, under Wayland I boot and everything is lumped into the one virtual desktop.
I'm sticking with X11 right up until the bitter end, every time I've tried Wayland there's been some showstopper issue preventing me from using it, and almost all of those issues have nothing to do with the fact that I'm running Nvidia hardware/drivers. Furthermore, because Wayland is the compositor and not your WM - It's not like you can just switch WM's and everything will be roses.
/rant off
I’m having fun playing with a Microsoft ReFS stack right now and that’s been interesting. Performs really well and it was smart enough to point out the stupid shit I did and flag me for it and actually tell me how to fix it. So weird when a Microsoft error actually gives you useful information.The "ZFS for everything" religious phenomenon has been an interesting one on the timeline of modern computing. Off-topic, but ZFS is pretty much inescapable for anyone that's tried researching improving or expanding their storage. Just about every online guide, forum, youtuber-that-knows-just-enough-to-be-dangerous preaches it as the One Tool for every storage job, and often knee-jerk dismiss anything else in a discussion. And not always because they took the time to truly understand how it works under the hood, but because they themselves heard it from someone else, or equate safety to popularity.
It's excellent for a lot of use cases - the built-up goodwill isn't an accident. But it's complex and has gotcha's and quirks, data corruption bugs are still being found occasionally, expansion isn't straightforward, and striping non-mission-critical data like home media introduces unnecessary risk that can be avoided with other solutions. /old man waving broom
Wayland on AMD is damn dream. I moved my nvidia card to the HTPC/Family Gaming Room and took the AMD card and put it on my office computer since I primarily run Linux there. Ever since the switch it's been a dream. Update after update, program after program no issues. Even GPU sharing with KVMs runs without issue. To each their own but the only issues I used to have dealt with screenshots on Wayland. Other than that nothing to report.
I'm on AMD and for me Wayland sucks ass. It's ok until I want to run a game. For example, in order to run Lost Epoch I have to input a launch option to run it in an X11 window and then it hard locks the system if I alt-tab. Now I just login under X11 since it always works and it has me questioning returning the 7900XT and grabbing a 4070ti S or 4080S. I figure that by the time Wayland is actually good it will be ok on Nvidia.Wayland on AMD is damn dream. I moved my nvidia card to the HTPC/Family Gaming Room and took the AMD card and put it on my office computer since I primarily run Linux there. Ever since the switch it's been a dream. Update after update, program after program no issues. Even GPU sharing with KVMs runs without issue. To each their own but the only issues I used to have dealt with screenshots on Wayland. Other than that nothing to report.
I did a little research on the floating docks. Turns out I need 5.25.x to have the option, which is why I couldn't find it. Only 5.24.7 is available on my Mint 21.3 distro. Oh well. Latte dock for now!You create an additional floating dock located at the bottom of the screen and add the 'Icon's only Task Manager' widget.
Latte Dock isn't actively developed anymore, you will have problems with Latte Dock. Latte Dock won't work under Wayland.
I did a little research on the floating docks. Turns out I need 5.25.x to have the option, which is why I couldn't find it. Only 5.24.7 is available on my Mint 21.3 distro. Oh well. Latte dock for now!
I'm on AMD and for me Wayland sucks ass. It's ok until I want to run a game. For example, in order to run Lost Epoch I have to input a launch option to run it in an X11 window and then it hard locks the system if I alt-tab. Now I just login under X11 since it always works and it has me questioning returning the 7900XT and grabbing a 4070ti S or 4080S. I figure that by the time Wayland is actually good it will be ok on Nvidia.
I just installed KDE Neon instead.I don't think floating docks became an option until 5.27, although my memory isn't great so I could be wrong.
And meanwhile all the AMD fanbois claim "Wayland's running perfectly under AMD, all your issues are because you're running Nvidia hardware/drivers..."
Yeah...Nah. The reality is Wayland's still half baked.
I'm on AMD and for me Wayland sucks ass. It's ok until I want to run a game. For example, in order to run Lost Epoch I have to input a launch option to run it in an X11 window and then it hard locks the system if I alt-tab. Now I just login under X11 since it always works and it has me questioning returning the 7900XT and grabbing a 4070ti S or 4080S. I figure that by the time Wayland is actually good it will be ok on Nvidia.
I just installed KDE Neon instead.
Pretty sexy, but getting used to not using apt was a little something else.
When I ran apt it told me no such command. Ended up using pkcon, as pacman gave me the same error as apt.*Cough*
I still use apt under KDE Neon, just not for Wine. Use the Wine Flatpak instead. Although I am trying to switch to mostly Flatpak installs of all my most used software.
When I ran apt it told me no such command. Ended up using pkcon, as pacman gave me the same error as apt.
Hmm. Interesting. So I can't do apt update/upgrade but I can do apt install? Wild world.If you're updating the OS, KDE Neon will inform you to use pkcon. If you're installing software, you can still use apt.
Hmm. Interesting. So I can't do apt update/upgrade but I can do apt install? Wild world.
I want to agree with you, but when I run sudo apt anythinghere it comes back with an unknown command. Maybe I don't have apt installed or something. I'm running the newest KDE Neon iso.You can update using apt, but it isn't recommended. KDE Neon is loosely based on Ubuntu LTS.
The command is apt-get, not apt, iirc.I want to agree with you, but when I run sudo apt anythinghere it comes back with an unknown command. Maybe I don't have apt installed or something. I'm running the newest KDE Neon iso.
I'm not too worried about it.
Thanks for the help!
It used to be many years ago, but it changed to apt. That said, maybe it's apt-get on this distro.The command is apt-get, not apt, iirc.
It used to be many years ago, but it changed to apt. That said, maybe it's apt-get on this distro.
Er...That's odd, something's not right there, as apt is running fine here.I want to agree with you, but when I run sudo apt anythinghere it comes back with an unknown command. Maybe I don't have apt installed or something. I'm running the newest KDE Neon iso.
I'm not too worried about it.
Thanks for the help!
Yeah. I figured it was better than the testing one as I just wanted to test plasma 6 at the time.Er...That's odd, something's not right there, as apt is running fine here.
What version of KDE Neon did you install? It it the User Edition?