duckduckbang VS ripgrep

A lot of the snooping does have an actual role with search - they need to guess the intended domain of the query [1]

Welcome to my side project, a better organized directory of domain specific search engines, based on duckduckgo !bang operators https://github.com/MoserMichael/duckduckbang/blob/master/REA...

Ideally this directory/thesaurus should help you to find a domain specific search engine, without the need of snooping on the part of the search engine. I also auto translated this directory into several languages.

[1] of course they also need the snooping for targeted advertising, but that's a different story!)

I have a catalog of duckduckgo !bang operators; a script is using google translate to translate the UI and site descriptions into several languages; it is better than nothing, but it is not an ideal solution.

https://github.com/MoserMichael/duckduckbang/blob/master/REA...

I didn't manage to automate the use of DeepL in python;

I think that specialised search engines are gaining ground, it has become easier to set one up, thanks to elasticsearch/lucene. They can be quite good, for a limited domain, and they don't have to invade your privacy in order to find out what you are looking for. I think that what is missing are tools like this, that would aid the discovery and use of these search engines. I hope that this will allow them to eat into the market from the 'low end'.

The projects source is here: https://github.com/mosermichael/duckduckbang

Unfortunately they don't invest too much into !bang operators at duckduckgo, however that's my input data...

taking care of google ;-) I have a catalog of duckduckgo !bang operators https://mosermichael.github.io/duckduckbang/html/main.html - i hope that it allows for better discoverability of specialized search engines. The latest feature added is a description for each search engine, just hover over the name, and you get a description derived from the sites meta and title tags.

I think that specialised search engines are gaining ground, it has become easier to set one up, thanks to elasticsearch/lucene. They can be quite good, for a limited domain, and they don't have to invade your privacy in order to find out what you are looking for. I think that what is missing are tools like this, that would aid the discovery of such search engines.

The project source is here: https://github.com/mosermichael/duckduckbang

ripgrep - https://github.com/BurntSushi/ripgrep

Basic code searching skills seems like something new developers are never explicitly taught, but which is an absolutely crucial skill to build early on.

I guess the knowledge progression I would recommend would look something kind this:

- Learning about Ctrl+F, which works basically everywhere.

- Transitioning to ripgrep https://github.com/BurntSushi/ripgrep - I wouldn't even call this optional, it's truly an incredible and very discoverable tool. Requires keeping a terminal open, but that's a good thing for a newbie!

- Optional, but highly recommended: Learning one of the powerhouse command line editors. Teenage me recommended Emacs; current me recommends vanilla vim, purely because some flavor of it is installed almost everywhere. This is so that you can grep around and edit in the same window.

- In the same vein, moving back from ripgrep and learning about good old fashioned grep, with a few flags rg uses by default: `grep -r` for recursive search, `grep -ri` for case insensitive recursive search, and `grep -ril` for case insensitive recursive "just show me which files this string is found in" search. Some others too, season to taste.

- Finally hitting the wall with what ripgrep can do for you and switching to an actual indexed, dedicated code search tool.

live grep: ripgrep

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

I'm not clear on why you're seeing the results you are. It could be because your haystack is so small that you're mostly just measuring noise. ripgrep 14 did introduce some optimizations in workloads like this by reducing match overhead, but I don't think it's anything huge in this case. (And I just tried ripgrep 13 on the same commands above and the timings are similar if a tiny bit slower.)

[1]: https://github.com/radare/ired

[2]: https://github.com/BurntSushi/ripgrep/discussions/2597

Explore o Ripgrep no repositório oficial: https://github.com/BurntSushi/ripgrep

🔎🗃️ ripgrep or ugrep (search fast, use regex patterns or fuzzy search, pipe output to bash/zsh shell for further processing V coloring)