Earlier quoted context omitted.
How about tracking licenses or subscriptions sold and show that to investors?
How do you do that with an OSS project that's on GitHub?
Reflex – Web apps in pure Python
121–130 of 152 posts
Re: Reflex – Web apps in pure Python
#122Earlier quoted context omitted.
good Lord, when did things get to be like this? if I shipped a free web framework with opt- out telemetry, I'd feel like a massive douche
Opt-out telemetry in companies based on open source projects has become a critical component of YC applications, VC pitches, and acquisition pitches. If it was opt-in of course nobody would turn it on. It's shady but I also somewhat understand the founders who are doing product-led growth by giving out the product on GitHub/PyPI, yet still need some usage metrics to quantify the stickiness to their backers. Pip insta…
man... the modern YC/VC webdev game is rough.
Re: Reflex – Web apps in pure Python
#123Why are we trying to fit a square peg into a round hole
Re: Reflex – Web apps in pure Python
#124I haven't worked with Python in many years now. Do people not use Django or Flask anymore? What's the recommended web stack, and where does this one fit in?
I'd see this as more like Svelte (or at least the projects I'd usually build with Svelte I might consider this for instead).
Re: Reflex – Web apps in pure Python
#125Why wouldn't it say nowhere (README, the website) what does it actually do and how? It's all marketing bullshit such as: Get up and running in seconds! Build web apps in minutes. Deploy with a single command. Build anything, faster. Create your whole app in a single language. Don't worry about writing APIs to connect your frontend and backend. This kind of shit might catch a manager's eye, not a developer's one.
It has a complete code example in the README. Looks pretty nice for the use case it's designed for.
Github and hackernews are both places where developers exchange ideas, so it helps if you explain which tech you build on and what challenges you faced.
Re: Reflex – Web apps in pure Python
#126- you still use html and a templating language for the views
- it mostly looks like old ssr code but you can transparently call methods on the server (like meteorjs)
- you get one of the best ORMs in existence with great relationship handling and generated admins
https://www.django-unicorn.com/examples/search
Not 1.0 yet but I'm using it in production and omgosh is it easy to crank out UIs.
Re: Reflex – Web apps in pure Python
#127My 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.
Wild timeline: for ref. a HTTP webserver in C would run you under 1mb, all-in, if TLS'sn't required.
Re: Reflex – Web apps in pure Python
#128Interesting how the reception seem to be different this time around compared to when they were called Pynecone. At least that is my recollection. I follow this project with interest, I don't understand all that "you shouldn't do x with y". Each to their own requirements, its great to have a choice.
Re: Reflex – Web apps in pure Python
#129Django + Unicorn has a similar goal except: - you still use html and a templating language for the views - it mostly looks like old ssr code but you can transparently call methods on the server (like meteorjs) - you get one of the best ORMs in existence with great relationship handling and generated admins https://www.django-unicorn.com/examples/search Not 1.0 yet but I'm using it in production and omgosh is it easy…
> Note that all examples are deliberately left unstyled to present the simplest implementation.
I've looked at too many documentation examples that show a bunch of things at once, with unrelated tech, making it hard to understand the current point.
Re: Reflex – Web apps in pure Python
#130Earlier quoted context omitted.
It has a complete code example in the README. Looks pretty nice for the use case it's designed for.
That answers the "what does it actually do" part, but not the "how". Github and hackernews are both places where developers exchange ideas, so it helps if you explain which tech you build on and what challenges you faced.
This is literally a link to the source code repo!