Now that the WIndowServer runs as its own user, it can no longer boost anon's processes.

With my microkernel fan hat on, the right way to solve this is "time" or "scheduling context" capabilities, which a thread can send to another thread, and that other thread would use to get scheduled.

With my "SerenityOS is a classic Unix" hat on, we don't want to go all the way there, but maybe we could have a lite version of that, where you would be able to sys$boost anyone, but at the expense of giving up some of your own priority. That way the overall priority assigned to a group of malicious processes stays the same, and they can just redistribute it between them.

Then we'd bump WindowServer's initial priority some more, to make it run at High priority even when it grants some of its priority to the active client. But — we'd need to track who actually boosted whom, so that when the client dies, the priority boost returns to the WindowServer.