So now I have to search on the web to find how to run it from the command line. It feels like going back 20 years.

~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.8G     0  7.8G   0% /dev
tmpfs           1.6G  1.6M  1.6G   1% /run
/dev/sda4        39G   12G   25G  33% /
tmpfs           7.8G   92M  7.7G   2% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/loop2       78M   78M     0 100% /snap/knowte/2
/dev/loop1      163M  163M     0 100% /snap/gnome-3-28-1804/145
/dev/loop3       56M   56M     0 100% /snap/core18/1885
/dev/loop6      384K  384K     0 100% /snap/bpytop/147
/dev/loop4       61M   61M     0 100% /snap/core20/634
/dev/loop5       98M   98M     0 100% /snap/core/10185
/dev/loop7       78M   78M     0 100% /snap/knowte/3
/dev/loop8       63M   63M     0 100% /snap/gtk-common-themes/1506
/dev/loop9       57M   57M     0 100% /snap/bitwarden/31
/dev/loop10     162M  162M     0 100% /snap/gnome-3-28-1804/128
/dev/loop11      76M   76M     0 100% /snap/vitomu/2
/dev/loop12      98M   98M     0 100% /snap/core/10126
/dev/sda5       499G  108M  498G   1% /files
/dev/sda3        39G   49M   37G   1% /tmp
/dev/sda1       288G  129G  144G  48% /home
/dev/sda7        33G   49M   31G   1% /other
tmpfs           1.6G   20K  1.6G   1% /run/user/1000
/dev/loop13     384K  384K     0 100% /snap/bpytop/152
/dev/loop14      56M   56M     0 100% /snap/core18/1932

@dragonmouth

There is a lot of word about why it would be to your benefit to switching from the simplicity of distro repositories to the complex structure of Snaps. As mentioned in the first article, snaps are easy to install across Linux distributions, they are also secure by default due to the way they run on a Linux system, and they support snapshots and many other useful features described in that article. Every package management system has its advantages and disadvantages, so you can give snap a try, maybe you will like it.

@Rob

It’s the usual idea of applications running in the background as a daemon or services, just like managing (starting, enabling, etc.) services under systemd or any other init system. Snapd just manages its services (apps beneath a snap designed to run in the background as a daemon) independently from the main system and services manager.

Having those services start at boot up sounds like Windows too.

The alias feature is a semi +1.