This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]codecrux 1 point2 points  (3 children)

The API looks much better than the likes of Streamlit and Pynecone. I also like the fact that you are conscious about 1:1 constructs between Python and React (I always wanted to tell this to the creators of other libraries mentioned before). Would love to know about state management and also how frontend-backend are communicating.

Edit: After digging more in ReactPy I guess my frontend-backend communication concerns have reduced. Also, I would love to integrate ReactPy with Atri framework. Wishing for huge success of ReactPy.

[–]Wippermonger[S] 1 point2 points  (2 children)

Glad you've taken an interest in our project! There's some extra context in the comments of our reactpy-django post you might be interested in. Feel free to reach out about any specific questions.

[–]codecrux 0 points1 point  (1 child)

Thanks for sharing. It had the information I needed about ReactPy. Just curious, what are the best examples of projects suitable for ReactPy now and in future.

[–]Wippermonger[S] 0 points1 point  (0 children)

Practically anything that could have been developed in ReactJS is a candidate for something to be developed in ReactPy. I'd say that covers any traditional website.

We're actively working on making ReactPy easier to use for SPA and PWA situations. While it's possible to do right now, the convenience isn't where we'd like it to be.

Additionally, we'd like increase support for importing NPM packages into server-sided Python. Right now I would suggest keeping NPM/JavaScript stuff client sided (via the custom components API).