I wonder, is there some way to create a key-value store out of any physical or virtual object that can store state? I know there is a lot of work done with quantum computing to store state in quarks. I can see that has value.
But, what is the most inefficient data storage mechanism you can come up with? Here are a few I can think of:
Instagram-as-a-database - You issue a request to save your data, we encode it using some visual encoding scheme, take a picture, and then upload it somewhere. You get returned a URL, and can then decode it or update it.
MTurk-as-a-database - The possibilities are endless here. Someone could write down your request on a piece of paper and then you could send another request where they type it back.
Twilio-as-a-database - Encode your data as an audio stream. Store it in random voicemail boxes. Retrieve it later by calling up, listening to your voicemail, decoding the messages.
Start using the DB. If you get bored enough you can examine the data physically in-game.
Atoms or electrons, but not quarks.
I say this as someone who worships Crockford for inventing JSON.
I've seen too many projects get fucked hard because they used flatfiles.
Edit: Seriously though, managing synchronization/atomic changes to flatfiles manually is a Bad Idea (TM).
It's somewhere up there with, "I have a performance problem. I'll use pthreads!" Now you have 1,02-SEGMENTATION FAULT problems.
And also shows its really a one-day app!
Shameless plug: sign up for our beta! http://nimbusbase.com