This looks interesting! I want to try it out for a project we are working on, but we would need some of the features like callers, doctoring, and typing
https://reflex.dev/ is all made in Reflex and has raised a seed round! There are also a few YC companies using Reflex that have raised seed rounds too.
We do use nextjs but I think what's the most handy part of Reflex is the simplification of state management and event handling so there is more complexity to the framework.
Yeah I see your point it's definitely something we are going to try and reduce in the future. We wanted to give the users the ability to wrap external react components and leverage that ecosystem so there were trade off we had to make.
The 3MB of JS is in dev mode or prod mode? (Is this similar to the other comment where they were running in dev mode but when they ran in prod it was much smaller ~ 340KB?)
We have 5 badges in total, and 1 of them to points to our integrations test passing. And the integration test do serve an important purpose in making sure we are compatible on multiple different os and don't make a change that would break WSL for example. More info here https://github.com/reflex-dev/reflex/tree/main/.github/workf...
The others are the current latest version, python version we support, how many people are on our discord (A metric to see community activity), and a badge that points to our docs. I think all of these are important but open to suggestions on ones you think would serve a better purpose.
Will be improved in the future as we start to offload client side actions with wasm, starting to do this but the python wasm ecosystem is still maturing
Agree a little different approaches, we found many developers wanted to stick with a 100% code approach and avoid the constraints of using an online drag and drop builder like retool/anvil etc. Instead opting to stick a traditional code tech stack that provides benefits like easier version control with ui and reviews with larger teams. Where as with a low code tool you are now forced to develop on the ui platform and locked in by the vendor.
We have also had some users build some fairly large Pynecone apps including our whole website built in our own framework.
Pynecone comes with a built in sqlite database on the server only not on the browsers. you can also easily connect to any external db by changing the pcconfig
We are working on improving the performance, we are still pretty new but there are a few different ways we can speed state updates up. For state updates like pressing the counter a lot of times it can been seen, we will improve this.
Thanks! We are in the process of making it faster, the projects still new and there's a lot of different ways we can improve and speed things up. Especially since we want to start incorporating web assembly in the future.
What is the timeline on the coming soon features?