3 ms·
The thing is that those dumber tools can do smarter things than IDEs. I had 2 use cases lately - one was to investigate usage of all function bodies that used
by xlii 3y ago
The thing is that those dumber tools can do smarter things than IDEs.
I had 2 use cases lately - one was to investigate usage of all function bodies that used specific library for the last 6 months. JetBrains IDE has semantic search but it requires a lot of fiddling (syntax feels very foreign, might be Groovy thing or their own DSL and doesn’t span across multiple commits.
Second was to navigate through a custom pre-transpiration layer, which JetBrains could pick up around 30% of the times.
Those are two cases solved quickly with list refiltering (first one took 15 minutes, second took less than 3). And they were portable, as sharing was a simple copy & paste.
The gist of it is that dumb and smart is marketing thing. ripgrep is dumb tool just as fzf is, but they can be made into a very smart setup.
IDEs can make high general work impact but from my experience suck badly when you enter road less traveled.
- brabel 3y agoYou don't give enough information to know what you actually did, but I am pretty sure you're splitting hairs here... IntelliJ's "grep" is incredibly fast and has the huge benefit that you can keep an iteractive list of matches and go through them in the search window without leaving the search, even edit the matches manually if you want. > suck badly when you enter road less traveled. It seems you just decided that's the case without any sort of rationale behind it. Please give a real example I can try instead of hand waving.