4 ms·
I 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 o
by OJFord 5y ago
I 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?