macports-www VS ripgrep

macports - https://www.macports.org

I switched to MacPorts after becoming tired of Brew tainting my filesystem.

MacPorts keeps things clean in /opt/local.

https://www.macports.org/

https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-pack...

gh is available via Homebrew, MacPorts, Conda, Spack, Webi, and as a…

I've read the article but some questions still remain. Does Retroactive install the shared dylibs of previous macOS releases? Or does it use an approach similar to https://www.macports.org/ ?

I highly recommend using yt-dlp to download videos in the highest quality available from a wide variety of web sites (notably YouTube, hence the "yt" in the name, but it supports a ton of sites). The best way to install it is with an open-source package manager, either Homebrew or MacPorts. These make it easier to install dependencies like Python 3.11 and optional (but highly recommended) utilities like ffmpeg. Both Homebrew and MacPorts are great, and you can install both side-by-side. I guess I'd recommend Homebrew over MacPorts because it downloads pre-built binaries instead of compiling from source, so it's faster. But again, they are both great.

This is Reddit so they will most likely be people who say to download Macports, but frankly, I don't care, and homebrew is enough for me. I'm not smart, but I know not to download programs/random things without prior research, don't use sudo commands on things you don't know and don't enter your password if you feel unsafe.

The initial setup was quick and painless, but I quickly realized that MacOS does not ship with a package manager (to my surprise!) the Apple Store won't be enough to cover my needs, so onto Google I went. I learned that the two most popular package managers are Homebrew and MacPorts. After reading for a while, I found some users concerned about how Homebrew managed folder permissions (here and here), and with the fact that it installs already compiled binaries, which may be a security/privacy issue. However, it seems that the folder issue was addressed with the ARM release of Homebrew, which now installs under the /opt/homebrew folder.

On Linux, most distributions come with their own package manager out of the box (e.g. Ubuntu / Debian has APT). One annoying thing about macOS as a development platform is that it does not come with one out of the box, and Homebrew has emerged as the most popular third-party management by far. There are other ones like MacPorts as well but I think this is the kind of thing where the popular one tends to become more popular because people don't want to learn/use multiple package manager. I actually used to use MacPorts before I switched to Homebrew just because it's been getting a lot more momentum / features / development and it's where every package is.

Others have offered solutions, but for future reference the actual Terminal commands that failed would be useful; "File not found" sounds like a path error, "Command not found" sounds fixable via Homebrew or Macports

TL;DR, about the section that states software from other UNIX-like OSes is hard to port to MacOS, how about homebrew and macports?

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)