Simple-Comic VS ripgrep

🫴 Simple Comic free and open source - a reader for Graphic Novels, but it will also open image pdfs or a directory of images. It uses Apple's Vision Framework so you can use the mouse to select text in .pngs, .jpgs, and it has a Find command to make it all searchable. Once you've got the text, you can use the built-in Text-To-Speech to have it read to you, do a Google search, or paste it into translate.google.com to get it translated into a more comfortable language.

/u/F0x3S/ Take a look at this macOS Manga reader: https://github.com/MaddTheSane/Simple-Comic and https://github.com/MaddTheSane/Simple-Comic/issues/87 for handling OCRed text, with searching, and .cbz/.cbr metadata in a Manga reader.

It is macOS, not iOS, but take a look at Simple Comic, source code on github.

Source code at: https://github.com/MaddTheSane/Simple-Comic

I used the Vision framework to add full-text searching, and selection©ing to the text in Graphic Novels. Graphic Novels are just collection of image files, usually a zip of jpegs. It is a free reader app in the Apple App Store: Simple Comic It's for Mac, but it's open-source. The source code is here.

Take a look at https://github.com/MaddTheSane/Simple-Comic - it's an open source reader for .cbz files. It will compile and run on your Mac. It can open a .pdf and display just one or two pages at a time.

hideOCRMenusIfUnavailable in OCRTracker.m in the open-source App Simple Comic which, if you go into Preferences and turn off Recognize Text hides all the menu items that depending on recognizing text to function. Go into Preferences* and turn Recognize Text back on, and it puts those menu items back. That way, I don't have to explain to the user why those menus items are dim.

You give it a CGImageRef, and a block, and the block gets called back with an array of structs, each of which contains a rectangle, a confidence level, and a string, that corresponds to one line of text. https://github.com/DavidPhillipOster/MockSimpleComic takes that and wraps it in a layer, so you can mouse over the text like you can in Preview when you open a .png. https://github.com/MaddTheSane/Simple-Comic/ has been taking my pull requests and putting it up on the App Store. All available today, and with the Vision framework, which works back to the 2019 vintage macOS, and iOS.

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)