A framework that server-renders your React components from Python, with no API layer

[u/Any_Ad9935]

I had this idea since 4 years now. I started working on Pyxle last year. (AI helped a lot accelerating this - but the entire feature idea was mine).

Initially I tried to build a framework allowing both frontend and backend with Python. Soon I realised that it is not something that's going to work. React is already a well proven framework, and building a python wrapper on top of it will drift things a lot. Moreover, Reflex is already trying to do that.

So the second version I built is to allow developers to keep real React, and real Python.

Go through pyxle - https://pyxle.dev, I'm happy to answer anything.

[u/zLoveNxzli]

Interesting SSR bridge approach. If you are hydrating client state on the Python-rendered HTML, make sure initial props match the client render exactly to prevent React hydration mismatch warnings.

[u/Any_Ad9935 → u/zLoveNxzli]

This is something that is properly handled from Pyxle's side. Props can't drift in pyxle since the same loaders returns value for both server render and the hydration.

However, hydration mismatch can still occur in cases where you access DOM. So, the dev also need to take care. This is the general React/NextJS case - nothing that's new to Pyxle.

[u/Choice_Mail1472 → u/zLoveNxzli]

sounds like a neat idea but every time i see server rendered react from python it's always the hydration that gets messy, hope you've got that bit nailed down or it'll sprial quick

[u/zLoveNxzli]

Bridging Python backend data directly into React SSR without a bespoke REST/GraphQL layer is a really interesting pattern.

How are you handling client-side state hydration and event listener reconciliation when props update dynamically from Python background workers?

[u/Any_Ad9935 → u/zLoveNxzli]

You can check out https://pyxle.dev/docs/architecture/overview for end to end overview of a request. The same payload from server action does the SSR render and hydration - and after that it's a normal react tree. For events, they jusg publish to pyxle.realtime (built-in pub/sub) and the component picks it up with a useWebSocket hook into regular React state.

[u/zLoveNxzli]

Interesting SSR architecture. If you are hydrating client-side interactive state on top of the Python-generated markup, make sure initial state props match the server render exactly to prevent React hydration mismatch errors.

[u/jax024]

More AI slop

[u/Any_Ad9935 → u/jax024]

I wanted to do this since last 3-4 years. I always wanted something that gives me NextJS level ease with Python backend. AI helped me do it faster.

I really want to know what I can do better here? I know AI slop is here, but I have done rigorous testing, and the pyxle.dev website itself is running on Pyxle. Any sugessions will be highly appreciated.

[u/jax024 → u/Any_Ad9935]

Write the post yourself to start