3 ms·
Aseprite uses the sell the binaries model. It's open source but you have to compile it yourself (and it has many dependencies). I've tried getting things to com
by andai 4y ago
Aseprite uses the sell the binaries model. It's open source but you have to compile it yourself (and it has many dependencies). I've tried getting things to compile before and I consider it about as appealing as a visit to the dentist (only longer and more painful!) so I just forked over the cash.
- pabs3 4y agoAsesprite is is shared source, not open source. https://dev.aseprite.org/2016/09/01/new-source-code-license/ https://dev.aseprite.org/2016/09/01/new-source-code-license/ https://bugs.debian.org/864990 https://bugs.debian.org/864990 https://github.com/aseprite/aseprite/blob/main/EULA.txt https://github.com/aseprite/aseprite/blob/main/EULA.txt https://opensource.org/osd https://opensource.org/osd
- austinjp 4y agoInteresting. A sort of "sell convenience" model. I'm a bit out of this loop, but isn't this how several SaaS/PaaS operators work? Provide open-source software but offer paid-for solutions such as hosting and/or support?
- _fjb4 4y agoAs stated by another user it's not true open source, the source is solely available for personal use and for the submission of patches back to the author. Such a model can backfire though as it would appear to be legal for a third-party contributor to create a set of scripts that would compile and prepare the application (load all the dependencies in a container and so forth) and release those scripts. Those scripts could even become accepted by a Linux distro's package manager, similar to how package managers package freeware prop software by using a script to legally grab the binary from the developer's site and installing it.
- jtsiskin 4y agoWhat I dislike about this model is it incentivizes insane and complicated build processes. You’re incentives not to make a simple docker image
- fomine3 4y agoSynergy was like that too, but GPL.