Approaching Woodhill

Operate for me, operating system.

I know how you juggle your processes--

mutex and wait and signal and fork--

and I want that to work for me.

I want to be able to stop a feeling and say

"wait your turn in the back store"

while I dutifully execute my tasks,

removing the obligations and resources

until I am ready and able to complete them,

and they starve out while the

garbage collector returns their allocated spots to emptiness.

I know how you manage your memory--

dynamic loading, dynamic linking, overlays, or paging.

My memory is similar, but it isn't exactly like that.

When I draw an old feeling from my past,

I don't store it in local RAM; it goes behind my eyes

so that the regret application can access it at 20 nanoseconds

cycling every detail of that data in a single blink,

so that it can be available when I accidentally think even for a moment

and am crushed with every other missed opportunity and mistake.

I know that you have ways to stop an executing thread

from entering into the critical section

from sifting through unsorted heaps of corrupted data

fragmented along my life's physical memory.

Give me a synchronization monitor to #killall -9.

I want to know structure like you do:

trading pointers and addresses to threads efficiently,

designed specifically so as not to miss a beat.

I want to be engineered to not say the wrong thing

and to not lose track of myself when everything depends on me

and to not deadlock--to not enter a cycle

while I wait for her

and she waits for him

and he waits for me

and we all keep waiting.

Stuck without preemption,

without an interrupt to break the circle.

But, truly,

I don't want a system that doesn't make mistakes,

like you are,

I want an algorithm that lets me live with them.