I've looked into this recently and it's really good. They make use of Python's type annotations to do some clever conversions to frontend code.
Reflex – Web apps in pure Python
11–20 of 152 posts
Re: Reflex – Web apps in pure Python
#12Re: Reflex – Web apps in pure Python
#13$5 million raised for hosting? I honestly fail to understand the ways of VC despite a decade of trying to understand them.
Re: Reflex – Web apps in pure Python
#14Re: Reflex – Web apps in pure Python
#15sometimes the war is lost even before the battle begins. During grad school, I wrote a whole bunch of web apps entirely in R using Shiny. It was clunky as hell, but yeah, it worked. I went looking for what's up with Shiny these days and found this - https://shiny.posit.co/
So yeah, full on pivot into python. pip install shiny. Alright!
"No web development skills required. Develop web apps entirely in R I mean Python"...yeah that's not happening.
Re: Reflex – Web apps in pure Python
#16Why are we trying to fit a square peg into a round hole
Maybe it is easier to learn a framework within the ecosystem of a language you already know than to learn both a framework and a new language.
Tons of software exists for this reason. For example, somewhat relevant here, web apps in R via R Shiny: https://www.rstudio.com/products/shiny/
(There is also Shiny for Python IIRC.)
Re: Reflex – Web apps in pure Python
#17Why are we trying to fit a square peg into a round hole
because some people have a square peg and not a round one.
Re: Reflex – Web apps in pure Python
#18Earlier quoted context omitted.
JS got popular on the server because it was the default option on the client. Makes sense that Python should get popular on the client because it's the default option on the server.
Since when is Python the “default choice” for server side dev?
Never to the degree JS on the client is, though the early and strong support on PaaS/serverless systems gaveit something of an edge for certain server-side stuff, and it was popular for a long time (though not dominant) outside of that.
Really, I think the main driver for isomorphic Python web libraries like this isn't general web apps (though they'll get used for that, too), but the putting frontends on data science, ML, etc., stuff where Python is the dominant tooling language.
Re: Reflex – Web apps in pure Python
#19Why are we trying to fit a square peg into a round hole
[deleted]
Re: Reflex – Web apps in pure Python
#20My major complain here is that, as far as being a web framework there is precious little information here about the framework. How does this framework scale with multiple requests? What concurrency strategy is it using (threads, processes, actors, etc?). Is this opinionated (it doesn't seem so but it also doesn't say it isn't either). How does this work with popular libraries x,y,z. The full docs have a little bit more information, but not a ton. But mostly there are some cute toy examples and "built in python" and thats about it.
Lets compare this with for example play https://www.playframework.com/ I know from this that it built on Akka, its stateless, aims for predictable resource consumption, has non-blocking io, etc. There is a ton of really important information on what does this web framework actually do that is really important when you are making a choice of a framework.
I have no idea how good this framework is, but besides a few toy examples, I can't see anything that makes me thing "wow this is great I need to use this". Using python to generate front end attributes isn't new, most any web framework can do this also.