Showing posts with label computing. Show all posts
Showing posts with label computing. Show all posts

Monday, June 8, 2026

Still Running

Seethrough Head with Circuit Connections and Computer Interface Icons 

A biological device built for uptime, not closure.

There is a difference between closure, forgetting, and termination.

Take the stupidest possible example: a pen. I need to write something, and I want my favorite black pen. If I find it, the task closes immediately. Need, search, satisfaction, use. Nothing interesting has to keep running. The process completed its loop.

But if I cannot find the black pen and settle for a red one, something different happens. The functional task closes: I can write. But a small discrepancy remains: where is the black pen?

Most of the time, that discrepancy is too trivial to become memory. It does not cross into the archive of the self. Two years later, if I find the pen under a couch cushion, I almost certainly will not think: there it is, the unresolved black pen of June 2026. It will barely register. The process died before it became memory.

So the mind does not preserve every unfinished thing. That would be unbearable. Most unresolved things probably go into a temporary folder: unfinished but probably unimportant. Desktop clutter, one inch from the recycle bin.

That folder matters because it lets us distinguish between unfinishedness and memory. Unfinishedness alone is not enough to become long-term memory. The organism needs a reason to preserve it. Evolution is not interested in archiving every loose end. It is interested in keeping what may matter later.

The event horizon of long-term memory may be the point at which an experience becomes future-relevant. Not philosophically important. Biologically important.

Threat crosses. Reward crosses. Shame crosses. Belonging crosses. Betrayal crosses. Novelty crosses. A failed prediction crosses. A social wound crosses. Anything that might help the organism anticipate danger, find safety, preserve status, avoid humiliation, repeat pleasure, or understand attachment has a better chance of being saved.

The missing black pen evaporates because it usually does not matter. But if that pen belonged to your dead father, or if losing it caused a public failure, or if someone stole it in a way that confirmed an old distrust, then the same object changes category. It is no longer a pen. It is evidence. It is a cue. It is a future-relevant disturbance.

Borges’s Funes is useful here by contrast. In “Funes the Memorious,” Borges imagines Ireneo Funes, a poor young man from Fray Bentos, Uruguay, left paralyzed after being thrown by a horse. He is incapable of forgetting, and Borges understands the horror of that better than anyone: this is not a superpower, but a curse.

Funes remembers everything: every object, every scene, every variation in light. But that is not necessarily intelligence. It may be the opposite of usable memory. Funes is buried under undigested particulars. No conclusions, no hierarchy, no compression, no mercy. He does not preserve what matters; he preserves everything. He has raw footage where a mind needs models.

Human memory is stranger. We do not remember everything, and that is one of the reasons we can think. But what we do remember may not always be stored as a conclusion. Sometimes long-term memory is not an answer. Sometimes it is a process still running.

Not: this happened, file closed.

But: keep modeling this; it may matter again.

That is why some memories feel less like past events and more like suspended computations. Was I safe? Was I loved? Was I humiliated? Did I misunderstand? Could I have acted differently? Should I expect this pattern again? What does this say about me?

The past is not always remembered as a scene. Sometimes it is remembered as an unfinished task.

This makes human memory different from Funes’s curse. Funes retains objects and scenes: raw perceptions, almost thing-like in their solidity, rather than processes, abstractions, or connections. Humans often have processes that outlive the objects. The details decay, but the unresolved computation remains.

Of course, not every process is allowed to continue. Sometimes the system deprioritizes. Sometimes it lets the folder decay. Sometimes sleep strips a task of urgency without fully resolving it. And sometimes, under dysfunction or emergency, a process may be effectively terminated. Alcohol blackout is one example: the body continues, the conversation continues, behavior continues, but the autobiographical recorder stops saving. The process burns without leaving a file.

The task manager metaphor helps.

A system may ask: Terminate this task? It is still running. Unsaved progress may be lost.

And sometimes the organism answers: terminate. The processor is overheating.

The mind wants closure. The organism wants uptime. Between the two sits an interface designed by evolution, apparently running Windows Vista on an aging Intel i5 with forty-seven Chrome tabs open — unsupported since 2017, but somehow still online.

