kylerush

Pardon my own ignorance, but isn't it also bad to have all of this trash on land? I would love for it to get removed from the ocean, but what's the terminal state plan? I'm sure there's a plan, I'm just wondering what it is.

1. The conda recommendation is in the JS App Walkthrough documentation page:

> A Python package manager: we recommend conda or pip

2. Makes sense! Something like sqlalchemy/alembic would be cool for PostgreSQL support.

3. Ah, this is interesting. Will read up on the different ASGI implementations. I had just assumed that having LLM workloads, async or not, on your main web server would be a problem (memory and/or i/o), but maybe not. To do date I’ve been moving LLM i/o workloads to background jobs on different machines with Celery, but it’s a bit more work and also makes streaming impossible. I recently did a Qwik + Celery stack for heavy LLM use, but have wanted a pure Python solution.

Thank you!

Nice work! I think the Python community definitely needs something like this. The thought never occurred to me to use HTMX w/Python for both server rendered HTML and dynamic behavior in the browser.

I have a few questions for you.

1. Why do you recommend conda or pip and not uv? Is this because the plug and play deployment platforms are configured to use pip?

2. Do you plan to make this “batteries included” like Django? E.g. it looks like currently you have to manage database schema and migrations outside of FastHTML.

3. Perhaps not in scope for this, but it seems to me making LLM API requests in the FastHTML backend could cause some scaling problems since these i/o operations can take a really long time and tie up the same threads required to render web pages. Any thoughts on that?

EDIT: Added third question.

There seems to be a libertarian slant to a lot of the comments on this. It reads as if most people believe they have an inalienable right to extend Apple’s products. In other words, it doesn’t matter what I do, what I say, or how I treat Apple, I have an inalienable right to extend their platform. A pretty bold take in my opinion.

I assume using this large of a context window instead of RAG would mean the consumption of many orders of magnitude more GPU.