Given how vocal anti-snap people are, I just wanted to provide a voice in favour of snap. It's always my preferred method of install for anything not in the default archives.
That being said, I was wondering how many people actually find the Snap system and ecosystem useful. Reverse engineering snapd (which is licensed under GPLv3) and snap app format in order to create a compatible server would be a fun project.
I believe that the Canonical Snap server is hardcoded into snapd, so even if someone did implement their own you would need to recompile snapd to even use it.
So you're saying signal requested their own program be removed from the snap store? Sorry, I'm a little confused on terms. When you say snap maintainer, are you saying you are the maintainer of the signal snap package, or that you're a maintainer of snap itself?
If it the popey from podcasts he used to work at Canonical. Actually looking at this confused, popey also came up with the snap removal tool that is handy https://github.com/popey/unsnap
Maybe he has a love hate relationship with snaps lol
I just used it at work to build an ad server. For a web app that has a few well defined features, Snap is awesome and fast, and working in Haskell is totally a joy. It doesn't have the high level functionality that a web framework like rails or django has though. (yet)
Unfortunately, I used the old Snap extension API since the new snaplet API wasn't around when I started! So maybe if I have some time I'll refactor it to use the new API, which looks like it's a lot better than the old extension API.
One cool thing is if you statically link your binary and build on ubuntu 10.04, you can actually just directly deploy binaries to Heroku, even though it's not a supported language. Just throw in a package.json file or whatever to trick Heroku and specify your Snap binary in your Procfile.
reply