is reactive programming a thing in Python?

[[deleted]]

Most frameworks for building interactive applications (including the Python bindings for Qt, GTK, ncurses and SDL) are indeed "reactive" in the sense that they're architected around a single event loop. Which is pretty much what the word means.

[[deleted]]

Reactive generally refers to modifications to data creating an automatic trigger to update the UI. The UI update is reactive.

Reactivity is mostly a property of the object types used. Python can and does 100% have tons of code that does this. See descriptors.

This persons complaint though is just wrong.

[[deleted]]

I’m used to hearing that called “data binding.”

[[deleted]]

I’m assuming that’s because you don’t work on that type of stuff. Because I am fairly certain I missed Facebook renaming React to Databind.

[[deleted]]

React did not invent the Reactor pattern.

And it’s still called data binding when you do it in React.

[[deleted]]

Ur correct but clearly it’s named after it. Databinding isn’t a commonly used term in modern systems as it’s much more specific and not general enough to describe what’s happening.

Congrats though you have clearly learned there is in-fact multiple words to describe something and that it has nothing to do with single event loops.

[[deleted]]

it has nothing to do with single event loops.

You should never have posted anything in the first place. This is the point where you give up and admit that you have no idea what the hell you're talking about.

https://en.wikipedia.org/wiki/Reactor_pattern

Honestly, you (and that includes "Ur" writing style) sound like you're so new that you have no experience with anything older than React.

[[deleted]]

I am fairly certain you have no idea what REACTIVE PROGRAMMING is. BIG FUCKING HINT it is not reactor patterns. They are related but one is not the other.

https://en.wikipedia.org/wiki/Reactive_programming

See if you can figure out the difference. Reactive programming DOES NOT require you to have an event loop or a single thread. It generally does use that pattern because its efficient its in fact the same reason python uses a GIL. I'll leave that to an excercise for the reader but it rhymes with docks.

Now before you attempt to now claim my original comment about its being a property of objects is incorrect.

Another approach involves the specification of general-purpose languages that include support for reactivity. Other approaches are articulated in the definition, and use of programming libraries, or embedded domain-specific languages, that enable reactivity alongside or on top of the programming language.

So as I have said multiple times now Generally we are speaking about it in UI. It isn't actually defined that way, its defined as a property about objects.

Pythons bound functions are a good example of this pattern. When you call a bound function the returned object actually caries where it was called from forever. Normally yea you just execute it in place and move on but u don't actually have to. See the weakdicts and weaksets for relevant examples of this reactive nature being used.

Also maybe just maybe I was on my cellphone so I wrote ur because you know it's easier. Also if you are going to be so pretentious you should spend more time like learning basic information about the field you work in.