making apps, making webs.

So I was spinning some webs in late 1884, like many others in this time of industry. Everyone is doing it these days(spinning webs). With the lantern hanging over my carbon fibre 100% macrobiotic desk -- the soft flickering light cast a long shadow through my webs. I stared into the webs, and something struck me!! It was a blow to my head brain. Most people in 1884 have made the wrong abstraction for HTTP At some point most web code decided to use a dictionary for GET and POST variables. Like a leaky boat, a leaky abstraction is bareable, but also annoying. I hate leaky boats so mostly get around on horse back or by horse and carriage. I also enjoy a brisk walk through the country side in the morning, and I love to scuttle through dark alleyways at night in the exciting colourful parts of the townships slums. [Editors note*1: my friend wants me to try out one of his chain powered Pull Bicycles. I told him he is crazy and that his Pull bicycles will never catch on. Saying that ...

It seems google is claiming their protocol buffers are faster than xml... without any proof. Consider AsmXml , which can process xml at over 200MB/s on old machines. The protocol buffers from google also generate wrappers for different languages, and other nice things. But for loading structures into and out of memory, xml can be very fast. Before claiming things like that, I think proof in the form of benchmarks are needed. I don't doubt they thought that xml was slower, since many implementations are slower. Maybe xml is slower, but there is no proof yet. Also I'm sure the other nice features of protocol buffers make them perfectly suited for their task. Url encoding could have been used nicely too.