While I applaud the attempt, stating it's "performant" is misleading, as any calculation that could happen client side means a call to the network with Pynecone

While I applaud the attempt, stating it's "performant" is misleading, as any calculation that could happen client side means a call to the network with Pynecone. You can see it in their demo: https://pynecone.io/docs/getting-started/introduction https://pynecone.io/docs/getting-started/introduction The counter increment should be instantaneous, but instead, it goes through websocket, calls a python function on the server, and comes back. In which case the difference between this and django+htmx is not huge: mostly you get widgets in pure Python, and websocket is not experimental. Not sure it's worth giving up the whole django and htmx community to get locked in their widget set. I'm not saying this to hit on the project, I do think pycone is a cool idea and it's nice to see people trying to make web dev more accessible. But I want people to know what they are signing for.