71–80 of 152 posts
Installing all the python deps (250mb), and node_modules (500mb) , plus a package size of 3mb of js isn't a great look.
My only wish for this is that it didn't just cobble a bunch of existing web stuff together behind the scenes and put an python interface + code generator on it. Installing all the python deps (250mb), and node_modules (500mb) , plus a package size of 3mb of js isn't a great look.
The 3MB of JS is in dev mode or prod mode? (Is this similar to the other comment where they were running in dev mode but when they ran in prod it was much smaller ~ 340KB?)
My 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 mo…
In general, I think the readme's not bad. I think the example is eye-catching, and I can imagine this would be really nice to make a prototype with. Whether or not it would scale well etc, yes, it would be good to have some of that detail. But I can see a really good use for it already.
Worth noting is that this framework has telemetry [1] enabled by default [2] which gathers and sends off various information about your system unless you explicitly disable it. [1] https://github.com/reflex-dev/reflex/blob/919f239168d789056d... [2] https://github.com/reflex-dev/reflex/blob/919f239168d789056d...
There’s nothing user identifiable here though. No ips, locations, etc. I guess they could get it from the reception though hmm
It sends the information to a remote server, so your IP is obviously shared as well. It also sends a "project_hash" as "distinct_id" which sounds like a unique tracking ID to me.
So now you have some serious talent looking at the pain points people express about the platform, because ofcourse you want to keep the "devlopers, devlopers, devlopers" happy.
Personally I dont see the attraction of an all python approach to the web. The event driven nature of client side programming has no particular affinity with Python. While JS is clearly a monopoly, it doesnt strike as we are paying a huge price for the lack of alternatives. Maybe its just my lack of imagination. If people complain about JS frameworks is because of the choices and designs and burdens these imply, not the fact they are JS.
The area where an all-Python approach would be a radical new take that opens entirely new horizons is actually not the web, but mobile apps.
Worth noting is that this framework has telemetry [1] enabled by default [2] which gathers and sends off various information about your system unless you explicitly disable it. [1] https://github.com/reflex-dev/reflex/blob/919f239168d789056d... [2] https://github.com/reflex-dev/reflex/blob/919f239168d789056d...
I haven't kept up with web framework type things in awhile—how commonplace is this? from here it looks kind of insane.
https://nextjs.org/telemetry https://docs.streamlit.io/library/advanced-features/configur...
My 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 mo…
It's just Python code that gets translated into a NextJS app.
I'm following Pynecone (now Reflex) from the start and liked the idea of building out an AST with Python and compiling that to a working web app (we're actually doing the same with https://wasp-lang.dev/ , only it's a DSL and an explicit compiler with JS interop).
Earlier quoted context omitted.
They even have that long bunch of meaningless badges to say that tests are passing or whatever!
We have 5 badges in total, and 1 of them to points to our integrations test passing. And the integration test do serve an important purpose in making sure we are compatible on multiple different os and don't make a change that would break WSL for example. More info here https://github.com/reflex-dev/reflex/tree/main/.github/workf... The others are the current latest version, python version we support, how many people…
I expect tests to always be passing before merging anything.
pypi metadata has the list of supported python versions, in text format
A link to your documentation? Ok but why can't it be a regular link?
I use forums or IRC, so the online users on whatever aren't super meaningful to me personally.