A computer from 2006 is old now. That sounds obvious until you stop and do the math. A machine from that period may have shipped with Windows XP, maybe Windows Vista if it was unlucky, or some version of Mac OS X that is now a museum piece by modern support standards. On the Linux side, it may have been running a distribution from an era when wireless drivers still made people mutter at their desks.
Yet a surprising number of those machines still turn on. The screen may be dim. The battery may be useless. The hard drive may sound like it is auditioning for mechanical failure. But the keyboard works, the ports are still there, and the processor can still add numbers just as honestly as it did when the machine was new.
The better question is not whether a twenty-year-old computer is useful in the abstract. The better question is useful for what.
If the job is the modern commercial web, the answer gets rough quickly. Current browsers are heavy. Many sites assume current TLS support, recent JavaScript engines, hardware acceleration, video codecs, plenty of memory, and a processor that can keep up with pages written like desktop applications. A 2006 machine can sometimes be coaxed into loading those pages, especially with enough RAM and a lightweight Linux installation, but it is not going to feel young.
Security is the other hard limit. Running an unsupported operating system on the open Internet is asking for trouble. That does not mean the machine must be thrown away. It means the role needs to be chosen carefully. A twenty-year-old computer used for online banking, password management, main email, or account administration is a bad idea. A twenty-year-old computer used for writing, local tools, retro software, terminal access, or a contained lab is a different matter.
There is still plenty of useful work that does not require the heaviest parts of today’s web. A machine from that period can be a writing station. It can run a text editor, keep notes, read plain documents, manage a local archive, play older media files, run period games, connect to BBSes, SSH into newer systems, or serve as a terminal for machines doing the harder work elsewhere. In some cases it can run a lightweight desktop well enough for email, feeds, and simple browsing, as long as expectations stay grounded.
Linux can help, but Linux is not a time machine. A lightweight distribution may give old hardware a cleaner second life. Replacing a spinning hard drive with an SSD can make a dramatic difference, if the machine supports it. Adding RAM helps, up to the limits of the hardware. Cleaning dust from the cooling system can matter more than people expect. Still, there comes a point where the browser, the kernel, the graphics stack, or basic electrical age sets the boundary.
The good news is that usefulness does not have to mean daily-driver status. We have a bad habit of measuring every computer by whether it can be the one machine for everything. That is a narrow standard. A twenty-year-old laptop may be a poor main computer and an excellent distraction-free writing box. An old desktop may be silly for video editing and perfectly fine as a serial console, ham radio station, test machine, file sorting station, or retro gaming rig.
Old hardware is also useful because it teaches limits. Modern computers hide a lot behind speed. Wasteful software can survive because the machine underneath is fast enough to absorb the damage. On older hardware, waste becomes visible. A bloated web page stutters. A careless background service matters. A simple native program feels good because it respects the machine. That kind of feedback is educational.
There is a repair lesson too. Twenty-year-old computers often come from the last period when many machines were still reasonably serviceable. That was never universal, but it was common enough to matter. Screws were common. Drives and memory were reachable. Batteries were more likely to be replaceable. Ports were generous. Documentation existed. Compared with sealed modern devices, some older computers feel less polished and more honest. You can open them without feeling like you are violating a product manager’s wishes.
That does not mean keeping every old machine alive makes sense. Some are power-hungry. Some are unreliable. Some use aging capacitors, dying displays, brittle plastics, or storage that should not be trusted. Sometimes the right answer is to salvage parts, wipe the drive, recycle the machine properly, and move on. Sentiment is not a maintenance plan.
But useful old computers deserve a fair assessment. Start with the hardware. Does it boot reliably? Can it take more RAM? Is the storage healthy? Does it overheat? Are replacement parts available? Then look at the job. Does that job require current security patches? Does it require modern web services? Does it require high performance, or only patience and a keyboard? The answer usually becomes clear once the job is specific.
For me, the most interesting uses are the ones that respect the age of the machine. Use it as a writing system. Put a small Linux or BSD setup on it if the hardware allows. Keep it off important accounts. Let it talk to newer machines over SSH. Use it for old software that belongs on it. Use it to learn how much computing can still happen without a stack of subscriptions and background services.
A twenty-year-old computer can still be useful. It probably should not be asked to ignore the last twenty years of software inflation. Give it a job that fits, keep the risks contained, and it may still earn its place on the desk.