Pynecone – Performant, customizable web apps in pure Python
1–10 of 86 posts
Re: Pynecone – Performant, customizable web apps in pure Python
#2It’s just Python.
The app state is just a class. State updates are methods in the class. And the UI is a reflection of the state.
It's rare to see this sort of clarity on a landing page. Even more impressed to see that it carried over into the documentation, which is excellent.
I've been a fan of the plotly/Dash framework, but this looks like an exciting alternative, feeling more immediately accessible without some of the quirks (like the pragmatic but weird-feeling 12 virtual columns, for example). I look forward to re-implementing some existing projects for comparison.
Re: Pynecone – Performant, customizable web apps in pure Python
#3for a second i read this as Pinecone, that 700m vector database
Re: Pynecone – Performant, customizable web apps in pure Python
#4Seems like a more ambitious Streamlit
Re: Pynecone – Performant, customizable web apps in pure Python
#5It's a beautiful project and close to the Holy grail of fullstack software development (a single framework for building modern Web apps).
But, be advised that it's not production ready and quite unstable yet.
this week my deploy script was broken because version 0.1.26 was un-released. Which broke my docker file build with pinned dependencies.
The file upload component was changed a few times so my UI with file uploads silently stopped working.
I had some issues when state binding input components. Which lead to the backspace key no longer working inside a text box.
The websocket state updates can make the ui feel sluggish.
Despite all that, I love this framework and will continue tinkering with it. It hope it can grow to maturity before people lose interest!
Re: Pynecone – Performant, customizable web apps in pure Python
#6This looks awesome! Has anyone made a personal portfolio site/ blog with this yet? Considering jumping from Jekyll: https://jeffreylikeswebsites.com
Re: Pynecone – Performant, customizable web apps in pure Python
#7It’s just Python. The app state is just a class. State updates are methods in the class. And the UI is a reflection of the state. It's rare to see this sort of clarity on a landing page. Even more impressed to see that it carried over into the documentation, which is excellent. I've been a fan of the plotly/Dash framework, but this looks like an exciting alternative, feeling more immediately accessible without some o…
I would love to hear what your experience is.
We've been using Pynecone for a bit and are coming up against some problems.
For example trying to write a wrapper for AG Grid there is no way to pass a custom class attribute so you can't style the output with a theme.
Re: Pynecone – Performant, customizable web apps in pure Python
#8I followed the link to try the increment/decrement example/demo from the landing page (https://pynecone.io/docs/getting-started/introduction). There is probably almost a full one second delay between the time I click the "increment" button and the updated count being rendered.
Not seeing any network requests so I can't imagine why it would be so laggy.
Re: Pynecone – Performant, customizable web apps in pure Python
#9I followed the link to try the increment/decrement example/demo from the landing page ( https://pynecone.io/docs/getting-started/introduction ). There is probably almost a full one second delay between the time I click the "increment" button and the updated count being rendered. Not seeing any network requests so I can't imagine why it would be so laggy.
Clicking sends a websocket message to the backend. Which then responds with a state update message which updates the frontend react components.
rhe round trip would probably take the same time with rest APIs, but you would have the ability to add some loading indicators or hints, because you'd have full control over client side rendering. You don't have that when using pynecone. It's a tradeof
Re: Pynecone – Performant, customizable web apps in pure Python
#10I followed the link to try the increment/decrement example/demo from the landing page ( https://pynecone.io/docs/getting-started/introduction ). There is probably almost a full one second delay between the time I click the "increment" button and the updated count being rendered. Not seeing any network requests so I can't imagine why it would be so laggy.
Clicking sends a websocket message to the backend. Which then responds with a state update message which updates the frontend react components. rhe round trip would probably take the same time with rest APIs, but you would have the ability to add some loading indicators or hints, because you'd have full control over client side rendering. You don't have that when using pynecone. It's a tradeof
Ah thanks, I see that now under the State -> Overview docs page:
All user state is stored on the server. Behind the scenes, events are sent as API calls to update the state on the server. The state delta is then sent to the frontend, which updates the UI to reflect the new state.