6 ms·
I have always used traditional grep to search codebases. It serves me better than an IDE when there’re lots of scattered and frequent queries. grep’s design is
by piekvorst 3mo ago
I have always used traditional grep to search codebases. It serves me better than an IDE when there’re lots of scattered and frequent queries.
grep’s design is surprisingly winning, exceeding expectations to this day.
- weaksauce 3mo agoyou might be interested in https://github.com/boyter/cs https://github.com/boyter/cs pretty fast and neat project to search code interactively with a lot of optimizations on finding the right thing
- boyter 3mo agoCame here to post than and you already did. Thank you!
- piekvorst 3mo agoThe bottleneck, in my case, was indeed the poorly designed GUI of JetBrains and VSCode versus CLI. By migrating to CLI, I have abandoned intelligent queries as well. This project seems like a bridge: it preserves CLI, but restores the queries. This is a promising road that I would probably not take. I have learned to live with simple per-line regular expressions. I have never felt that they slow me down. In fact, the opposite is true: they let me craft fuzzy queries clearly, i.e., to balance the fuzziness across the query. I’ve never learned to do that with the black-box intelligent queries, which severely limited my scope in the past.