darling VS earlyoom

There is actually a Wine-like transplier called Darling. The problem is that development is very slow because there is not as much need for MacOS programs on Linux, and there is a huge shortage of volunteers and manpower. And it has been rendered almost obsolete because Apple moved to ARM. Additionally 90% of Apple's API is closed source despite Apple claiming to champion open source.

Unfortunately not. Darling [0] is still at the point that it can only run command line applications. Only the most basic GUI applications are supported. That's still a massive accomplishment that I don't want to diminish, but it's nowhere near the point that WINE was at even quite a long time ago.

[0] https://www.darlinghq.org/

xcodebuild CLI to compile iOS apps without a Mac. Seems possible in theory, although there's an ongoing issue some are seeing apparently: https://github.com/darlinghq/darling/issues/488

I wonder if there's opportunity for overlap with darling (https://www.darlinghq.org/) here, somewhat like using WINE on top of actual Windows.

Hi guys, just wanted to make a quick shoutout to Darling since not a lot people seem to know about it, which is a compatibility layer like Wine for Linux, but it allows for MacOS applications instead of Windows apps to be able to run on Linux!

> The system is not supposed to 'lock up' when you run out of physical RAM. If it does, something is wrong. It might become slower as pages are flushed to disk but it shouldn't be terrible unless you are really constrained and thrashing. If the Kernel still can't allocate memory, you should expect the OOMKiller to start removing processes. It should not just 'lock up'. Something is wrong.

I don't why but locking up is my usual experience for Desktop Linux for many years and distros, and I remember seeing at least one article explaining why. The only real solution is calling the OOMKiller early either with a daemon or SysRq.

> It should not take minutes. Should happen really quickly once thresholds are reached and allocations are attempted. What is probably happening is that the system has not run out of memory just yet but it is very close and is busy thrashing the swap. If this is happening frequently you may need to adjust your settings (vm.overcommit, vm.admin_reserve_kbytes, etc). Or even deploy something like EarlyOOM (https://github.com/rfjakob/earlyoom). Or you might just need more RAM, honestly.

Yeah. Exactly. But as the thread says, why aren't those things set up automatically?

It's not that simple: some defaults may differ, and some features may arrive at different times (if ever). For example, earlyoom has been enabled on Workstation since F32, but the KDE Plasma spin got it one release later.

Most answers will answer your question, but you can do better and avoid the freezes in the first place. IME almost every time the system froze up and didn't come back in a few seconds it was out of memory. The obvious solution is to add memory, but you can use Early OOM to kill hungry processes if you're running out of memory instead.

It sounds like you're running out of memory though, so if your OS's OOM killer isn't working as well as it should, you can try earlyoom as an alternative.

Swap is indeed supposed to prevent this AFAIK. You can though try some tools like EarlyOOM and see if it helps : https://github.com/rfjakob/earlyoom