Thoughts on porting Fabric to Python?

[andreamancuso]

Hello!
First of all, let me tell you how impressed I am to see what you guys accomplished with ReactPy. Seriously ambitious and amazing.

I understand based on this answer that you've a bigger fish to fry at the moment, however I still would like to ask: what if somebody wanted to port https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Renderer/implementations/ReactFabric-prod.js to Python (primarily this file, not the entire React Native ecosystem), where/how would you start?
Have you written a reconciler algorithm?

Cheers!

[Archmonger]

I haven't read the react fabric source code. However, implementation of anything React-Native related is going to need tinkering with the ReactPy Client.

I don't see a world where anything React-Native related could be server-side rendered, so client-side components would need to get ported to ReactPy core first. Currently, client-side components only exist in Django due to convenience (specifically due to Django having built-in template tags and settings framework).

In summary, to get React Native running within ReactPy the "order of operations" would be the following:

1. Embedding ReactPy via Template Tags #653
2. Client Side Python Components #110
3. Run ReactPy as a Native App #570

[Archmonger]

As a note about the template tags, someone has an open PR in reactpy-django that is functional and utilizes Jinja template tags. This is convenient because Jinja is exactly what ReactPy core will eventually use for template tags. If I recall, the merge blocker for that PR was a lack of tests. It is likely very easy to shove that source code into ReactPy core and add some tests.

Then regarding client-side components, it would also be an exercise in mostly copy-pasting the following from ReactPy-Django: 1, 2, 3, 4, 5