Guest Blog 2: The Decumani

Thank goodness for Harry, since I had no material this week.  His latest production is a… Decumani:

My wife and I were visiting Naples this fall. We had just finished a tour of the city’s Duomo, and were poking around the Via dei Tribunali, near the Via San Gregorio Armeno, in the Decumano Maggiore section of the city. The San Gregorio Armeno is famous for the craftsmen that still carve shepherds and other figures for the traditional Neapolitan nativity scenes, a tradition that dates back some 400 years. It was lunch time and by happenstance we found ourselves in the  Antica Pizzeria "i Decumani". While there were introduced by our table neighbors to the restaurant’s signature dish “i Decumani.” Looking more like a pizza “ring” rather than a pizza “pie” we were intrigued and ordered one.

It was delicious, and unlike any pizza we had ever tasted. The ring was “stuffed” with eggplant, olives, and mozzarella cheese. And then it was covered with slices of prosciutto, and arugula leaves.

Being somewhat of a pizza chef myself (we have a wood burning pizza oven at our house) i Decumani 2I started to deconstruct the dish with the objective of recreating the treat once we arrived back in the States. It appeared that once the pizza dough was formed into a “pie”, the center portion was cut to make flaps that were then folded back over the fillings and the outer crust, thereby forming a ring.

i Decumani 1

I tried this technique after we arrived back home with pretty good results, as you can see from the pictures.

Mobile Client Wars and Client Diversity

As Android’s market share creeps up on iPhone, the drums of blogerati buzz beat louder on topics such as “which platform will win”, “battle of the titans over mobile”, etc.

A lot of this is just the chattering e-classes chattering (and, btw, Android’s going to win), but there is a trend below the radar here that has longer legs: I call it “client diversity”.

The fact is we are driving toward a computing architecture where different kinds of clients all attach to the network and use network resources (increasingly) for storage, computation, and collaboration.

Smartphones are one kind of client; “new” tablets like iPad (and the raft of Android tablets to be announced at CES shortly) are another.  But the various smartphones have more in common, say, than iPhone and iPad.  We are moving toward an ecosystem where different clients will be used for different functions and will co-exist more-or-less stably.

Most of my friends and colleagues are experimenting with substituting an iPad for a laptop in their road trips (the consensus seems to be that iPad does better for short trips, laptops for multi-city ones).  Most everyone with a smartphone and an iPad is finding that some apps, games, and activities work better on one than another.

Guess what?  Things are probably going to get more diverse.  We have second-class network clients like wireless picture frames, and even the poor Sony Dash.  We have automobile-based clients like media players and on-board nav systems.  (We have in fact nascent clients in all the GPS units out there, longing to be web-connected as well as GIS-connected.)

Why so many?  Because they are cheap enough (eventually) so that it’s more important to have the best client for each purpose than to have one client for all purposes.

Guess what else?  The mobile clients will start to control the non-mobile ones, so that your content from your smartphone will show up on the on-board nav system where the display is larger, although it may still be controlled from the smartphone (whose keyboard is better for input).  Your email will segue to the giant TV in your hotel room when you arrive because it’s easier to see.  This won’t take tech miracles, but it will take a hell of a lot of negotiations, similar to what the wireless voice world went through when it discovered how to do universal roaming.