WEBVTT 00:00:00.000 --> 00:00:03.180 Right now, you are probably staring at a sleek, 00:00:03.779 --> 00:00:07.040 modern computer desktop or, you know, maybe a 00:00:07.040 --> 00:00:09.679 really messy one. Most likely messy. Yeah, true. 00:00:10.000 --> 00:00:12.439 But somewhere hidden in the corner of your screen 00:00:12.439 --> 00:00:15.619 is a graveyard and it's a graveyard that actually 00:00:15.619 --> 00:00:18.480 sparked a decades old war. Oh, totally. Fought 00:00:18.480 --> 00:00:21.519 with like multi -million dollar legal briefs 00:00:21.519 --> 00:00:24.059 and some deeply, deeply clever software engineering. 00:00:24.079 --> 00:00:27.219 Exactly. So welcome to today's deep dive. We 00:00:27.219 --> 00:00:30.030 are taking a stack of sources. Primarily, this 00:00:30.030 --> 00:00:32.850 incredibly comprehensive Wikipedia article on 00:00:32.850 --> 00:00:35.409 trashing computing to explore something you use 00:00:35.409 --> 00:00:38.509 literally every single day. It really is the 00:00:38.509 --> 00:00:41.109 ultimate hidden in plain sight topic. Most of 00:00:41.109 --> 00:00:42.929 us don't give a second thought to the digital 00:00:42.929 --> 00:00:44.869 trash bin. I mean, why would you? Right. But 00:00:44.869 --> 00:00:46.649 it represents one of the most critical shifts 00:00:46.649 --> 00:00:48.890 in how humans actually interact with machines. 00:00:49.329 --> 00:00:51.590 Also, I love the setup we have today. Yeah, I 00:00:51.590 --> 00:00:53.329 have to point this out for you listening at home. 00:00:53.869 --> 00:00:56.539 Looking at our expert right now. They are seated 00:00:56.539 --> 00:00:59.640 against this amazing dynamic backdrop. It keeps 00:00:59.640 --> 00:01:03.479 shifting between like vintage 1980s computer 00:01:03.479 --> 00:01:06.640 manuals, then to glowing green command line text, 00:01:06.900 --> 00:01:10.400 and then back to these modern sleek desktop environments. 00:01:10.579 --> 00:01:13.340 It is very cool. It really sets the mood for 00:01:13.340 --> 00:01:16.620 digital archeology. It does, because our mission 00:01:16.620 --> 00:01:20.359 today is to uncover the history, the hidden technical 00:01:20.359 --> 00:01:23.140 mechanics, and honestly, the surprising psychological 00:01:23.140 --> 00:01:26.500 design behind that little icon. is wild when 00:01:26.500 --> 00:01:29.079 you realize that every single time you casually 00:01:29.079 --> 00:01:31.620 toss away a blurry photo or you scrap a messy 00:01:31.620 --> 00:01:34.719 draft document, you're participating in a carefully 00:01:34.719 --> 00:01:36.799 crafted illusion. Okay, let's unpack this because 00:01:36.799 --> 00:01:38.219 we have to start with the core definition, right? 00:01:38.280 --> 00:01:41.299 The digital trash bin is fundamentally a graphical 00:01:41.299 --> 00:01:45.420 user interface desktop metaphor. Yes, a GI metaphor. 00:01:45.599 --> 00:01:47.420 Right. But to understand why developers felt 00:01:47.420 --> 00:01:49.219 the need to invent a metaphorical garbage can 00:01:49.219 --> 00:01:51.200 in the first place, we have to look at what using 00:01:51.200 --> 00:01:53.299 a computer actually felt like before it existed. 00:01:53.620 --> 00:01:56.329 Which was not fun. No, it was terrifying. If 00:01:56.329 --> 00:01:58.689 we connect this to the bigger picture, you really 00:01:58.689 --> 00:02:01.629 have to imagine the sheer anxiety of early computing. 00:02:01.810 --> 00:02:04.230 Oh, I can only imagine. Like, before graphical 00:02:04.230 --> 00:02:06.489 interfaces, you were just staring at a command 00:02:06.489 --> 00:02:10.229 line prompt. Just glowing text on a black screen. 00:02:10.389 --> 00:02:13.310 The green text from your backdrop. Exactly. And 00:02:13.310 --> 00:02:15.889 if you wanted to remove a file, you typed a command, 00:02:16.229 --> 00:02:20.550 like RM in UNIX -based systems, and you hit Enter, 00:02:21.189 --> 00:02:24.979 and that was it. The file was just gone. Instantly. 00:02:25.139 --> 00:02:28.080 Oh. Yeah, there was no, are you sure, prompt. 00:02:28.180 --> 00:02:31.620 There was no safety net at all. Which means literally 00:02:31.620 --> 00:02:34.599 one typo could destroy weeks of work. Absolutely. 00:02:34.919 --> 00:02:37.689 One straight keystroke and boom. Gone. I mean, 00:02:37.710 --> 00:02:39.889 the psychological paralysis that most have induced 00:02:39.889 --> 00:02:43.550 is crazy, especially for everyday office workers 00:02:43.550 --> 00:02:45.030 who are being introduced to computers for the 00:02:45.030 --> 00:02:47.449 very first time. This is the late 70s, early 00:02:47.449 --> 00:02:49.469 80s. Right. They were used to physical filing 00:02:49.469 --> 00:02:52.490 cabinets. Exactly. And if every single p -stroke 00:02:52.490 --> 00:02:55.509 carries the risk of permanent destruction, you 00:02:55.509 --> 00:02:57.310 aren't going to experiment. You are going to 00:02:57.310 --> 00:03:00.169 be terrified of the machine. And that is exactly 00:03:00.169 --> 00:03:02.330 the problem that developers were facing. The 00:03:02.330 --> 00:03:04.569 true purpose of the trash metaphor wasn't really 00:03:04.569 --> 00:03:08.080 just file management. I mean, it was, but mostly 00:03:08.080 --> 00:03:10.539 it was designed to lift the burden of perfection 00:03:10.539 --> 00:03:12.979 from the user. Oh, that's a great way to phrase 00:03:12.979 --> 00:03:14.819 it. Yeah. And the source material developers 00:03:14.819 --> 00:03:17.919 actually refer to this as providing a grace period. 00:03:18.099 --> 00:03:20.379 A grace period. Right. OK, so think of the digital 00:03:20.379 --> 00:03:24.180 trash bin like a digital holding cell. Right. 00:03:24.259 --> 00:03:26.860 Or like a purgatory. It's not a landfill where 00:03:26.860 --> 00:03:29.740 things are destroyed immediately. It's a psychological 00:03:29.740 --> 00:03:32.699 safety net. Exactly. By creating the sort of 00:03:32.699 --> 00:03:36.710 staging area between your active workspace, and 00:03:36.710 --> 00:03:39.949 the actual permanent deletion of the file, software 00:03:39.949 --> 00:03:42.610 engineers basically gave users permission to 00:03:42.610 --> 00:03:45.669 be messy. To make mistakes. Yes. It fundamentally 00:03:45.669 --> 00:03:47.629 changes your relationship with the computer. 00:03:47.949 --> 00:03:49.650 It gives you the confidence to actually clean 00:03:49.650 --> 00:03:51.810 up your desktop because you know you aren't making 00:03:51.810 --> 00:03:53.770 an irreversible decision. Right, because you 00:03:53.770 --> 00:03:56.650 can actually just open up the trash, browse your 00:03:56.650 --> 00:03:59.009 quote unquote deleted files as if they were in 00:03:59.009 --> 00:04:00.610 a normal directory. Yeah, they just sit there. 00:04:00.719 --> 00:04:03.159 And you can just pull that spreadsheet back out 00:04:03.159 --> 00:04:05.120 if you realize, oh, wait, I made a mistake. I 00:04:05.120 --> 00:04:07.800 actually need this. Exactly. This concept of 00:04:07.800 --> 00:04:11.099 skeuomorphism, which is designing digital objects 00:04:11.099 --> 00:04:13.919 to mimic their real world counterparts, it was 00:04:13.919 --> 00:04:16.459 so crucial for reducing that learning curve. 00:04:17.060 --> 00:04:19.379 But they didn't just immediately land on the 00:04:19.379 --> 00:04:22.279 perfect trash can icon, did they? Figuring out 00:04:22.279 --> 00:04:24.459 exactly what that real world counterpart should 00:04:24.459 --> 00:04:27.120 look like took some iterations. Oh, a lot of 00:04:27.120 --> 00:04:29.180 iterations. And some of them were a bit intense. 00:04:29.279 --> 00:04:33.589 Yeah. Which brings us to late 1978. There's a 00:04:33.589 --> 00:04:36.170 developer named Bill Atkinson, and he is working 00:04:36.170 --> 00:04:38.529 on the Appalisa. A legendary machine. Truly. 00:04:39.410 --> 00:04:41.290 And he's tasked with building an icon -based 00:04:41.290 --> 00:04:43.970 file manager. And according to the historical 00:04:43.970 --> 00:04:47.879 records in our sources, By March 1982, Atkinson 00:04:47.879 --> 00:04:50.519 produces a mock -up for deleting files that is 00:04:50.519 --> 00:04:53.660 just. It is incredibly visceral. Visceral is 00:04:53.660 --> 00:04:55.420 definitely the word for it. His original design 00:04:55.420 --> 00:04:57.620 for the trash icon actually featured buzzing 00:04:57.620 --> 00:05:00.639 flies. Buzzing flies. It's just a fascinating 00:05:00.639 --> 00:05:03.240 choice, isn't it? It's gross. Well, yeah. He 00:05:03.240 --> 00:05:05.579 wanted to communicate, decay. He wanted the user 00:05:05.579 --> 00:05:07.899 to intuitively understand, without reading a 00:05:07.899 --> 00:05:12.160 manual, that this is where useless, rotting data 00:05:12.160 --> 00:05:14.769 goes to die. But it's almost too aggressive. 00:05:14.910 --> 00:05:17.730 I mean, you have this pristine digital desk and 00:05:17.730 --> 00:05:20.610 you're just putting literal rotting garbage on 00:05:20.610 --> 00:05:23.269 it. Yeah, it was a bit much. So ultimately, they 00:05:23.269 --> 00:05:25.670 dialed it back. Thankfully. When the Apple Lisa 00:05:25.670 --> 00:05:29.300 officially launched in 1983. The buzzing flies 00:05:29.300 --> 00:05:32.560 were gone. Replaced by just a wastebasket icon. 00:05:32.720 --> 00:05:35.480 Right. And it was drawn to look like a standard, 00:05:35.980 --> 00:05:38.759 physical, alley -style garbage can, you know, 00:05:38.819 --> 00:05:40.639 complete with those vertical lines to look like 00:05:40.639 --> 00:05:44.120 a ribbed surface, an open lid, and a little handle 00:05:44.120 --> 00:05:46.220 on the bottom. Classic. And Apple knew exactly 00:05:46.220 --> 00:05:48.939 how powerful this visual shorthand was. Their 00:05:48.939 --> 00:05:51.319 marketing at the time heavily leaned into this 00:05:51.319 --> 00:05:53.480 skeuomorphic design. Oh, they used it everywhere. 00:05:53.620 --> 00:05:55.399 They ran advertisements essentially arguing, 00:05:55.480 --> 00:05:57.120 hey, if you can find the trash can, you already 00:05:57.120 --> 00:05:59.029 know how to... on a computer. Exactly, they were 00:05:59.029 --> 00:06:01.730 borrowing your real -world intuition to completely 00:06:01.730 --> 00:06:04.889 bypass the need for a technical manual. And then, 00:06:05.350 --> 00:06:08.730 you know, in 1984 the legendary designer Susan 00:06:08.730 --> 00:06:11.730 Kerr comes in and refines the icon for the classic 00:06:11.730 --> 00:06:15.730 Mac OS. She gives us that sleek closed lid design 00:06:15.730 --> 00:06:17.949 that became globally recognized. Truly iconic, 00:06:18.209 --> 00:06:20.339 but... You know, this massive success creates 00:06:20.339 --> 00:06:22.540 a completely new problem for Apple. Oh, of course 00:06:22.540 --> 00:06:25.399 it does. Because if Apple creates a visual metaphor 00:06:25.399 --> 00:06:27.980 that instantly teaches everyone in the world 00:06:27.980 --> 00:06:29.800 how to use a computer. Naturally, every other 00:06:29.800 --> 00:06:31.199 software company is going to want to use it, 00:06:31.259 --> 00:06:34.000 too. Right. Which leads to a massive legal battle. 00:06:35.120 --> 00:06:38.019 But wait, I have to ask, how can a company claim 00:06:38.019 --> 00:06:40.560 ownership over a concept as basic as throwing 00:06:40.560 --> 00:06:43.680 garbage away? Didn't physical trash cans exist 00:06:43.680 --> 00:06:47.029 for, like, centuries? You would think, and this 00:06:47.029 --> 00:06:49.089 raises a really important question about intellectual 00:06:49.089 --> 00:06:51.449 property in the digital age, like who actually 00:06:51.449 --> 00:06:53.990 owns a metaphor? Right. Well, Apple certainly 00:06:53.990 --> 00:06:56.389 believed they owned this one. This resulted in 00:06:56.389 --> 00:06:59.589 the landmark 1988 lawsuit, Apple Computer Inc. 00:06:59.850 --> 00:07:01.949 versus Microsoft Core. Which went on for a long 00:07:01.949 --> 00:07:05.069 time, right? Right. Oh, yeah. It dragged on until 00:07:05.069 --> 00:07:09.509 a final appeal decision in 1994. Basically, Apple 00:07:09.509 --> 00:07:12.509 sued Microsoft, claiming that Windows had stolen 00:07:12.509 --> 00:07:15.310 the look and feel of the Macintosh operating 00:07:15.310 --> 00:07:17.269 system. They were trying to copyright the entire 00:07:17.269 --> 00:07:19.910 experience of using a graphical desktop. Precisely. 00:07:20.110 --> 00:07:23.550 They wanted to own the whole GUI. But the court's 00:07:23.550 --> 00:07:26.490 ruling was incredibly nuanced, actually. Oh, 00:07:26.589 --> 00:07:29.660 so. It relied on a legal concept known as the 00:07:29.660 --> 00:07:33.180 idea expression dichotomy. Okay. The judge essentially 00:07:33.180 --> 00:07:36.339 dissected the graphical user interface into discrete 00:07:36.339 --> 00:07:39.519 elements. The court ruled that the idea of using 00:07:39.519 --> 00:07:42.600 overlapping windows or the idea of using a metaphorical 00:07:42.600 --> 00:07:45.199 container to delete files was functional. Meaning 00:07:45.199 --> 00:07:47.759 it's just a tool. Exactly. It was a utilitarian 00:07:47.759 --> 00:07:49.699 solution to a software problem and therefore 00:07:49.699 --> 00:07:52.060 you cannot populate the idea itself. Okay, so 00:07:52.060 --> 00:07:54.079 the court is saying Microsoft is allowed to have 00:07:54.079 --> 00:07:56.759 a digital holding cell for deleted files. Yes. 00:07:57.279 --> 00:07:59.360 However, the court also ruled that while the 00:07:59.360 --> 00:08:01.959 functional idea is free to use, Apple's specific 00:08:01.959 --> 00:08:04.240 artistic expression of that idea, like the ribbed 00:08:04.240 --> 00:08:07.199 lines, the handle, the closed lid of their specific 00:08:07.199 --> 00:08:09.319 trash can that was highly original and protected 00:08:09.319 --> 00:08:11.420 by copyright. So you can build a way to delete 00:08:11.420 --> 00:08:13.819 things, but you absolutely cannot draw a trash 00:08:13.819 --> 00:08:15.600 can to do it. Right. You have to draw something 00:08:15.600 --> 00:08:18.899 else entirely. That completely explains the bizarre 00:08:18.899 --> 00:08:22.720 landscape of 1990s software. Forced by this legal 00:08:22.720 --> 00:08:26.120 ruling, non -Apple developers had to scramble 00:08:26.120 --> 00:08:29.420 to invent alternative visual metaphors. They 00:08:29.420 --> 00:08:32.620 had to achieve the exact same psychological goal 00:08:32.620 --> 00:08:35.159 without violating the copyright. Yeah, you saw 00:08:35.159 --> 00:08:37.720 incredible fragmentation. Suddenly, software 00:08:37.720 --> 00:08:40.679 suites introduced tools called the Smart Eraser 00:08:40.679 --> 00:08:43.860 or the Shredder, which is deeply literal. But 00:08:43.860 --> 00:08:46.279 the most famous pivot, of course, came from Microsoft. 00:08:46.600 --> 00:08:49.720 When they designed Windows 95, they bypassed 00:08:49.720 --> 00:08:52.039 the trash can entirely and gave the world the 00:08:52.039 --> 00:08:54.840 recycle bin. The recycle bin. It is just wild 00:08:54.840 --> 00:08:56.799 to think that the Windows recycle bin, arguably 00:08:56.799 --> 00:08:59.220 one of the most recognizable digital icons on 00:08:59.220 --> 00:09:02.240 the planet, was born largely as a copyright dodge. 00:09:02.759 --> 00:09:04.960 Seriously. But Microsoft couldn't just change 00:09:04.960 --> 00:09:07.460 the name and the picture, right? Implementing 00:09:07.460 --> 00:09:09.539 the recycle bin forced them to build an entirely 00:09:09.539 --> 00:09:12.159 new mechanical architecture under the hood. Oh, 00:09:12.159 --> 00:09:15.299 absolutely. And here's where it gets really interesting. 00:09:16.080 --> 00:09:18.879 Because the visual metaphor we see on screen 00:09:18.879 --> 00:09:23.019 completely masks the mathematical reality of 00:09:23.019 --> 00:09:25.419 what the computer is actually doing. Right. The 00:09:25.419 --> 00:09:27.700 graphical interface is essentially a puppet show. 00:09:27.779 --> 00:09:29.840 The puppet show, yeah. And the recycle bin is 00:09:29.840 --> 00:09:32.100 one of the most elaborate tricks it performs. 00:09:32.240 --> 00:09:34.360 OK, to illustrate this, let's look at a logical 00:09:34.360 --> 00:09:37.899 puzzle. Say I am cleaning up my computer. I take 00:09:37.899 --> 00:09:41.580 a file called financialreport .pdf, and I drag 00:09:41.580 --> 00:09:44.110 it into the recycle bin. OK. Standard procedure. 00:09:44.549 --> 00:09:47.289 Later, in a completely different folder, I find 00:09:47.289 --> 00:09:49.970 another file that is accidentally also named 00:09:49.970 --> 00:09:52.929 financialreport .pdf. It happens all the time. 00:09:53.070 --> 00:09:55.450 Right. And I drag that second file into the recycle 00:09:55.450 --> 00:09:58.629 bin, too. Now, in any normal computing scenario, 00:09:58.990 --> 00:10:01.350 if you try to put two files with the exact same 00:10:01.350 --> 00:10:03.970 name in the exact same folder, the system stops 00:10:03.970 --> 00:10:05.789 you. Yeah, it throws an error. It asks if you 00:10:05.789 --> 00:10:08.450 want to overwrite the first file. Exactly. But 00:10:08.450 --> 00:10:11.330 the trash never does that. It happily holds both. 00:10:11.549 --> 00:10:14.090 How is the trash holding duplicates without crashing? 00:10:14.470 --> 00:10:16.029 Because the files aren't actually going into 00:10:16.029 --> 00:10:18.429 a single beautified container at all. Really? 00:10:18.590 --> 00:10:21.610 Yeah. When you drag a file to the recycle bin 00:10:21.610 --> 00:10:24.730 on Windows or the trash on a Mac, you aren't 00:10:24.730 --> 00:10:27.889 moving it to a magical bin on your desktop. You 00:10:27.889 --> 00:10:30.889 are actually moving it to deeply hidden system 00:10:30.889 --> 00:10:34.179 level folders. Hidden folders. On modern Windows, 00:10:34.220 --> 00:10:37.100 for example, the operating system creates a hidden 00:10:37.100 --> 00:10:40.980 directory called $recycle .bin at the very root 00:10:40.980 --> 00:10:43.460 of your hard drive. But just hiding the folder 00:10:43.460 --> 00:10:46.419 doesn't solve the duplicate name problem. Like, 00:10:46.559 --> 00:10:49.919 two identical file names inside $recycle .bin 00:10:49.919 --> 00:10:52.340 should still trigger an overwrite conflict. You 00:10:52.340 --> 00:10:54.480 would think so. It feels like the operating system 00:10:54.480 --> 00:10:57.340 has to put these files into like a witness protection 00:10:57.340 --> 00:10:59.909 program. It can't just hide them. It has to assign 00:10:59.909 --> 00:11:01.990 them entirely new identities to prevent them 00:11:01.990 --> 00:11:04.330 from colliding. That is the perfect analogy. 00:11:04.549 --> 00:11:06.909 The witness protection program, the system absolutely 00:11:06.909 --> 00:11:08.830 strips them of their original identities. How 00:11:08.830 --> 00:11:11.690 does it do that? Historically, prior to Windows 00:11:11.690 --> 00:11:14.669 Vista, when you moved a file to the bin, the 00:11:14.669 --> 00:11:16.929 operating system physically moved it to the hidden 00:11:16.929 --> 00:11:19.470 folder and instantly renamed it using a rigid 00:11:19.470 --> 00:11:21.889 formula. It would rename the file starting with 00:11:21.889 --> 00:11:24.350 a D for deleted. Makes sense. Followed by the 00:11:24.350 --> 00:11:26.879 original drive letter. then a sequential index 00:11:26.879 --> 00:11:29.559 number, and finally the original file extension. 00:11:29.960 --> 00:11:32.960 So your financialreport .pdf secretly became 00:11:32.960 --> 00:11:36.279 something completely unrecognizable, like dc1 00:11:36.279 --> 00:11:38.940 .pdf? Exactly. It completely masked the real 00:11:38.940 --> 00:11:41.580 name at the file system level. Okay, but if the 00:11:41.580 --> 00:11:43.860 operating system secretly renamed my file to 00:11:43.860 --> 00:11:47.759 dc1 .pdf, how does my recycle bin know to still 00:11:47.759 --> 00:11:50.980 display the name financialreport .pdf when I 00:11:50.980 --> 00:11:53.320 open the bin to look inside. Like, I still see 00:11:53.320 --> 00:11:55.559 the original name. Because the system also maintains 00:11:55.559 --> 00:11:58.799 a secret master ledger. Oh, a ledger? Yeah. In 00:11:58.799 --> 00:12:01.240 those older Windows versions, it generated a 00:12:01.240 --> 00:12:05.090 hidden binary file called info2. This ledger 00:12:05.090 --> 00:12:07.529 meticulously recorded the new fake name, the 00:12:07.529 --> 00:12:10.149 original real name, and the exact directory path 00:12:10.149 --> 00:12:12.590 the file originally came from. Wow. So when you 00:12:12.590 --> 00:12:14.730 double -click the recycle bin icon on your desktop, 00:12:14.909 --> 00:12:17.509 the interface reads that info to ledger and actively 00:12:17.509 --> 00:12:19.750 projects an illusion. A puppet show. Exactly. 00:12:20.070 --> 00:12:22.429 It renders the original names for you, masking 00:12:22.429 --> 00:12:25.490 the chaotic, sequentially numbered reality happening 00:12:25.490 --> 00:12:28.049 at the file system level. The software is literally 00:12:28.049 --> 00:12:30.230 lying to me to make me feel comfortable. It is 00:12:30.230 --> 00:12:33.500 brilliant. It really is. And this architecture 00:12:33.500 --> 00:12:35.659 evolved to become even more sophisticated later 00:12:35.659 --> 00:12:40.399 on. Post Windows Vista, Microsoft abandoned that 00:12:40.399 --> 00:12:43.200 single Info2 ledger. Why? Because if the ledger 00:12:43.200 --> 00:12:45.460 gets corrupted, you lose everything in the bin. 00:12:45.980 --> 00:12:49.019 So now, when you delete a file, the system actually 00:12:49.019 --> 00:12:51.340 splits it into two distinct pieces. I get what 00:12:51.340 --> 00:12:53.340 are the pieces. It creates one file, starting 00:12:53.340 --> 00:12:56.659 with the character's dollar sign R, which holds 00:12:56.659 --> 00:12:59.879 the actual raw data of your PDF. The document 00:12:59.879 --> 00:13:02.840 itself. Right. Then it creates a second, entirely 00:13:02.840 --> 00:13:05.200 separate file, starting with dollar sign I, which 00:13:05.200 --> 00:13:07.879 contains the metadata. So the original name, 00:13:07.960 --> 00:13:10.500 the original location, and the timestamp of when 00:13:10.500 --> 00:13:12.730 you deleted it. The bin just reads the dollar 00:13:12.730 --> 00:13:15.830 sign I file. Yep. The recycle bin interface just 00:13:15.830 --> 00:13:18.190 stitches these dollar sign R and dollar sign 00:13:18.190 --> 00:13:20.509 I files together visually for you on the fly. 00:13:21.029 --> 00:13:22.990 But wait, if the system is just hiding these 00:13:22.990 --> 00:13:25.049 files in a hidden folder and changing their names, 00:13:25.429 --> 00:13:27.230 dragging something to the trash doesn't actually 00:13:27.230 --> 00:13:29.690 free up any hard drive space at all. No, not 00:13:29.690 --> 00:13:31.830 a single byte. The data is still sitting right 00:13:31.830 --> 00:13:33.809 there, taking up the exact same amount of room. 00:13:34.009 --> 00:13:36.629 That is the central trade -off of the grace period 00:13:36.629 --> 00:13:39.730 we talked about earlier. You are actively sacrificing 00:13:39.730 --> 00:13:42.210 storage capacity in exchange for psychological 00:13:42.210 --> 00:13:45.269 safety. Wow. The file isn't gone. The operating 00:13:45.269 --> 00:13:47.870 system just changed its address and hid it from 00:13:47.870 --> 00:13:49.769 your standard search functions. Which brings 00:13:49.769 --> 00:13:52.929 up another huge technical hurdle. What happens 00:13:52.929 --> 00:13:55.850 if I am working across multiple drives? Oh yeah, 00:13:55.950 --> 00:13:59.850 this is a big one. Say I have a massive 50 gigabyte 00:13:59.850 --> 00:14:02.889 video file sitting on an external USB thumb drive. 00:14:02.950 --> 00:14:06.309 Okay. If I drag that video file to the trash 00:14:06.309 --> 00:14:09.509 on my Mac's main desktop, copying 50 gigabytes 00:14:09.509 --> 00:14:11.889 from a USB drive to the main hard drive's hidden 00:14:11.889 --> 00:14:14.649 trash folder would take several minutes. At least. 00:14:14.769 --> 00:14:17.230 But when you do it, the trash icon updates instantly. 00:14:17.409 --> 00:14:19.539 There's no loading bar. You've hit on a major 00:14:19.539 --> 00:14:21.879 architectural challenge. Because moving data 00:14:21.879 --> 00:14:24.200 across different physical drives or partitions 00:14:24.200 --> 00:14:27.559 is computationally expensive. It requires literally 00:14:27.559 --> 00:14:30.080 rewriting all those ones and zeros to a new disk. 00:14:30.100 --> 00:14:32.759 Wait, which takes time? To bypass this, the operating 00:14:32.759 --> 00:14:34.759 system doesn't actually move the file to your 00:14:34.759 --> 00:14:36.799 main hard drive at all. So where does it go? 00:14:37.200 --> 00:14:40.080 Instead, it creates a separate, hidden trash 00:14:40.080 --> 00:14:42.279 directory on every single drive you connect. 00:14:42.419 --> 00:14:45.210 On the external drive itself. Yes. On a Mac, 00:14:45.250 --> 00:14:48.009 for instance, it quietly creates a hidden folder 00:14:48.009 --> 00:14:51.429 called slash dot trashes right there on the external 00:14:51.429 --> 00:14:54.370 USB drive. Ah. So when I delete a file from the 00:14:54.370 --> 00:14:57.090 USB drive, the computer is just instantly shuffling 00:14:57.090 --> 00:14:59.389 the file's pointer into the hidden slash dot 00:14:59.389 --> 00:15:02.470 trashes folder on that exact same USB drive. 00:15:02.830 --> 00:15:05.389 It never travels to the main computer. Precisely. 00:15:05.590 --> 00:15:08.330 It's an instantaneous local reassignment. And 00:15:08.330 --> 00:15:10.730 this is why, if you delete a massive file from 00:15:10.730 --> 00:15:13.210 a thumb drive, then unplug the thumb drive and 00:15:13.210 --> 00:15:15.190 plug it into a completely different computer. 00:15:15.690 --> 00:15:17.929 That file is still secretly sitting in the hidden 00:15:17.929 --> 00:15:20.610 trash folder taking up space. Yep. You haven't 00:15:20.610 --> 00:15:22.909 freed up anything until you empty the trash while 00:15:22.909 --> 00:15:24.889 that specific drive is connected. Which means 00:15:24.889 --> 00:15:27.090 the graphical interface is projecting a unified 00:15:27.090 --> 00:15:30.700 illusion. It shows me one single trash can on 00:15:30.700 --> 00:15:34.320 my desktop. But under the hood, it's aggregating 00:15:34.320 --> 00:15:36.539 hidden folders scattered across every single 00:15:36.539 --> 00:15:39.279 hard drive and USB stick plugged into the machine. 00:15:39.620 --> 00:15:41.700 It's a miracle it works as well as it does. It 00:15:41.700 --> 00:15:44.639 is an incredibly complex orchestration. Just 00:15:44.639 --> 00:15:47.299 to let me throw something away. But as a user, 00:15:47.779 --> 00:15:50.070 you don't always want the puppet show. Sometimes 00:15:50.070 --> 00:15:52.429 you don't want the grace period. You just want 00:15:52.429 --> 00:15:55.129 the raw mathematics of the machine to wipe the 00:15:55.129 --> 00:15:58.330 file instantly and give you your disk space back. 00:15:58.690 --> 00:16:00.450 The developers definitely accounted for that. 00:16:00.529 --> 00:16:02.409 If you understand the system, you can bypass 00:16:02.409 --> 00:16:04.289 the safety net entirely. How do you do that? 00:16:04.429 --> 00:16:06.909 On Windows, holding down the Shift key while 00:16:06.909 --> 00:16:09.669 hitting Delete completely skips the recycle bin. 00:16:09.809 --> 00:16:12.570 Oh, it just vaporizes it. Exactly. On a Mac, 00:16:12.710 --> 00:16:15.490 the equivalent is Option plus Command plus Delete, 00:16:15.509 --> 00:16:17.590 which is actually a feature they formally introduced 00:16:17.590 --> 00:16:20.919 in El Capiton. Good to know. And it's not just 00:16:20.919 --> 00:16:23.580 human power users who bypass this. The source 00:16:23.580 --> 00:16:25.980 material notes that low -level system utilities, 00:16:26.379 --> 00:16:28.340 or scripts run directly from the command prompt, 00:16:29.019 --> 00:16:31.340 often ignore the visual trash metaphor completely. 00:16:31.610 --> 00:16:34.529 which is a functional necessity. Your operating 00:16:34.529 --> 00:16:37.750 system is constantly generating, using and destroying 00:16:37.750 --> 00:16:40.850 thousands of invisible temporary cache files 00:16:40.850 --> 00:16:43.590 in the background every single hour. If every 00:16:43.590 --> 00:16:46.110 automated deletion went into the visual recycle 00:16:46.110 --> 00:16:48.350 bin, the user would open it up and just see a 00:16:48.350 --> 00:16:50.590 terrifying flood of system gibberish. It would 00:16:50.590 --> 00:16:52.750 be unusable. It would render the psychological 00:16:52.750 --> 00:16:55.509 safety net completely useless because the user 00:16:55.509 --> 00:16:57.629 would never be able to find their own deleted 00:16:57.629 --> 00:17:00.730 spreadsheet amidst all that noise. So... We have 00:17:00.730 --> 00:17:03.190 this magical holding cell storing hidden files 00:17:03.190 --> 00:17:06.029 with secret identities across multiple drives. 00:17:06.869 --> 00:17:10.170 But that leads to the inevitable problem of resources. 00:17:10.470 --> 00:17:13.430 Storage space. Right. If dragging a file to the 00:17:13.430 --> 00:17:15.690 trash doesn't actually delete it, eventually 00:17:15.690 --> 00:17:18.829 these hidden dollar sign recycle .bin folders 00:17:18.829 --> 00:17:21.450 are going to fill up the entire hard drive. How 00:17:21.450 --> 00:17:23.950 does the system manage capacity without breaking 00:17:23.950 --> 00:17:26.329 the illusion? Well, the rules governing capacity 00:17:26.329 --> 00:17:28.930 have shifted drastically over the decades, mostly 00:17:28.930 --> 00:17:31.289 reflecting how storage technology itself has 00:17:31.289 --> 00:17:34.089 changed. OK. Let's look at older Windows systems 00:17:34.089 --> 00:17:37.269 prior to Vista. The recycle bin wasn't a bottomless 00:17:37.269 --> 00:17:39.670 pit. It was governed by a strict mathematical 00:17:39.670 --> 00:17:42.970 quota. By default, it reserved a global setting 00:17:42.970 --> 00:17:45.910 typically 10 % of the host drive's total capacity. 00:17:46.250 --> 00:17:48.910 10 % makes sense. If I have 100 gigabyte drive, 00:17:49.109 --> 00:17:51.569 Reserving 10 gigabytes for mistake seems pretty 00:17:51.569 --> 00:17:53.930 reasonable. It does, but there was a bizarre 00:17:53.930 --> 00:17:56.950 historical limitation. No matter how massive 00:17:56.950 --> 00:18:00.170 your physical hard drive was, older Windows architectures 00:18:00.170 --> 00:18:03.549 imposed a hard cap. The recycle bin could absolutely 00:18:03.549 --> 00:18:07.170 not exceed 3 .99 gigabytes of space. Wait, 3 00:18:07.170 --> 00:18:10.710 .99 gigabytes? That is so oddly specific. It 00:18:10.710 --> 00:18:13.789 was a limitation of the FAT32 file system format. 00:18:14.150 --> 00:18:17.150 So what happens if I try to delete a single 5 00:18:17.150 --> 00:18:19.880 gigabyte video file on an old Windows machine. 00:18:20.400 --> 00:18:22.400 The system simply couldn't put it in the bin. 00:18:22.680 --> 00:18:24.599 It would throw an error message, prompting you 00:18:24.599 --> 00:18:27.240 to permanently delete the file immediately, completely 00:18:27.240 --> 00:18:29.279 removing your grace period for that file. Because 00:18:29.279 --> 00:18:31.779 it just physically couldn't fit. Right. But the 00:18:31.779 --> 00:18:34.079 more insidious problem happened when you naturally 00:18:34.079 --> 00:18:36.799 filled up that 3 .99 gigabyte quota over time 00:18:36.799 --> 00:18:39.119 with thousands of smaller files. Does it stop 00:18:39.119 --> 00:18:40.960 you from deleting more things? Like, does it 00:18:40.960 --> 00:18:42.960 tell you it's full? No, and that's the catch. 00:18:43.140 --> 00:18:45.200 The system doesn't warn you at all. Instead, 00:18:45.259 --> 00:18:47.319 it employs a first -in, first -out protocol. 00:18:47.720 --> 00:18:50.779 It quietly begins assassinating the oldest files 00:18:50.779 --> 00:18:53.000 at the bottom of the bin to make room for the 00:18:53.000 --> 00:18:55.279 new ones you are deleting today. Oh, wow. So 00:18:55.279 --> 00:18:57.680 your psychological safety net is entirely conditional. 00:18:57.839 --> 00:19:00.079 Completely conditional. Your grace period for 00:19:00.079 --> 00:19:02.700 a deleted file depends directly on how much other 00:19:02.700 --> 00:19:04.339 junk you happen to throw on top of it later. 00:19:04.539 --> 00:19:07.119 If I delete a lot of stuff on a Tuesday, the 00:19:07.119 --> 00:19:09.880 file I deleted on Monday might get secretly, 00:19:10.220 --> 00:19:12.240 permanently destroyed without me ever realizing 00:19:12.240 --> 00:19:15.130 it. Exactly. It was a very un - predictable safety 00:19:15.130 --> 00:19:17.589 net. And this is why modern mobile operating 00:19:17.589 --> 00:19:20.509 systems approach the psychology completely differently. 00:19:20.609 --> 00:19:24.609 If you look at Android 11 or the native photos 00:19:24.609 --> 00:19:28.170 and mail apps on iOS, they abandoned the invisible 00:19:28.170 --> 00:19:31.269 storage cap entirely. They replaced it with the 00:19:31.269 --> 00:19:33.509 dimension of time. Oh, right. They implement 00:19:33.509 --> 00:19:36.410 a strict 30 -day auto -delete countdown timer. 00:19:36.490 --> 00:19:39.269 Which is vastly superior from a user experience 00:19:39.269 --> 00:19:41.650 standpoint. It's totally transparent. You know 00:19:41.650 --> 00:19:44.130 with absolute certainty that you have exactly 00:19:44.130 --> 00:19:47.069 30 days to change your mind. It's no longer dependent 00:19:47.069 --> 00:19:50.089 on some hidden algorithmic calculation of gigabytes 00:19:50.089 --> 00:19:52.910 happening behind the scenes. Exactly. It replaces 00:19:52.910 --> 00:19:55.109 a confusing mechanical rule with a predictable 00:19:55.109 --> 00:19:58.130 human rule. And speaking of confusing rules, 00:19:58.210 --> 00:20:00.359 we have to talk about about what happens when 00:20:00.359 --> 00:20:03.539 these visual metaphors break down and actually 00:20:03.539 --> 00:20:06.039 cause user panic. I am so glad you brought this 00:20:06.039 --> 00:20:09.259 up. In the source material, there is one specific 00:20:09.259 --> 00:20:12.059 historical quirk that highlights exactly what 00:20:12.059 --> 00:20:14.759 happens when developers take a desktop metaphor 00:20:14.759 --> 00:20:17.519 way too far. It's my favorite part. It is wild. 00:20:17.619 --> 00:20:21.819 It's from the 1984 Mac OS. Back then, hard drives 00:20:21.819 --> 00:20:23.859 were prohibitively expensive, so most people 00:20:23.859 --> 00:20:26.259 ran the entire operating system directly from 00:20:26.259 --> 00:20:29.410 a floppy disk. But the computers only had one 00:20:29.410 --> 00:20:31.710 disk drive. So if you needed to load a different 00:20:31.710 --> 00:20:34.549 program, you had to physically eject the floppy 00:20:34.549 --> 00:20:36.130 disk that was already inside the machine. Right. 00:20:36.130 --> 00:20:38.269 And how did Apple's operating system require 00:20:38.269 --> 00:20:40.490 you to eject that disk? Oh, man. You had to use 00:20:40.490 --> 00:20:42.869 your mouse, click on the floppy disk icon on 00:20:42.869 --> 00:20:45.549 your screen, drag it across the desktop and drop 00:20:45.549 --> 00:20:47.970 it into the trash. What's fascinating here is 00:20:47.970 --> 00:20:50.569 the sheer cognitive dissonance this caused for 00:20:50.569 --> 00:20:54.049 a new computer user in 1984. I would be absolutely 00:20:54.049 --> 00:20:56.740 terrified. You just spent millions of dollars 00:20:56.740 --> 00:20:58.700 on marketing telling me that the trash is where 00:20:58.700 --> 00:21:01.339 my files go to be destroyed. Now you are telling 00:21:01.339 --> 00:21:03.519 me to take the physical floppy disk containing 00:21:03.519 --> 00:21:06.259 my life's work and throw it in the garbage just 00:21:06.259 --> 00:21:08.559 to get it out of the machine. It is the ultimate 00:21:08.559 --> 00:21:11.539 clash between object -oriented programming logic 00:21:11.539 --> 00:21:14.380 and human intuition. Makes no sense to a person. 00:21:14.519 --> 00:21:17.299 Right, but from the computer's internal logic, 00:21:17.599 --> 00:21:20.660 dragging an icon to the trash simply meant remove 00:21:20.660 --> 00:21:24.099 this object from my active desktop space. The 00:21:24.099 --> 00:21:25.819 operating system knew it wasn't going to format 00:21:25.819 --> 00:21:28.759 the disk. The code simply unmounted the volume 00:21:28.759 --> 00:21:31.119 and triggered the mechanical mechanism to pop 00:21:31.119 --> 00:21:33.740 the floppy out of the drive. But emotionally, 00:21:34.119 --> 00:21:36.180 asking a user to throw their valuable data into 00:21:36.180 --> 00:21:39.099 a garbage can was an abysmal design choice. It's 00:21:39.099 --> 00:21:41.859 basically asking the user to ignore the very 00:21:41.859 --> 00:21:44.339 metaphor you just taught them. It was so universally 00:21:44.339 --> 00:21:47.779 recognized as a failure of design that the Genome 00:21:47.779 --> 00:21:50.380 Human Interface Guidelines, which is a major 00:21:50.380 --> 00:21:52.920 set of design principles for Linux environments. 00:21:53.099 --> 00:21:55.779 They literally cite this exact historical quirk 00:21:55.779 --> 00:21:59.299 from 1984 as the prime textbook example of what 00:21:59.299 --> 00:22:03.539 not to do. Really? That's amazing. Yeah. It represents 00:22:03.539 --> 00:22:06.779 taking a visual metaphor way beyond its reasonable 00:22:06.779 --> 00:22:10.109 logical limits. Thankfully, Mac OS eventually 00:22:10.109 --> 00:22:12.950 fixed this. They implemented a dynamic change 00:22:12.950 --> 00:22:16.210 so that if you drag a disk icon today, the trash 00:22:16.210 --> 00:22:18.910 can instantly transforms into a universal eject 00:22:18.910 --> 00:22:21.190 symbol before you drop it. Right. The small visual 00:22:21.190 --> 00:22:23.990 cue that says, don't worry, we are just ejecting, 00:22:24.069 --> 00:22:26.630 not destroying. A tiny tweak that likely saved 00:22:26.630 --> 00:22:28.789 millions of users from a massive spike in blood 00:22:28.789 --> 00:22:31.210 pressure. Undoubtedly. So what does this all 00:22:31.210 --> 00:22:34.400 mean? We've traced this journey from the terrifying 00:22:34.400 --> 00:22:37.440 finality of the command line through Bill Atkinson's 00:22:37.440 --> 00:22:40.319 buzzing flies to the nuanced legal battles over 00:22:40.319 --> 00:22:43.279 copywriting and expression versus an idea. We've 00:22:43.279 --> 00:22:45.859 covered a lot of ground. We really have. We've 00:22:45.859 --> 00:22:47.799 seen how developers engineered hidden dollar 00:22:47.799 --> 00:22:50.460 sign R and dollar sign I metadata files to create 00:22:50.460 --> 00:22:52.859 the illusion of duplicates and how we shifted 00:22:52.859 --> 00:22:56.059 from rigid gigabyte limits to 30 -day timers. 00:22:56.519 --> 00:22:58.579 What I am taking away from this is that the graphical 00:22:58.579 --> 00:23:02.490 user interface is profoundly empathetic. Empathetic, 00:23:02.630 --> 00:23:05.170 yeah, I like that. It's a layer of code entirely 00:23:05.170 --> 00:23:08.009 dedicated to managing human anxiety. It bridges 00:23:08.009 --> 00:23:11.230 the gap between the cold binary reality of the 00:23:11.230 --> 00:23:15.690 machine and the messy indecisive reality of human 00:23:15.690 --> 00:23:19.200 thought. But, you know, looking at how far this 00:23:19.200 --> 00:23:21.420 architecture has come, this raises an important 00:23:21.420 --> 00:23:24.579 question. One that wasn't explicitly covered 00:23:24.579 --> 00:23:27.099 in our source text, but it feels like the inevitable 00:23:27.099 --> 00:23:30.200 next step in this evolution. Lay it on me. Where 00:23:30.200 --> 00:23:32.460 is the trash metaphor heading? Well, think about 00:23:32.460 --> 00:23:34.660 it. The entire reason we created the trash can 00:23:34.660 --> 00:23:37.160 metaphor was because local storage space was 00:23:37.160 --> 00:23:39.759 incredibly limited and expensive. Right. We had 00:23:39.759 --> 00:23:41.779 to delete things to make room, so we needed a 00:23:41.779 --> 00:23:44.220 safe psychological mechanism to facilitate that 00:23:44.220 --> 00:23:48.109 deletion. But as we move into an era of massive 00:23:48.109 --> 00:23:50.789 cloud computing and nearly infinite digital memory, 00:23:51.210 --> 00:23:54.009 the concept of a user running out of space is 00:23:54.009 --> 00:23:57.130 rapidly fading. That's a profound point. I rarely 00:23:57.130 --> 00:23:59.869 check my local hard drive capacity anymore. Everything 00:23:59.869 --> 00:24:02.609 just synchronizes to the cloud seamlessly. Exactly. 00:24:02.890 --> 00:24:05.170 So if storage is effectively infinite and we 00:24:05.170 --> 00:24:07.569 never truly have to empty the trash to save space 00:24:07.569 --> 00:24:09.980 anymore... Are we approaching a future where 00:24:09.980 --> 00:24:12.799 the trashcan metaphor disappears entirely? Will 00:24:12.799 --> 00:24:15.680 it just be replaced by an eternal, perfectly 00:24:15.680 --> 00:24:18.720 searchable archive of every mistake, every blurry 00:24:18.720 --> 00:24:20.799 photo, and every discarded thought we've ever 00:24:20.799 --> 00:24:23.660 had? If the technical limitation is gone, do 00:24:23.660 --> 00:24:25.519 we ever really need to delete anything again? 00:24:26.000 --> 00:24:29.579 An eternal archive of our mistakes that is both 00:24:29.579 --> 00:24:32.019 incredibly convenient and slightly terrifying 00:24:32.019 --> 00:24:34.450 to contemplate. We might need a whole new psychological 00:24:34.450 --> 00:24:36.769 safety net just to process the idea that nothing 00:24:36.769 --> 00:24:39.130 is ever truly gone. We just might. Well, thank 00:24:39.130 --> 00:24:41.089 you all for joining us on this exploration of 00:24:41.089 --> 00:24:43.130 the digital graveyard. We hope you walk away 00:24:43.130 --> 00:24:45.190 with a new appreciation for the hidden architecture 00:24:45.190 --> 00:24:47.390 on your screen, and we encourage you to think 00:24:47.390 --> 00:24:50.049 twice the next time you hear that highly satisfying, 00:24:50.250 --> 00:24:52.410 crumple sound effect. Until next time.