Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ReactPy VS PyneCone #988

saurabhwadekar started this conversation in General
Discussion options

ReactPy VS PyneCone

You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

In general, my argument against PyneCone is that it relies on what (from what I can tell) is an outdated Model-View-Controller (MVC) strategy for state management. Over time, frontend developers have found that MVC just doesn't scale well. Wherever possible, ReactPy tries to replicate the well-liked and battle-hardened interfaces pioneered by ReactJS.

With that said, it seems like PyneCone, as it says, comes with a few more "batteries included" - for example, a database and built-in components based on Chakra UI. This comes at the cost of some flexibility though of course.

You must be logged in to vote
1 reply
Comment options

For example, due to ReactPy's modular construction, it can run in a variety of different contexts (e.g. Django and Jupyter Notebooks). This allows you to write your components once, and use them anywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /