4 ms·

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, giv

by samhuk 4y ago

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 :)

apetuskey 4y ago
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.
- samhuk 4y ago
  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 :)
apetuskey 4y ago
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.
- samhuk 4y ago
  Thank you very much for the insight. Best of luck with the future of your project.
- JPKab 4y ago
  Thanks! I asked a question and now see you had already answered it. For those who are curious why these frameworks are great: I'm an experienced full stack developer, and I can write React apps in my sleep and I've used a bunch of different state management frameworks including redux/mobx/etc, but my current startup is a back-end API as a service company and I simply don't have the time to hand-code front-ends with whatever flavor of the month developments in the JS front-end ecosystem. Frankly, I'm sick and tired of the entire front-end ecosystem. It changes too fast for very little gain. So so so so many new tools that empower you but then come with baggage. I don't want to deal with it for some internal apps or basic things like allowing my customers to check their usage balances.... this looks promising!

by samhuk 4y ago

apetuskey 4y ago

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.

samhuk 4y ago
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 :)

apetuskey 4y ago

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.

samhuk 4y ago
Thank you very much for the insight. Best of luck with the future of your project.
JPKab 4y ago
Thanks! I asked a question and now see you had already answered it. For those who are curious why these frameworks are great: I'm an experienced full stack developer, and I can write React apps in my sleep and I've used a bunch of different state management frameworks including redux/mobx/etc, but my current startup is a back-end API as a service company and I simply don't have the time to hand-code front-ends with whatever flavor of the month developments in the JS front-end ecosystem. Frankly, I'm sick and tired of the entire front-end ecosystem. It changes too fast for very little gain. So so so so many new tools that empower you but then come with baggage. I don't want to deal with it for some internal apps or basic things like allowing my customers to check their usage balances.... this looks promising!