HEADON! Apply directly to the forehead!

And if you order before midnight tonight, we will include a free sample of HEAD ON: Apply directly to the forehead! [VIDEO]

I only learned about "head on" in the last month or so. In case anyone missed the reference, it's an annoying TV commercial: [VIDEO]

I've meant to contribute to this discussion and answer questions, but this article is more than a year old, and I've been it regularly and made lots of progress since then, I feel I should writing a fresh new article about it, including some actual documentation and examples. I'll post it to HN as soon as I'm done, and put a link to it here. And I would appreciate hearing from anyone who's interested in or working on similar ideas, so we can collaborate to combine our forces! (Email in profile.) It also needs a good name! (As a rule of thumb, I try not to get bogged down in naming things when I should be spending my time actually working on them and using them, to figure out what they actually are before naming them. But it's been more than a year and now I want to talk about it more mellifluously.) I was calling it "JSONster", but that sounded too monstrous, don't describe it, and nobody gets the Napster reference these days. So I tried to think of better name by repeatedly pounded my fist against my forehead, which gave me a headache, when suddenly a homeopathic solution to my naming problem sprang to mind: "SpreadON", short for "Spreadsheet Object Notation". Elevator Pitch: SpreadON applies JSON to spreadsheets like butter to waffles, so it melts into the nooks and crannies. Marketing Ploy: SpreadON: Apply directly to the spreadsheet. SpreadON: Apply directly to the spreadsheet. SpreadON: Apply directly to the spreadsheet. [VIDEO] [LINK] >HeadOn is the brand name of a topi

You still have to pay for a 64 bit pointer to an un-interned string though. It's the fact that the keys are repeated for each record that overwhelms the size of the keys or pointers themselves, when you have millions of records. If you are using fixed structures, then the keys are implicit and don't need to be repeated or even represented as pointers, just known fixed offsets into the structures. I wrote this about "Representing and Editing JSON with Spreadsheets": [LINK] [LINK] SpreadOn: Apply Directly to the Forehead. [VIDEO]

I'd love to have a database of once-annoying but now-nostalgic TV commercials to intersperse between the shows, and insert into commercial breaks. (Those dramatic pauses in Star Trek TOS just aren't the same without a Crazy Eddie interruption.) HEAD ON: Apply Directly to the Forehead: [VIDEO] W.E.T. P.E.T.S.: [LINK] Fine Corinthian Leather: [LINK] Bic Banana Ink Crayon: [LINK] Flea Market Montgomery: [LINK] Crazy Eddie: [LINK]