Love & Closures

This is part of a love & programming series.

The most difficult thing about the end of a relationship is to tell ourself the story of this ending. We like to look back and find a million reasons to justify the fact things have terminated — it only seems fair, for ourself and the other person, to come up with an actual reason than just say ‘things didn’t feel right anymore’.

Closures are important because they help us move on. To know we can access parts of our past to justify a present situation — whether it makes sense or not — is certainly a great human quality.

In programming, closures are the same because they allow functions to access their lexical scope even when invoked outside of it. They are a difficult concept to grasp when not put into practice.

A relationship is basically a stock of memories.

By the time those memories are built, we don’t think about them so much, because they don’t yet exist in the past. But as soon as the relationship ends, we become archaeologists of our own past and dig extensively. It’s likely that their place has changed in memory, or rather, the place from which we like to invoke them.

By moving relationshipHistory inside breakUp34, we’re still able to access history, even if it’s now in the inner scope.

Closures have more to do with moving memory around rather than definite endings. They’re spatial and moral arrangements we take to relieve ourselves from the pain of facts.