@@ -265,12 +265,11 @@ <h2 class="subtitle has-text-centered">
265265 </ div >
266266
267267 < p >
268- Its official implementation requires < strong > nearly 900 lines of handwritten logic</ strong > , and even
269- FlashRAG still takes
270- < strong > over 110 lines of code</ strong > . In contrast, UltraRAG 2.0 achieves the same functionality with
271- just
272- < strong > 50 lines</ strong > . Notably, about half of this is merely Pipeline Yaml pseudo-code, dramatically
273- lowering the development barrier and implementation cost.
268+ In the official implementation, the Pipeline alone requires < strong > nearly 900 lines of handwritten logic</ strong > .
269+ Even with a benchmark RAG framework such as FlashRAG, it still takes < strong > over 110 lines of code</ strong > .
270+ In contrast, UltraRAG 2.0 achieves the same functionality with just < strong > around 50 lines of code</ strong > —and notably,
271+ nearly half of these are simply Yaml pseudo-code for pipeline orchestration.
272+ This dramatically lowers the development barrier and implementation cost.
274273 </ p >
275274
276275 < div class ="item ">
@@ -290,7 +289,7 @@ <h2 class="subtitle has-text-centered">How Different Frameworks Implement IRCoT:
290289
291290 < p >
292291 We showcase how frameworks differ in implementing the same functionality.
293- FlashRAG requires verbose control logic with explicit loops, conditionals, and state updates.
292+ FlashRAG requires lengthy control logic with explicit loops, conditionals, and state updates.
294293 UltraRAG 2.0, on the other hand, simplifies everything into just < strong > a few lines of Pipeline
295294 YAML—branches and loops</ strong > are expressed declaratively,
296295 removing the burden of manual coding.
0 commit comments