Surely 'strings' would be even better?

Feels important, but I wish they also had compared against something like MeiliSearch or Algolia.

I recently watched the new Palantir + Kirkland & Ellis fund formation platform demo, and I was surprised to see how effective the union of structured data was in an agent harness. We're used to dealing with flat files and comparing here basic ways of searching, essentially, long strings, but using Palantir's "Ontology" graph framework, I think Kirkland is going to be able to achieve some exception and differentiating outcomes in legal tech. The whole idea assumes that they've got great structured data already, and perhaps that's the real valuable unknown, but giving an agent those tools is super powerful.

I wrote about it[1] and came away with a different view on both Palantir and the future of agentic workflows personally.

[1] sorry, LinkedIn: https://www.linkedin.com/pulse/fund-managements-killer-app-d...

Tangential, I have a hook that rewriters grep to rg but lately I wonder if this is actually wasteful as the model is so biased to grep, is there a way to shim/alias perhaps?

This is a surprising result. With structured inputs like source code, I’d expect grep to outperform semantic search, but natural language’s errors and inconsistencies seem to leave so many cracks for information to fall through.

If you are truly bitter-lesson pilled - give the agent all the tools and let it decide which to use.

- regex (grep) - hybrid search (bm25+vector)

this X vs Y is uninteresting when the answer can be both.

I'm curious to see what patterns it's grepping.