Files are skeuomorphic. That’s a nice fancy word. But it just means that they’re a digital concept that mirrors a physical item. A Word document, for example, is like a piece of paper, sitting on your desk(top). A jpeg is like a painting and so on. They each have a little icon that looks like the physical thing they represent. A pile of paper, a picture frame, a manilla folder. It’s kind of charming really.
One thing I like about files is that there’s a consistent way of interacting with them, no matter what’s inside. Those things I mentioned above — copying, sorting, defragging — I can do those to any file. It could be an image, part of a game or a list of my favourite utensils. Defragmenter doesn’t care. It doesn’t judge the contents.
I’ve had a love of files since I first started creating them in Windows 95. But I’ve noticed that we are starting to move away from the file as a fundamental unit of work.
The Rise of the Services.mp3
As a teenager I indulged in the digital equivalent of collecting and managing vinyl: MP3 files. So many 128kbps MP3 files. Ripped from CDs or passed around between friends. If you were lucky enough to own a CD-rewriter you could burn them onto a CD and pass them around that way. CDs were 700mb. That’s nearly 500 floppy disks!
I’d go through painstakingly adding IDv1 and IDv2 tags. As time went on, people started to develop tools that would fetch the track listings automatically from the cloud, so you could check and validate your MP3s. Sometimes I’d even listen to the damn things. Although, I suspect the time spent organising and validating them vastly outweighed the time spent listening.
Then about ten years ago everyone started to use this green Swedish Company. You could just stream whatever you wanted, whenever you wanted. Well, I thought. That’s all very well. But what’s the quality like? Is it better than my 128kbps MP3s?
Yes. It turned out. Yes it was.
Along the way, 128kbps, which we had been told was “indistinguishable” from the massive wav files that come on CDs, had become rubbish. Now MP3s came at 320kbps. On messageboards people performed spectral analysis on the files, producing brightly green and blue coloured charts to “prove” that the files sounded good.
It was about this time that gold plated SCART monster cables were a thing.
The files on streaming services were good enough quality, available on more devices and gave you access to all recorded music, not just the MP3s you happened to have on your computer. You didn’t need a carefully crafted collection of files on your hard drive anymore. You just needed a username and password to Spotify and you were away.
Well, I thought, that’s nice, but I’ve also got these massive video files I’ve ripped from DVDs. The internet is way to slow for me to stream video like that.
Burying the Files.png
I used to have a Sony Ericsson with the catchy name of k610i. It was red and I loved it. I could connect it to my computer and copy files across. It didn’t have a headphone port, so I had to use an adapter or the special headphones that came with it. In many ways it was ahead of its time.
Later, when I had more money and the technology had moved on, I got an iPhone. Obviously, they are lovely. Everyone knows that. They’re beautiful, the brushed aluminum that is black, so black, blacker than darkness itself, and medical grade glass are near perfect items brought down from the gods themselves.
But they don’t make it that easy to get to your files. Images are dumped into a big stream, sorted by date. Audio is somewhere in iTunes. Notes are… in a list? Apps are scattered around the desktop. Some of my files are in iCloud. You can email photos to liberate them from the iPhone, and through a convoluted method via iTunes you can access some files within certain apps. But those files are transitory. Cached and may be deleted without warning. These aren’t like the carefully crafted files and folders on my computer.
On the Mac, iTunes sorts out your music files for you. They’re handled by the system. The interface displays the music to you and you can sort the files there. But if you look under hood, at the files themselves, you see a rabbit warren of mess, weird names and strange folders. “Don’t bother yourself with these”, the computer says, “I’ll handle this for you.” But I do bother myself with them.
I like being able to look at and access my files. But now the systems I use try to stop me doing so. “No,” they say, “access them through these bespoke, proprietary interfaces”. I just want my file browser back, but now I’m not allowed it. It’s a relic of an earlier era.
Yet I can’t help missing those files and folders and the control I had with them.
Caching and Dependencies.tmp
I started building websites in the days when 1px by 1px transparent gifs were a thing and the proper way to make a two column layout was to use a table. As time went on, best practice changed and I happily repeated the mantra that tables should only be used for tabular data and not for layout as I gradually struggled to convert my trivial layouts into CSS. At least it’s not a table, I said proudly as I looked upon my three column layout that didn’t work properly in Firefox.
Now when I build websites I run
npm install and download 65,000 dependencies that get dropped into a node_modules folder. So many files. I don’t care about them though. I just delete the folder, and run
npm install again when I need to. They’re nothing to me.
The other day, I came across a website I’d written over two decades ago. I double clicked the file and it opened and ran perfectly. Then I tried to run a website I’d written eighteen months ago and found I couldn’t run it without firing up a webserver, and when I ran
npm install one or two of those 65,000 files had issues that meant node failed to install them and the website didn’t run. When I did get it working, it needed a database. And then it relied on some third party APIs and there was an issue with CORS because I hadn’t whitelisted localhost.
My website made of files carried on chugging along. This isn’t me saying that things were better in the old days. I’m just saying… years ago websites were made of files, now they are made of dependencies.
Everything’s a link.lnk
No files were harmed in the making of this article. I went to Medium and started typing. In the background my words were sent to a database.
The unit of creation has moved from the file to the database entry.
In some ways, that doesn’t make a huge difference. The data is the same, just stored in a database rather than an HTML document. The URL could even be the same, just behind the scenes it fetches the content from a different type of data store. But the implications are much bigger. The content is dependent on a whole heap of infrastructure, rather than being able to stand on its own.
This almost seems to act to reduce the value of any individual creative act. Rather than warranting their own file, they’re all just another line in a database table somewhere in the sky. My article, rather than being in it’s only file, standing on its own, is just a tiny cog in a machine.
Online services have started violating what I thought was a fundamental tenet of digital file manipulation. When I copy a file from one place to another, the file I get at the end is identical to the one I started with. These are digital representations of data that can be copied exactly, bit for bit.
Yet when I upload photos into Google cloud then download them again, the file I end up with is different from the one I started with. It’s been transcoded, re-encoded, compressed, optimized. Messed with. The spectral analysts would be furious. It’s like a photocopy, where the pages get lighter and messier over time. I half expect one of Google’s AI fingers to appear in the corner of one of my photos.
When I airdrop a video there’s a long initial process where the iPhone is doing something. What is my little super computer up to? I’m suspicious. “You’re transcoding, aren’t you?” I accuse it. It’s only later, when I eventually get the file somewhere I can use it that I find it’s been pushed and pulled so many times it’s a husk of its former glory.
No more definitive files.webm
Like everyone I have a mess of online services, all increasingly mixed up between my work and personal life. Dropbox, Google Drive, Box, OneDrive, Slack, Google Docs, and so on. There are others. So many others. WeTransfer, there’s another one. Trello. Gmail. People at work send me a link to a Google Sheet, I open it, and now it’s saved in my personal Google Drive next to a photo of a cute chicken I shared with my mum and a document listing the different computer mice I was considering buying in 2011.
The default view in Google Docs is all files sorted by the order you most recently opened them. I can’t sort or organise them. They’re just there, ordered in a way that prioritises the new over the important.
I don’t like this shift from timeless content to what is newest. Now, when I visit websites, they promote to me the latest thing. Why should the content that is newest be the most important? It seems so unlikely that something that was just created would happen to be better than everything created throughout all time. What are the odds that every time I arrive at the site, the pinnacle of human achievement has just been breached. But we don’t seem to have a way of sorting by quality. Only by recency.
All of these services, at least for me, are a mess. A dumping ground of odds and ends. Maybe this is how everyone else manages their files. Whenever I use anyone else’s computer, I’m always amazed by the mess of files they have all over the place. Unsorted, disorganised. How do they find anything?
This has taken away the sense of a definitive file. That file in Dropbox: is it the latest version? Or is that just a copy of one that really lives on my computer. Or did someone email a newer version? Or put it into Slack? And in a weird way that devalues the content in the files. I don’t trust them anymore. If I look at a file in Dropbox I think to myself: “Oh, there’s probably a newer version.”
Perhaps this is the archivist in me, but this process of creating files and flinging them into an unsorted pot and then searching or hoping that the newest one is the one we want gives me the collywobbles. It seems like a rejection of our past work, to just sling all the files into a heap, immediately devaluing them as soon as something newer comes along.
At work, I see colleagues creating files, emailing them and not even bothering to save the attachments to their hard drive. Their inbox is their new file management system. “Have you got that spreadsheet?” they ask. Someone hunts through their inbox and forwards the person back the email they sent. Is this really how we manage data in the 21st Century? It seems a strange backwards step.
I miss files. I still create many of my own, but increasingly, that seems an anachronism, like using a quill rather than a pen. I miss the universality of files. The fact they can work anywhere, be moved around easily.
The file has been replaced with the platform, the service, the ecosystem. This is not to say that I’m proposing we lead a uprising against services in attempt to overthrow our seed-funded overlords. You can’t throw your clogs into the internet pipes in an attempt to halt progress. More I say this to mourn the loss of our innocence before capitalism inevitably invaded the internet. When we create now, our creations are part of an enormous system. Our contribution a tiny speck in an elastic database cluster. Rather than buying and collecting music, videos or other cultural artefacts, we are exposed to the power hose: all culture, raging over us, for $12.99 a month (or $15.99 HD) as long as we keep up our payments like good economic entities. When we stop paying, we’re left with nothing. No files, the service is revoked.
Obviously files are still around. It’s just we’re increasingly abstracted away from them. I keep my own assemblage of files. My own little world. In that way I’m an anachronism that’s somehow bubbled up from the bottom of that most recently edited list.
All Rights Reserved for Simon Pitt