Item — HN Reader

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.

2 comments

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!

Thank you very much for the insight. Best of luck with the future of your project.