Even though it does not finish scan (it exited on some non-excluded binary .rc file), it took time measured with a watchtime utility
With this limitation, it is not viable to use this tool for real workflow locally.
Although it sounds sarcastic, in reality it might be easier and faster to replace the pdd with a perl script. Or rewrite using approaches in https://github.com/junegunn/fzf tool - it is capable of finding regexes way faster than pdd while being truly cross-platform and dependency-free (pdd requires ruby runtime and 5 gems).
The text was updated successfully, but these errors were encountered:
I wrote a tool in Go in a couple of hours that does the same as pdd in less than 1 second (on my machine) on the same codebase. You can close the issue if you think 1.5 minutes execution time is OK for your tool.
@ribtoks but this tool not only scans files but also validates what it finds, performs a number of checks, and creates a multi-level XML document. I'm sure it's possible to make it faster, but it's not a simple scanner. Anyway, I like the tool you created!