RAG Is Not Dead
Highlights
- ▸Long context didn't kill RAG — context size and retrieval quality are complementary, and attention still degrades at the edges of 1M-token windows
- ▸RAG still wins on freshness, security, cost, and latency; long context wins on small knowledge bases and one-shot research — pick the right tool for the problem
- ▸'RAG' as a term is getting more precise — it's really 'retrieval + ranking + rewriting + generation', and each stage is its own product category now
Original excerpt
Frequently asked questions
What is "RAG Is Not Dead" about?
This article by Swyx (Shawn Wang) is part of the Swyx (Shawn Wang) reading list on Burn 451, covering ai engineering.
Who wrote "RAG Is Not Dead"?
This piece is part of the Swyx (Shawn Wang) vault on Burn 451, covering ai engineering. The original author is attributed at the source link.
How can I read more content from Swyx (Shawn Wang)?
The complete Swyx (Shawn Wang) reading list is available at burn451.cloud/vault/swyx. Each article includes an AI-generated summary so you can decide what to read in seconds. Connect the Burn 451 MCP server to Claude or Cursor to query all Swyx (Shawn Wang) articles as live AI context.
Can I use "RAG Is Not Dead" with Claude or Cursor?
Yes. Install the burn-mcp-server npm package and connect it to Claude Desktop, Claude Code, or Cursor. Once connected, your AI can search and reference this article and the full Swyx (Shawn Wang) vault in real time — no manual copy-paste required.
More articles in this vault.
Import the full Swyx (Shawn Wang) vault to Burn 451 and build your own knowledge base.
Content attributed to the original author. Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.