Updated a couple of days ago. Two things broke: screen resolution on boot and weirdly enough Super key doesn't trigger applications menu when non-english keyboard layout is selected. Otherwise --...
Updated a couple of days ago. Two things broke: screen resolution on boot and weirdly enough Super key doesn't trigger applications menu when non-english keyboard layout is selected. Otherwise -- a great release. I won't be using tiling, but it's a nice additions for those who want it. Also I'm especially thankful for the missing Snaps from Ubuntu
I'm excited to upgrade (don't worry @pseudolobster, I haven't done it yet!). I've been very happy with Pop!_OS so far, and I'm excited to try the new tiling feature since I only have one monitor...
I'm excited to upgrade (don't worry @pseudolobster, I haven't done it yet!). I've been very happy with Pop!_OS so far, and I'm excited to try the new tiling feature since I only have one monitor and I'm always manually splitting windows in half already.
In other discussions of this release and Ubuntu at large, I've seen a bit of friction between Ubuntu's path to follow Snaps for installations versus Pop!_OS's decision to support Flatpak and .debs. As a new Linux user and lay computer user, these back-and-forths are a bit opaque to me. Can anyone with more perspective on this shed some light on one versus the other?
Flatpak is widely supported while Snap is Canonical's in-house solution; some of its features such as sandboxing don't work in most distributions—not sure if it works on Pop since it's based on...
Flatpak is widely supported while Snap is Canonical's in-house solution; some of its features such as sandboxing don't work in most distributions—not sure if it works on Pop since it's based on Ubuntu. Its server is also proprietary, so you are locked in to Canonical's while Flatpak is FOSS on both the client and server side and doesn't push Flathub on you; if I remember correctly, you have to manually add it as a server just like any other.
deb is Debian's package format and is used by all of its derivatives, including Ubuntu, although I'm guessing that they want applications outside of the official repositories to be distributed through Snap instead of deb files. It's nice and minimal, but can have troubles with dependencies when distributed unofficially since it uses the package manager to install them and isn't cross-platform.
EDIT: Here's a discussion on it with an answer from an official Pop!_OS developer.
This was very helpful, thank you! From my minimal understanding, it looked like Snaps and Flatpaks were two different implementations of the same thing. I had no idea Snaps were proprietary.
This was very helpful, thank you! From my minimal understanding, it looked like Snaps and Flatpaks were two different implementations of the same thing. I had no idea Snaps were proprietary.
Just to clarify, the Snap client is open source; however, the server is proprietary and I don't think there's any way to host your own. It looks like you also have to sign a CLA to contribute to...
Just to clarify, the Snap client is open source; however, the server is proprietary and I don't think there's any way to host your own. It looks like you also have to sign a CLA to contribute to the client, which as far as I know allows them to relicense the client to be proprietary as well in the future despite it being GPL.
Honestly, I just avoid both. My hard drive is not infinite, and flatpaks/snaps tend to eat a lot of space, while not providing me with anything of substantial value: I rarely if ever bump into...
Honestly, I just avoid both. My hard drive is not infinite, and flatpaks/snaps tend to eat a lot of space, while not providing me with anything of substantial value: I rarely if ever bump into dependency issues, and pretty much all of the apps installed are trustworthy enough, so I don't feel the need to sandbox them
Updated a couple of days ago. Two things broke: screen resolution on boot and weirdly enough Super key doesn't trigger applications menu when non-english keyboard layout is selected. Otherwise -- a great release. I won't be using tiling, but it's a nice additions for those who want it. Also I'm especially thankful for the missing Snaps from Ubuntu
Turns out it's a GNOME bug that causes Super to work only on first and fourth keyboard layout. Go figure
I'm excited to upgrade (don't worry @pseudolobster, I haven't done it yet!). I've been very happy with Pop!_OS so far, and I'm excited to try the new tiling feature since I only have one monitor and I'm always manually splitting windows in half already.
In other discussions of this release and Ubuntu at large, I've seen a bit of friction between Ubuntu's path to follow Snaps for installations versus Pop!_OS's decision to support Flatpak and .debs. As a new Linux user and lay computer user, these back-and-forths are a bit opaque to me. Can anyone with more perspective on this shed some light on one versus the other?
Flatpak is widely supported while Snap is Canonical's in-house solution; some of its features such as sandboxing don't work in most distributions—not sure if it works on Pop since it's based on Ubuntu. Its server is also proprietary, so you are locked in to Canonical's while Flatpak is FOSS on both the client and server side and doesn't push Flathub on you; if I remember correctly, you have to manually add it as a server just like any other.
deb is Debian's package format and is used by all of its derivatives, including Ubuntu, although I'm guessing that they want applications outside of the official repositories to be distributed through Snap instead of deb files. It's nice and minimal, but can have troubles with dependencies when distributed unofficially since it uses the package manager to install them and isn't cross-platform.
EDIT: Here's a discussion on it with an answer from an official Pop!_OS developer.
This was very helpful, thank you! From my minimal understanding, it looked like Snaps and Flatpaks were two different implementations of the same thing. I had no idea Snaps were proprietary.
Just to clarify, the Snap client is open source; however, the server is proprietary and I don't think there's any way to host your own. It looks like you also have to sign a CLA to contribute to the client, which as far as I know allows them to relicense the client to be proprietary as well in the future despite it being GPL.
Honestly, I just avoid both. My hard drive is not infinite, and flatpaks/snaps tend to eat a lot of space, while not providing me with anything of substantial value: I rarely if ever bump into dependency issues, and pretty much all of the apps installed are trustworthy enough, so I don't feel the need to sandbox them