macports-www VS just

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?

I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/just

I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.

Define your recipes and then you can compose them as needed.

[0] https://github.com/casey/just

just - https://github.com/casey/just

Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.

I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.

That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]

[0]: https://github.com/casey/just

> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin

I would consider using just for this:

https://github.com/casey/just

Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.

For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.

[1] https://github.com/casey/just

This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:

https://github.com/casey/just/issues/429

I really wish just was included as a package in distributions.

So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.

i've grown to like this for my personal projects. https://github.com/casey/just