Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

3.) -> While newer grep versions and SSDs helped with performance, using ag or any of it's many implementations tends to get results faster, especially on large code bases.

4.) I only had to resort to flow charts a couple times so far, mostly with Java libraries to externalize the data and control flow, because it grew just waaayy to large to keep in my head. A particular vivid memory I have here is netty (which also has a tendency for a particularly convoluted and complex control flow realized through modifying pipelines conditionally in many places).



> using ag or any of it's many implementations tends to get results faster, especially on large code bases.

Especially because ag tends to be smart about what it will ignore (e.g., the contents of node_modules, etc.)


ag is also multi-threaded, while recursive GNU grep doesn't do that (you'd need find+xargs workaround).


I like ripgrep, it's instantaneous on our large (>100k loc) codebase




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: