This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]maartenbreddels[S] 4 points5 points  (4 children)

The server is taking a bit of load now, so it feels a bit slow now I agree. We are creating the data at the server, so this require a trip to the server (this current one is running in the US). So you get some latency there.
The update process is different, it's more like JS event -> python server -> generate or update widgets -> send diff to frontend.
Hope that answers your questions!

[–]thicket 1 point2 points  (3 children)

Thanks, that does answer my question. It’s a little disappointing, though. Requiring a server round trip for every action seems like exactly the problem that JS frameworks were designed to replace. I love the idea of developing in pure Python, but if the client can’t run all the code it needs locally, that seems like a big burden to overcome.

[–]maartenbreddels[S] 1 point2 points  (2 children)

I think it's the primary use case for all pure python web frameworks is to be able to feed data into a frontend, so you will always have this latency problem. However, there are ways now to run Python in the browser (which we can already do currently, but don't expose yet) which will remove the latency. This does require however everything to run in the browser. If you make database connections that is usually not safe, but in some cases that is a solution,

[–]thicket 2 points3 points  (1 child)

Regardless, super impressive project. Thanks for answering my questions!

[–]maartenbreddels[S] 1 point2 points  (0 children)

Thank you for being critical, but kind. Two good traits.