Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

news.ycombinator.com

Post reply on HN
Print view View original

51–60 of 329 posts

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#51

Post by paulgb »

unmole wrote: post #50
ShakataGaNai wrote: post #38

Love the idea. As someone who's not trying to build The Next Big Thing (TM), but just get some stuff done - I appreciate the focus on the basics. A lot of the python webui's are heavily focused on AI/ML related stuff, which is cool - but what about those of us who just want to build an internal tool that does 5 specific things and nothing more? I try to avoid javascript if at all possible, so "python front to back" i…

> A lot of the python webui's are heavily focused on AI/ML I'm sorry, what?

I assume GP is referring to frameworks like Gradio (https://gradio.app/) and to a lesser extent Streamlit. Existing web UI frameworks for Python are somewhat opinionated around particular use cases, of which AI/ML is a prominent one.

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#52

Post by LifeIsBio »

I haven't seen anyone mention Anvil[1] yet, but it lets you "Build web apps with nothing but Python." and is lovely tool that I've successfully used for a handful of side projects.

But as someone who feels most at home with Python, I always love to see new competition in this space.

[1] https://anvil.works/

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#53

Post by apetuskey »

buremba wrote: post #47

The API seems pretty similar to Streamlit, another library to create data apps with Python Given thar it’s more popular compared to Pynecone based on Github, how do you plan to differentiate? I would love to hear about the way that you compile to NextJS because that’s a challenge with Streamlit. I have looked into your docs for custom components but I wonder if it’s possible to use compiled NextJS and bring my custom…

I think the biggest differentiation is that Pynecone apps are completely customizable and don't re render based on State changes. Streamlit is great for dashboard type apps but when you want to expand on your app you can be limited in terms of flexibility and customizability. The whole Pynecone website is made in Pynecone vs other frameworks like streamlit cannot do this because they are limited in what they can build.

See here for bringing your own components: https://pynecone.io/docs/advanced-guide/wrapping-react

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#54

Post by samhuk »

My only interaction in this space is helping out a friend of mine with Streamlit.

I'm surprised you haven't mentioned anything about it in your HN comment, given it seems, at least on the face of it, extremely similar.

Are you able to go into a bit more detail about why Pynecone and not others?

Did you ever consider contributing to Streamlit instead or forking it? if so, why didn't that work out? What do you do better? Etc.

Disclaimer: I'm not too knowledgeable about this niche, however, so if I'm very off-base here then please let me know :)

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#55

Post by paulgb »

picklelo wrote: post #49
RyEgswuCsn wrote: post #40

I like it. Reminds me of Vaadin and friends. One question regarding the states: when do I get a new State allocated? Is it with every new tab? It's definitely not per-browser-session: if I open a new tab I seem to get a new state, while undoing a closed tab seems to recover its state with it though. Also are old states gc'ed?

Each new browser tab creates a new state. We use Redis to store the state and expire it after 30 minutes.

Does that place some restrictions on what can be done with the state? e.g. does it need to be pickleable and relatively small since it needs to be loaded from redis on every event?

(Pretty cool, btw! Congrats on the launch)

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#56

Post by mynegation »

unmole wrote: post #50
ShakataGaNai wrote: post #38

Love the idea. As someone who's not trying to build The Next Big Thing (TM), but just get some stuff done - I appreciate the focus on the basics. A lot of the python webui's are heavily focused on AI/ML related stuff, which is cool - but what about those of us who just want to build an internal tool that does 5 specific things and nothing more? I try to avoid javascript if at all possible, so "python front to back" i…

> A lot of the python webui's are heavily focused on AI/ML I'm sorry, what?

They probably meant that most of the time Web UI is implemented in Python, it is by someone who does not care much about design and complicated interactions and does not want to learn JavaScript, it is someone doing AI/ML who just wants some buttons, sliders and charts to quickly experiment. Gradio, which is similar to Pynecone, explicitly targets this audience and frameworks like Streamlit and Dash are also used by AI/ML community.

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#57

Post by apetuskey »

samhuk wrote: post #54

My only interaction in this space is helping out a friend of mine with Streamlit. I'm surprised you haven't mentioned anything about it in your HN comment, given it seems, at least on the face of it, extremely similar. Are you able to go into a bit more detail about why Pynecone and not others? Did you ever consider contributing to Streamlit instead or forking it? if so, why didn't that work out? What do you do bette…

I posted an answer to this in one of the other comments but in short Pynecone is much more customizable and flexible in terms of what your can build.

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#58

Post by samhuk »

apetuskey wrote: post #57
samhuk wrote: post #54

My only interaction in this space is helping out a friend of mine with Streamlit. I'm surprised you haven't mentioned anything about it in your HN comment, given it seems, at least on the face of it, extremely similar. Are you able to go into a bit more detail about why Pynecone and not others? Did you ever consider contributing to Streamlit instead or forking it? if so, why didn't that work out? What do you do bette…

I posted an answer to this in one of the other comments but in short Pynecone is much more customizable and flexible in terms of what your can build.

Just read it. Thanks!

I agree that Streamlit was very limited feature-wise. Basically for extremely simple PoCs, etc.

I like how you dog-food Pynecone for Pynecone's website :)

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#59

Post by apetuskey »

samhuk wrote: post #54

My only interaction in this space is helping out a friend of mine with Streamlit. I'm surprised you haven't mentioned anything about it in your HN comment, given it seems, at least on the face of it, extremely similar. Are you able to go into a bit more detail about why Pynecone and not others? Did you ever consider contributing to Streamlit instead or forking it? if so, why didn't that work out? What do you do bette…

We didn't consider forking it because our architecture if fundamentally different. This allows us to customize our apps more and make larger apps. We compile down to a react/next app vs streamlit who uses tornado and has to re-render based on changes to the app.

I think the idea's behind the projects are a little different. Streamlit - small data science apps vs Pynecone - A more generalized framework to built a broader range of applications.

Re: Launch HN: Pynecone (YC W23) – Web Apps in Pure Python

#60

Post by samhuk »

apetuskey wrote: post #59
samhuk wrote: post #54

My only interaction in this space is helping out a friend of mine with Streamlit. I'm surprised you haven't mentioned anything about it in your HN comment, given it seems, at least on the face of it, extremely similar. Are you able to go into a bit more detail about why Pynecone and not others? Did you ever consider contributing to Streamlit instead or forking it? if so, why didn't that work out? What do you do bette…

We didn't consider forking it because our architecture if fundamentally different. This allows us to customize our apps more and make larger apps. We compile down to a react/next app vs streamlit who uses tornado and has to re-render based on changes to the app. I think the idea's behind the projects are a little different. Streamlit - small data science apps vs Pynecone - A more generalized framework to built a broa…

Thank you very much for the insight. Best of luck with the future of your project.
Post reply on HN