Sometimes I Think We’re Living in a Simulation and Just Running Lines of Code

Perhaps we are lines of code…

Humans fancy that there’s something special about the way we perceive the world, and yet we live in loops, as tight and as closed as the Hosts do, seldom questioning our choices…” ~ Doctor Robert Ford, Westworld

This quote has been rolling around my head lately, leaving me amazed at its truth. Have you thought about your daily routine? I know my weekday mornings especially are locked into the same basic loop day in and day out, as if running lines of code from a script. Can I change it? Of course I can, but it snaps back to what it was if the new routine doesn’t prove useful.  The script changes on its own over time in large and small ways, but the basic…functionality…remains unchanged.

There are many other examples of this script-running in my life. What about you? Can you truly say you’re “drastically off-narrative”?

0 comments

Quote of the Day

Putin couldn’t have done it without the help of the GOP. From his attack on the 2016 U.S. election to his coverup since, Moscow’s greatest ally in hybrid warfare against America is the Republican Party.” ~ Alexandra Chalupa

0 comments

Lost

(Click to embiggen.)

There was a time when I used to understand macOS’s underlying disk structure—admittedly only on a rudimentary level—but now even that is long gone.

The illustration above is so much voodoo and black magic to me.

The other day while in Adobe Bridge I noticed there was a disk icon appearing on “Macintosh HD” called “dev”. Not remembering ever seeing this before, I became kind of alarmed. I had unsuccessfully attempted to install the McAfee Security Suite available through Cox (yeah, yeah, I know), and while I thought I’d managed to get it all ripped out afterward, I was concerned that this “dev” drive was an unwelcome remnant.

Interestingly, I couldn’t touch it, and it was only visible in Bridge. Even toggling all files visible in Finder it didn’t show up. I could log in as Root and manually find it through Terminal, but was still untouchable. I had a full backup from the night before, so I just resolved to restore the entire machine when I got home that night.

Booted into the backup clone drive and lo and behold, it was even there on that drive, a drive that had been completely disconnected when I was messing around with McAfee. Okay, I thought, it’s obviously been there a while, leading me to believe it was a glitch with the latest version of Bridge I’d installed a couple days earlier.

I uninstalled Bridge 2020 and reinstalled Bridge 2019, and guess what…it was gone. If I toggled hidden folders in Bridge it showed up, but was otherwise not visible.

Mystery solved. It’s a glitch in the Adobe Software. A glitch in a piece of Adobe software?! Color me shocked.

Further research into exactly what this “dev” volume was what led me to the diagram above. Realizing I’d never fully understand why it’s there, but knowing it’s supposed to be there, I walked away and got on with my life. Much like theoretical physics, the new volume structure in macOS is something I’ll never understand.

0 comments