Earlier quoted context omitted.
Because 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 i…
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.
. 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".