Ancient threat detection is the McAfee of the nervous system: allegedly there for protection, but intrusive, processor-intensive, full of false positives, and impossible to uninstall.

Threat detection is not evil. It exists for a reason. It kept bodies alive. It noticed danger, remembered predators, tracked betrayal, monitored social exclusion, scanned the dark, and made sure the organism did not walk cheerfully into death.

But what protects can also consume. A process designed to preserve the system can become one of the main reasons the system underperforms. It keeps scanning. It keeps warning. It keeps finding possible danger in tone, silence, memory, ambiguity, desire, fatigue, and rooms where nothing is technically happening.

That is the problem with running processes. They are not always wrong. Sometimes they are just too expensive.

The mind may prefer closure, but the organism prefers uptime. Uptime is not peace, not meaning, not resolution. It is the minimum miracle of continued operation: survival without the luxury of closure.

So maybe a life is not a clean sequence of completed tasks. Nor is it Funes’s impossible archive of everything. It is something more unstable: closed loops, decayed clutter, suspended processes, emergency terminations, and long-term memories that crossed the event horizon because evolution decided the future might need them.

Most things vanish. Some things conclude. Some things remain unresolved but harmless. And a few acquire enough gravity to keep trading with the present.

The past is not always recalled.

Sometimes it is negotiated with.

Sometimes it is still running.


Friday, October 30, 2015

What does Cloud Computing mean?


OpenClipArt image for gsagri04
When we hear the term "The Cloud" or "Cloud Computing" we immediately think in a vague and intuitive way of the Internet (and it's true, in fact, that the expression computing cloud has a lot to do with the Internet). However the Internet, in its most proto-archaic form, exists for over 40 years and it is popular for at least 20 without the term cloud being associated to it  in any way. Indeed this term  was coined in recent years to give account of a new phenomenon related to the Internet [i] of a new form of access to applications (the term software is barely used nowadays). Years ago the way to access a program, application or software was typically go to the computer store, purchase some discs and load them into the computer (hardware). Almost inadvertently, this type of access to computing applications has been displaced by its use online .

Without straining much the memory, we can mention the example of Adobe Acrobat, which until very recently called for a download of the program on the computer and now, however, only requires the user registration while all information is supported online . It is true that the documents you create can be downloaded into your private computer (although it is also possible to opt for storage in the cloud ) but the use of the service itself does not require any download. Another example is the emergence of platforms such as SoundCloud which doesn't require any software download but allows users to store their favorite songs and access them from their computers or any other computer. 
The concept of cloud computing is very broad and covers almost every possible kind of service online but when companies offer an utility hosted in the cloud,  they usually refer to one of three modes: software as a service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS).

Software as a service (SaaS) refers to a software distribution model in which applications are hosted by a company or service provider and made ​​available to users throughout a network, usually the Internet. Platform as a Service (PaaS) is a set of utilities that supplies the user with operating systems and associated services via the Internet without the need of performing any download or installation. Infrastructure as a Service (IaaS) refers to outsourcing of equipment used to support operations such as storage, hardware, servers and network components [ii] .
Ultimately, the term "The Cloud" does not refer to any "big one-eyed, omni-present mythical creature out in the land of the interwebs"[iii] . but to a new way of accessing and using computing programs.




[i] The origin of the term cloud computing is unclear. The expression cloud is Commonly used in science to describe a large agglomeration of objects That Appear visually from a distance as a cloud and describe any set of things Whose Further details are not inspected in GIVEN context. Liu, [edited by] Yang Hongji, Xiaodong (2012). "9". Software reuse in the emerging cloud computing era . Hershey, PA: Information Science Reference. pp. 204-227. ISBN  9781466608979 . Retrieved 11 December 2014 . (Cited in Wikipedia "Cloud Computing." Wikipedia . Wikimedia Foundation, nd Web. 29 Oct. 2015).
[ii] "What Is Model SPI (SaaS, PaaS, IaaS)?" - SearchCloudComputing Tech Target, Feb. 2012. Web 29 Oct. 2015.
[iii] Greenlee, Greg. "Get your heads out of the Cloud!" Blacks In Technology." Blacks In Technology. N.p., n.d. Web. 30 Oct. 2015.