riolu

The built in port has DMA. USB to Ethernet adapters don’t and have to go through the CPU first. You’re stressing the CPU for bandwidth you aren’t actually using.

Exactly. Streaming a 4K Dolby vision blue ray remux that I legally own on my NAS uses 60-80mbps.

> Note that if I am trying to fix an app that I want to keep using I sure as hell may want to keep the preferences.

Of course, `man defaults`. You can modify the preferences and potentially fix it, backup preferences, etc. Again I must stress that you use `defaults`, the .plist on disk isn't always accurate even if you terminate the app and reboot the machine.

> The case where I want it to auto clean up is where it is repeatedly broken and I never really got to using and configuring it yet. It's pretty rare.

There isn't really a one size fits all perfect automatic solution. Not all apps are good macOS citizens.

"right" click the app and select "Open" creates the same exception without the need to open settings. There's also an equivalent terminal command for the exception I can't remember.

If either of those aren't satisfying, you can always drop the check entirely which I can't personally recommend.

Apps that install persistent services typically check if the .app bundle exists in applications so in most cases just trashing the .app is enough to stop any errant left overs from executing.

> 1) app is buggy and I'm trying to fix it by reinstalling from scratch

You don't specify and it's highly dependent but in most cases when an app is misbehaving it's an issue with preferences. You can reset most apps with `defaults` without blowing away all its data. There are some intricacies with how macOS handles preferences, so you should avoid manually editing related .plist.

I used WSL2 on Windows 10 to compile the WSL2 kernel with additional flags supporting wireguard. So I'm pretty sure compiling works, maybe it was an issue with WSL1?

That isn't even remotely related the post and Monterey is over a year old.

The systems you are trying to SSH to are using outdated host keys, you need to actually update to get security fixes, it will regenerate host keys.

You shouldn't be worried about this CVE, it sounds like you have quite a few years of CVE's you've neglected to patch anyways.

Podman’s unofficial answer to compose is “podman compose”. The official answer is kubernetes.

Podman supports generating systemd units for “Pods” (groups of containers).

The unit files podman generates are portable. Rather than version controlling your compose.yml, you would version control your unit defining your pod.

Using a makefile you could handle installing/updating/etc your unit file.

It is an equally convenient way to manage your containers, but it does require learning and understanding how everything fits together, compose is nice because it abstracts a lot.

For someone with luks2 in the username you sure have a lack of understanding about encryption.

Why would it be so hard to believe that your recovery key is hashed and salted like every other password? You can't view your key after creation, you have to regenerate it. Do I really need to pull out Wireshark to verify this for you?

Advanced data protection is explicitly removing Apple as a holder of your keys, it's not re encrypting anything, it's not new encryption. The entire process is just deleting the key that was already stored on their servers anyway. How would it be in Apple's interest to keep your recovery key after press releases and multiple warnings saying you're on your own for recovery.

This "Safari is IE" is getting tired and has never been true. Apple is quite literally on governing members for Alliance for Open Media.

Safari existing has never held anyone back. The "plausible solution" is to be patient for Apple to implement AV1.

brew.sh backend is git.

This is not a good idea however. Anything you install that has thousands of files will slow down brew substantially during updates. GitHub has had issues specifically with brew.sh misusing their service.

Git should not be a backend for any application, it was not designed for such purpose...and you will be violating GitHub or any source host TOS.

> Not that person above but the install flow for docker is obnoxious on windows and Mac.

On windows it's `winget install docker`. Mac is more of the same, just drag and drop docker desktop into your Applications. You can skip the tutorials on first launch for desktop.

> Having to create an account for open source software isn't reasonable, there's ways around that but not easily for most people.

Creating an account is entirely optional, it doesn't even prompt you to sign in.

> there's ways around that but not easily for most people.

Please explain. It never requires an account at any point of the install. It never prompts for a sign in. It's entirely optional. How much easier can "not clicking the sign in button" be?

You don't even need to install docker desktop, you can just use docker CLI. It doesn't even have to be docker, you can use podman.

I believe OP comment is just struggling with adapting to containerized workflows. An account is not a requirement, nor is the install process difficult. If you're still wanting to do it without a container, you can just inspect the image to see what the steps are for configuring your environment yourself. It is more work to not use a container.

Rather than trying to force macOS to support package management, developers should be containerizing their environments where possible with docker/podman.

The best package manager for macOS is Docker with an Alpine container. Not ruby scripts with git as a backend and questionable permissions.