React, but in Python • Hacker News Board

Re: React, but in Python

#11

Post by ivoflipse » Tue, Jun 06, 2023, 5:34 PM UTC

Shameless plug for a similar project called Collagraph (https://github.com/fork-tongue/collagraph).

From the README: Write your Python interfaces in a declarative manner with plain render functions, component classes or even single-file components using Vue-like syntax, but with Python!

  - Reactivity (made possible by leveraging observ)
  - Function components
  - Class components with local state and life-cycle methods/hooks
  - Single-file components with Vue-like syntax (.cgx files)
  - Custom renderers

Currently there are two renderers:

PysideRenderer: for rendering PySide6 applications PygfxRenderer: for rendering 3D graphic scenes with Pygfx

It is possible to create a custom Renderer using the Renderer interface, to render to other UI frameworks, for instance wxPython, or even the browser DOM.

Re: React, but in Python

#12

Post by recursive » Tue, Jun 06, 2023, 5:39 PM UTC

uhtred wrote: post #2

I thought generating html from function calls went out with the dinosaurs. We back doing it again?

I mean, react does it. It never left. JSX compiles to function calls.

Re: React, but in Python

#13

Post by ledauphin » Tue, Jun 06, 2023, 5:42 PM UTC

paulddraper wrote: post #10

I'm lost. React builds interactive UIs (web, mobile). After each interaction, the virtual DOM is programmatically recreated and reconciled to the actual DOM. But reactpy is running on a backend sever??? Is each interaction resulting in a server call? Can someone explain what is going on? EDIT: Ah, okay, thanks. Every re-render is a network call. If people complained about web UI performance before..... :)

yes, from reading the docs, there's a websocket.

Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. And in many cases it's what SPAs do as well.

Of course, it depends what counts as an 'interaction', but that's been the case since JavaScript existed.

Re: React, but in Python

#14

Post by rch » Tue, Jun 06, 2023, 5:43 PM UTC

paulddraper wrote: post #10

I'm lost. React builds interactive UIs (web, mobile). After each interaction, the virtual DOM is programmatically recreated and reconciled to the actual DOM. But reactpy is running on a backend sever??? Is each interaction resulting in a server call? Can someone explain what is going on? EDIT: Ah, okay, thanks. Every re-render is a network call. If people complained about web UI performance before..... :)

Sounds like Elixir LiveView.

Re: React, but in Python

#15

Post by jcadam » Tue, Jun 06, 2023, 5:53 PM UTC

Perhaps a Tkinter replacement, eh?

Re: React, but in Python

#16

Post by quechimba » Tue, Jun 06, 2023, 6:05 PM UTC

ledauphin wrote: post #13

paulddraper wrote: post #10

I'm lost. React builds interactive UIs (web, mobile). After each interaction, the virtual DOM is programmatically recreated and reconciled to the actual DOM. But reactpy is running on a backend sever??? Is each interaction resulting in a server call? Can someone explain what is going on? EDIT: Ah, okay, thanks. Every re-render is a network call. If people complained about web UI performance before..... :)

yes, from reading the docs, there's a websocket. Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. And in many cases it's what SPAs do as well. Of course, it depends what counts as an 'interaction', but that's been the case since JavaScript existed.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

Re: React, but in Python

#17

Post by tomas789 » Tue, Jun 06, 2023, 6:09 PM UTC

quechimba wrote: post #16

ledauphin wrote: post #13

Earlier quoted context omitted.

yes, from reading the docs, there's a websocket. Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. And in many cases it's what SPAs do as well. Of course, it depends what counts as an 'interaction', but that's been the case since JavaScript existed.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

A no-op API call to FastAPI takes more than that. Even when running on localhost. And FastAPI is one of the better contestants.

Re: React, but in Python

#18

Post by LtWorf » Tue, Jun 06, 2023, 6:12 PM UTC

tomas789 wrote: post #17

quechimba wrote: post #16

Earlier quoted context omitted.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

A no-op API call to FastAPI takes more than that. Even when running on localhost. And FastAPI is one of the better contestants.

If fast api didn't use pydantic (the slowest library in that space), I'm sure it might be more deserving of the name :D

Microbenchmark to compare with typedload (which I wrote) and apischema https://ltworf.github.io/typedload/performance.html

Note that pydantic and apischema use .so files, while typedload is just pure python code.

Re: React, but in Python

#19

Post by Solvency » Tue, Jun 06, 2023, 6:17 PM UTC

quechimba wrote: post #16

ledauphin wrote: post #13

Earlier quoted context omitted.

yes, from reading the docs, there's a websocket. Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. And in many cases it's what SPAs do as well. Of course, it depends what counts as an 'interaction', but that's been the case since JavaScript existed.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

But... 99% of insert-startup-product-built-on-React (or honestly, any framework) is typically super slow (for whatever reason that might be). Sluggish, not super responsive, laggy UI, however you want to describe it. A far cry from the snappiness of desktop apps from 25+ years ago.

Something or some collection of people are doing something wrong, somewhere in the chain. So isn't this just yet another way to further entrench the modern state of meh-ness in performant UI?

Re: React, but in Python

#20

Post by paulddraper » Tue, Jun 06, 2023, 6:19 PM UTC

tomas789 wrote: post #17

quechimba wrote: post #16

Earlier quoted context omitted.

Yep. And nowadays you can deploy apps really close to users so latency is really low. If you have <100ms you don't really notice the latency.

A no-op API call to FastAPI takes more than that. Even when running on localhost. And FastAPI is one of the better contestants.

A no-op localhost call takes more than 100ms??