----
The research is jaw-dropping enough for the average reader to comprehend (e.g: I am not a techie, but a former IBEW datacenter wiretwister).
It could be covered in pube-sprinkled-turds and would still be worth reading.
To me the "slopLOL" crew is akin to people who'll take their time to correct others' their/they're/there usage:
Just read the fucking sentence (LLMs can and do and aren't so poopy-you-suck-for-asking-questions).
How news is delivered matters. If you don’t believe that, why would news outlets compete with each other? Even if the facts are the same, would you prefer to get them from a good or bad writer?
I am smart enough to not need perfection. I just want the data. Write however tf you want, the original facts matter most (to me).
And so will LLMs.
I'll suggest adaptation.
>why would news outlets compete with each other?
My suggestion would be: competition for the masses' con$umption$. It generally works; shouldn't have to obfuscate the `man` pages for this always-running daemon.
> I am smart enough
Knock yourself down a peg, kid.
Also, my IQ scares even me; I've chosen bluecollar so I don't have to be evil as much with it.
Companies do not give two shits about most users, with (e.g:) AMD saying the quiet part out loud, recently, with their recent gamers-last announcement.
Also see: Apple's invasive attempts to categorize all local data, by default; if you want to opt-out (some service, like OP's, you cannot!), it takes dozens of clicks for each new software – intentional dark-patterns to make opting-out cat-and-mouse.
> Also, my IQ scares even me
Oh, brother.
I mean this with the best of intentions and care: have you been psychiatrically evaluated lately? The language you’re using is consistent with friends I know who are off their stabilizing medications.
This is completely tangential to your point, but I'd bet that this daemon isn't always running. Apple is fond of putting as much system functionality as possible into daemons that (a) can be spun up quickly when needed in response to Mach IPC messages, (b) can be killed safely at any time to free up memory, including with SIGKILL if necessary, and most importantly (c) operate in the tightest, most locked-down sandbox they could devise.
For background computational tasks like this one, it can also be helpful for getting thread prioritization right. If some computation doesn't need to happen quickly, a daemon can easily make sure that it gets assigned to efficiency-optimized CPU cores, tell the OS scheduler to give priority to more important stuff, reduce precision of timers to coalesce wakeups, and make sure that any thermal throttling affects the background stuff before it slows down anything the user will notice. It's a pretty slick system.