3 ms·
Terrible choice for a license. I never go near AGPL.
by dcgudeman 5y ago
Terrible choice for a license. I never go near AGPL.
- _def 5y agoWhy?
- skinkestek 5y agoBecause most of us aren’t in a position where we can give away our code. There is a minefield regarding using AGPL servers and I prefer working around it. If I build AGPL code into my code or vice versa however it becomes very clear as far as I cam see: I have to provide a download link to the entire product. For many of us that is not an option: My clients would of course reject that, and of course I would not use it for my own for-profit projects either.
- OJFord 5y agoI realise it's probably still no-go for enterprise, but from 'how it works': > Pglet UI does not become embedded into your program, but is being served by an out-of-process Pglet server. Which seems aimed at addressing what you need to share and under what circumstances.
- formerly_proven 5y agoIt's dubious and untested whether the "but it's an external process" defense works against AGPL, especially when you're writing your program literally against the API of the project. It also seems inaccurate given the example from the README: . pglet.sh PGLET_WEB=true pglet_page pglet_add "text value='Hello, world!'" Clearly code from the project (pglet.sh) is embedded directly into your "application".
- skinkestek 5y ago> but is being served by an out-of-process Pglet server. Then I guess it is a server and not a framework? And if it is it only means we are going from well defined non-commercial and into the minefield that is using AGPL servers in a commercial setting?
- frou_dh 5y agoPresumably someone who chooses AGPL intentionally wants to exclude people who "won't go near AGPL", in which case this can't be a terrible choice, by construction.