If you grew up with one of these machines, you know the feeling I'm chasing. You flipped a switch and you were in — a blinking cursor, no boot screen, no updates, no twelve background processes deciding whether to let you work. The whole computer fit in your head. You could, in an afternoon, understand the thing from the keyboard to the chips. That clarity is what I miss, and it's worth being honest about whether you can rebuild it or just remember it.
Apple IIe vs. Commodore 64 — a first love
For me it's a genuine coin-flip between these two, and they represent two different philosophies worth thinking about even now.
The Apple IIe was the open, expandable, do-it-right machine — slots for days, a build quality and an ecosystem that made it the computer schools and tinkerers trusted. It invited you to add to it.
The Commodore 64 was the people's machine: cheaper, wildly capable for the money, with a sound chip (the legendary SID) and graphics that punched so far above its price that an entire demoscene grew up around squeezing miracles out of it. It invited you to push it past its limits.
Open and principled versus cheap and clever. Honestly, that tension still describes most of the interesting choices in hardware today.
What "modern guts" actually means
Here's where the engineer in me takes over from the nostalgic. You can build the dream today, and there are basically three honest approaches — each a different answer to "how much is real?"
1. Emulation in a period shell
The pragmatic build: a small modern board — a Raspberry Pi or a mini PC — running a faithful emulator, tucked inside a real or reproduction case. Combine it with a project like the Commodore 64 reproduction shells people build, or a mechanical keyboard with the right feel, and you get the look, the instant boot, and software compatibility, with modern speed and storage underneath. It's the least "pure" and by far the most usable.
2. New hardware, old architecture
The enthusiast middle ground. The retro-computing community has produced genuinely new machines — modern recreations and FPGA-based systems like the MiSTer project — that implement the original chips in reconfigurable logic rather than emulating them in software. You get cycle-accurate behavior, real cartridge and peripheral support, and hardware that will outlive the originals. This is where art and engineering meet, which is exactly the corner I like.
3. Restore the real thing
The purist path: hunt down an actual IIe or C64 and bring it back — recap the board, replace the failing power supply (the C64's original "brick" is infamous for taking chips with it when it dies), add a modern storage adapter so you're not feeding it floppies. You end up with the genuine article, quirks and all. It's the most soul and the most maintenance.
The honest part: what you can't bring back
I'd be lying if I pretended the modern build is strictly better. Some of what made those machines special doesn't survive the upgrade. The constraints were the magic. When you had 64K of memory and a fixed palette, every clever trick mattered, and the limits forced a kind of creativity that infinite resources quietly kill. A modern board running an emulator gives you the aesthetic but removes the very scarcity that made the demoscene, and the deep understanding, possible.
So the real design question isn't "how do I make it fast." It's "which constraints do I keep on purpose?" Maybe you keep the instant boot and the tactile keyboard but ditch the floppy. Maybe you keep a hard memory ceiling for a project just to feel that pressure again. The build is really a series of deliberate choices about what you're nostalgic for.
And yes — the cathode-ray fantasy
If I'm being indulgent about it: the dream version has a warm amber or green monochrome glow, mechanical keys with real travel, and a chunky toggle switch instead of a soft-touch button. Throw in a shortwave radio and some exposed vacuum tubes for switches and you've left "computer" behind and arrived at art object — which is fine, because that's half the point. It blends engineering and craft, the two things I can never quite keep separate, and probably shouldn't.
I haven't built the final version yet. But the parts list lives in my head, and every time I flip on something modern and wait through a boot sequence, that blinking cursor gets a little louder.