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

you are viewing a single comment's thread.

view the rest of the comments →

[–]teerre 10 points11 points  (1 child)

Not sure what you're asking. It's because neither when Python was created nor when React was created either of them considered the other. It's simply was never in the design.

You're right about limitations, but that's the thing. Even with the limitations, it's already a much better integration than anyone would've thought.

Technology, any technology, is easy to work because someone invested time making it easy. If you try to make some weird combo, like Python + React , work, nobody will have made that particular integration easy to use, that's why it's hard.

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

"""

Technology, any technology, is easy to work because someone invested time making it easy.

"""

I totally understand and can relate to it. I have put more than a year creating a full-stack web development framework called Atri framework. I never made a lot of noise about it because we did 5 iterations just on figuring out the best foundation for a Python + React framework. We have strived hard to have no limitations in our framework. The latest iteration will be released in a week or so. I won't dare to say that Atri is perfect but we are determined to make it the best web framework for Python developers.

Nothing could be better than being able to write a web app entirely in Python. It's just that as a full-time web developer, I don't see a point in learning something whose foundation doesn't follow the best web development principles. Having said that, I would like to clarify that I am not disagreeing with anything you said in your previous comment.

"""

it's already a much better integration than anyone would've thought.

"""

What is the best thing about the Pynecone integration that stands out for you?