It's meant for people who prefer their apps from the official sources rather than repackaged. All this script dies is make it easy so you don't have to google the app's name and search for an install method on its website.
That's a good point. I will also probably need a better update method than rm -rf-ing the files and replacing them with each update.
Could you elaborate? I'm not the best programmer so I'm open to suggestions.
But why choose snap only? Flatpak works on Ubuntu just fine, and on other distros obviously, so they could just choose that. Blender only officially support snap too. Vivaldi for example made a blog post about how snap has better sandboxing of chromium. https://social.vivaldi.net/@ruario/113164179328218870
Yep. I did automate it the best I could (I'm not creating entries for thousands of apps manually) but it will indeed require manual maintenance as the apps will change their installation methods over time.
Those are all official sources tho, but you have to trust me not to put in malicious commands of course.
I understand that people treat snap as if it was a contagious virus but the developers chose the method purposely. A lot of KDE apps are only distributed as snaps for example, k3b comes to mind. VLC as well.
There are flatpak versions but they aren't official, which defeats the point a bit.
I do however plan to somehow add the ability to prefer flatpak, since a few of the entries have both a flatpak and snap field.
Thank you, and fair enough.
Which one?
Everything else is FOSS besides the server and snaps can even be installed locally. I wrote a section of an article about most of the complaints. Most of the complaints I hear are just elitistic bullshit that makes new users confused and spreads misinformation.
I very much hope not. Luckily they seem to be doing well.
If you want to build from source, this brings nothing of value. Nix has pretty much everything.