←back to thread

230 points taikon | 1 comments | | HN request time: 0.196s | source
Show context
dcreater ◴[] No.42546890[source]
Yet another RAG/knowledge graph implementation.

At this point, the onus is on the developer to prove it's value through AB comparisons versus traditional RAG. No person/team has the bandwidth to try out this (n + 1) solution.

replies(2): >>42546979 #>>42550357 #
ertdfgcvb ◴[] No.42546979[source]
I enjoy the explosion of tools. Only time will tell which ones stand the test of time. But this is my day job so I never get tired of new tools but I can see how non-industry folks can find it overwhelming
replies(2): >>42547052 #>>42551832 #
trees101 ◴[] No.42547052[source]
Can you expand on that? Where do big enterprise orgs products fit in, eg Microsoft, Google? What are the leading providers as you see them? As an outsider it is bewildering. First I hear that llama_index is good, then I hear that its overcomplicating slop. What sources or resources are reliable on this? How can we develop anything that will still stand in 12 months time?
replies(4): >>42547244 #>>42547418 #>>42548475 #>>42551860 #
1. dcreater ◴[] No.42551860[source]
haha I had heard that langchain was overcomplicated, self contradictory slop and that llama index was better. I dont doubt its bad as well.

Both are cut from the same cloth of typical inexperienced devs who made something cool in a new space and posted on GitHub but then immediately morphed into a companies trying to trap users etc. without going through an organic lifecycle of growing, improving, refactoring with the community.