| ▲ | novoreorx 2 days ago | |
This kinda resonates with me. I've been using Python for over a decade and the only async method I trusted was gevent, and since I moved to Go after 2016, I never want use Python async in production level project, even I came back to see how it goes almost every year. But since Python's LLM ecosystem is so well, I really appreciate the courage it takes to migrate to Node when writing a RAG system. I've tried similar things recently, working on a document analyzing project using React Router as the full-stack framework, while put some ETL related work on the Python side, use inngest to bridge Node and Python services. In this way, I got the benefit of Node for LLM chat, while stil able to facilitate Python's SOTA ETL libraries. | ||