Skip to content

Commit

Permalink
why lightrag
Browse files Browse the repository at this point in the history
  • Loading branch information
liyin2015 committed May 20, 2024
1 parent f65c6c5 commit 91f1d64
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -90,8 +90,11 @@ You have a similar coding experience as PyTorch. Here is a side to side comparis

3. **Suitted for Both Researchers and Production Engineers**

We start with understanding the frontier of AI research and LLM productionalization, and our design is grounded on our understanding of all dataflow in LLM applications, and
the process of
On top of the easiness to use, we in particular optimize the configurability of components for researchers to build their solutions and to benchmark existing solutions.
Like how PyTorch has united both researchers and production teams, it enables smooth transition from research to production.
With researchers building on LightRAG, production engineers can easily take over the method and test and iterate on their production data.
Researchers will want their code to be adapted into more products too.



**LightRAG vs other LLM libraries:**
Expand Down

0 comments on commit 91f1d64

Please sign in to comment.