It seems like the repo's primary reasons are security research on macOS.
> They transition away from x86 anyway
I'm not sure what that has to do with running a Docker container. Containers support arm64; presumably you could do arm64 in both host and guest OS. (IDK if this particular image does; never used it.)
Why comment on something that you have never used?
The fact that containers supporting arm64 is not relevant because this project requires x86. Combine that with the fact that apple no longer sells x86 hardware - it would seem that them simply doing nothing would allow the project to fade off organically.
The idea of them taking specific action to kill this after ignoring it for years is very puzzling. It feels like they have given more time and attention to this project than asahi.
Asahi Linux? That's not osx, why would they care about that and what grounds would they have to take action?
Purely speculating here, but naybe they're taking action precisely because it's losing significance in the CI context? They might've seen the value in it before, and only see issues with it now
Keep brew far away from your prod system. Everything you can‘t do in macos just use a vm.
Don‘t touch the system and Timemachine will never corrupt, its that easy in my experience.
But… brew doesn’t touch the system, and never did?
Even when it used /usr/local (before the root system became hard readonly) that was an unused folder path, and it explicitly refuses to install as root.
I kind of made a general purpose sleep proxy myself a few years ago with a apache and some cgi scripts getting triggered when I visit my /jellyfin or /guacamole
It just listened to the fixed routes, woke the server and proxied the page when finished (sometimes took 2 loads)
But basically is the same as in the arzicle except I didn‘t need to manually WOL anything and my server just went to sleep by itself
