Live data from Hacker News

Pglet – Web UI framework for back end developers

github.com

21–30 of 37 posts

Re: Pglet – Web UI framework for back end developers

#21
post #18

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.

It'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".

Re: Pglet – Web UI framework for back end developers

#23
post #18

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.

> 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?

Re: Pglet – Web UI framework for back end developers

#28

Why isn't it just called Piglet?

already exists: https://ollycope.com/software/piglet-templates/latest/

also this one is very popular too: http://pyglet.org/

I would personally avoid the current name as it sounds phonetically the same as the above.

Re: Pglet – Web UI framework for back end developers

#29
post #27

Show me a demo of double binding data table with async loading, filters, sorters and groupers then we'll talk.

i'm convinced two-way binding is an anti-feature in reactive UI. bindings should flow one way from model to view, and view changes should be reflected back to the model via events.

Re: Pglet – Web UI framework for back end developers

#30
post #10

I wish there was a Go client. Sad that the server is Go but they dont have any released Go bindings.

Looks like there's a Go client here https://github.com/pglet/pglet-go

Just looked through the source, that is not a client! There is only a constructor to create a "Page" but the page has no methods, and there is nothing else exported.
Post reply on HN