boyter
Cursor was an interesting case where they were maintaining an index. I think everyone has converged on not doing that, which is where I started, with BM25 with some tweaks on top.
Notable link related to this https://www.youtube.com/watch?v=ZnmtJKFonLk where Jo Kristian Bergum (notable in the search space) agrees with BM25 being a good approach for agentic workflows.
Rare Not Random Using Token Efficiency for Secrets Scanning
Sloc Cloc and Code – Did I Just Get Buster Scrugged?
If you do hook this up please let me know, id love to write about it.
Id like to see that fork. Perhaps I can fold some of it in.
Sloc Cloc and Code 4.0 (scc) – Finding the files that need the most attention
Let me know if it fails in some area and I’ll fix it.
I think John turned out to be right in the end. They did seem to patch things up with John appearing on a episode years later I think "a christmas miracle" was the title, but that was the last time he was on as far as I know.
I suspect this comparison is against reading the whole codebase though compared to just getting the bits you need.
I will have to add this as a comparison to https://github.com/boyter/cs and see what my LLMs prefer for the sort of questions I ask. It too ships with MCP, but does NOT build an index for its search. I am very curious to see how it would rank seeing as it does not do basic BM25 but a code semantic variant of it.
This seems to work better for the "how does auth work" style of queries, while cs does "authenticate --only-declarations" and then weighs results based on content of the files, IE where matches are, in code, comments and the overall complexity of the file.
Have starred and will be watching.
Since it does it anyway I added dossier pages to it as well https://searchcode.com/repo/github.com/rust-lang/rust Which is useful for humans, and shows what the system is creating.
Best part is that I get to use the tools I have built, so https://github.com/boyter/scc and https://github.com/boyter/cs to improve it which benefits anyone using those tools.
Tobacco in Australia has been taxed to the point we have a huge black market for it now. You would have thought people would have learnt from prohibition.
You cannot police morals.
Some of the non-alcoholic beers are pretty good though and I am happy to drink them.
I use it when I have candidate libraries to solve a problem, or I just want to find out how things work. Most recently I pointed it at fzf and was able to pull the insensitive SIMD matching it uses and speed my own projects up.
I can’t find it right now, but there was a post about how ripgrep worked from a someone who walked through the code finding interesting patterns and doing a write up on it. With this I get it over any codebase I find interesting, or can even compare them.
We routinely see rg invocations that take more than 15 seconds
The only way that works is if you are running it over repos 100-200 gigabytes in size, or they are sitting on a spinning rust HDD, OR its matching so many lines that the print is the dominant part of the runtime, and its still over a very large codebase.Now I totally believe codebases like this exist, but surely they aren't that common? I could understand this is for a single customer though!
Where this does fall down though is having to maintain that index. That's actually why when I was working on my own local code search tool boyter/cs on github I also just brute forced it. No index no problems, and with desktop CPU's coming out with 200mb of cache these days it seems increasingly like a winning approach.
There was this post from cursor https://cursor.com/blog/fast-regex-search today about building an index for agents due to them hitting a limit on ripgrep, but I’m not sure what codebase they are hitting that warrants it. Especially since they would have to be at 100-200 GB to be getting to 15s of runtime. Unless it’s all matches that is.
Also localhost and presumably this are good for validating your logic before you throw in roles, network and everything else that can be an issue on AWS.
Confirm it runs in this, and 99% of the time the issue when you deploy is something in the AWS config, not your logic.
Bucketsquatting is (finally) dead
Sloc Cloc and Code – Locomo (LLM Output Cost MOdel)
Rare Not Random – Using Token Efficiency for Secrets Scanning
Stop reading the news. It makes you depressed or angry. Go hiking. Walk on the beach. Play with a dog or your children. Climb a tree.
Leave the slave slab phone at home, or delete every news and social app. Do not browse the web. Take a book and read.
It will be hard at first. Then it gets easier. Best thing I ever did.
Reminder. What passes for news today wouldn’t have registered for most people 100 years ago.