You’ve probably noticed that the places we remember rarely match the places we actually visit. You go to San Francisco, and it doesn’t look like the steep, sun-drenched hills you built in your head. It’s just traffic, fog, and tourists.
Enter a new web project that renders the entire city of San Francisco as a minimalist video game. It’s blocky. It’s abstract. And if you’re using Firefox on Windows 11, it might not even load, leaving you staring at a block bouncing in a circle while you frantically toggle your adblocker.
Most people look at this and see a tech demo. A cute little experiment. I look at this and see the most honest representation of digital memory ever created.
We don’t remember cities in 4K. We remember them in low-poly polygons and broken textures.
The tension here is beautiful. On one end, you have Microsoft Flight Simulator, using satellite data and cloud computing to render every single building, tree, and pothole with terrifying accuracy. On the other end, you have this: a stripped-down, geometric abstraction where San Francisco is reduced to its essential shapes.
Flight Simulator gives you the world. This minimalist game gives you the feeling of the world.
Look at the reactions. One commenter noted their first experience with SF was through the City Escape stage in Sonic Adventure 2. They didn’t even know it was San Francisco until they visited years later. Another fondly remembered the proxy version in GTA San Andreas. Someone else just cried in the corner about Cisco Heat.
These aren’t just game preferences. These are admissions that our internal maps are built on abstractions.
A perfectly rendered city is just a map. A broken, abstracted city is a memory.
The real genius of this project isn’t the geometry; it’s the failure. The fact that the game sometimes just refuses to load is the ultimate meta-commentary on how we consume cities through screens. You think you know a place because you’ve seen it on Google Earth or played it in Watch Dogs 2. You expect a seamless transition from digital representation to lived experience.
Instead, you get a bouncing block. A loading failure. The realization that the screen cannot capture the street.
We’ve been sold a lie that higher fidelity equals more reality. But adding more pixels to a screen doesn’t make it feel more alive; it just makes it more accurate. And accuracy is boring. Memory is messy, incomplete, and often stuck on a loading screen.
Realism isn’t about what you can render. It’s about what you can feel.
The next time you visit a city and feel that weird cognitive dissonance—the gap between the place you imagined and the place you’re standing in—don’t blame your memory. Blame the fact that you’ve been trying to run a high-fidelity simulation on a brain that thrives on abstraction.
This broken little SF game isn’t just a toy. It’s a mirror. It forces you to ask: which version of the city is actually more real? The one built from satellite data, or the one built from your nostalgia?
FAQ
Q: Isn't this just a broken web demo, not a profound statement on urban memory?
A: Maybe. But the frustration of watching a block bounce in a circle while waiting for it to load perfectly mirrors the disconnect between expecting a digital city and actually experiencing one. The 'bug' is the feature.
Q: Why does this matter if I'm not a game dev?
A: Because it applies to how you consume all media. You think your Google Street View tour of Paris prepared you for the real city. It didn't. You're walking around with a low-poly map and pretending it's high-fidelity.
Q: So you're saying high-end graphics are pointless?
A: No, they're great for escapism. But they're terrible for memory. If you want to capture how it feels to remember a place you've been, you don't need 4K textures. You need abstraction.