I resemble that comment!

But seriously, it does really bug me on principle that DropBox should use over half a GB simply because it uses Chromium, even when nothing is visible.

Maestral is a cross platform implementation of the Dropbox client API which I use on low end Linux machines.

Thanks for the tip - I’ll take a look

For me it's LSP servers taking 2 gigs of RAM. With Antigravity, Google managed to go beyond this, it is totally unusable for me (but other VScode clones work fine, apart from the 2 Go LSP servers).

haha exactly. i realized i spent too much time staring at htop wondering what is this process?, so i decided to automate my own anxiety.

Scheduler Manager is definitely the more accurate term. Im just the middleman between the chaos and the kernel.

Now we need processes to gain awareness of the process manager and integrate an LLM into each process to argue with the process manager why it should let them live.

Imagine Chrome.exe pleading its case: 'Please, I need 4GB of RAM, the user might revisit that tab from 3 hours ago!'

while BrainKernel replies: 'Objection overruled. You have 5 seconds to wrap up before SIGKILL.'

I might actually have to build a 'Process Defense Attorney' agent now. The logs would be hilarious.

Assistant to the scheduler manager

Assistant scheduler manager