|
|
|
|
|
by giantfrog
346 days ago
|
|
This is a really fun exercise; a rare example of something that's "data-centric" without being soulless. I think it's fascinating how it illustrates weirdness about how Americans think about and categorize "ethnic" food. For example, the author's analysis of Google data shows Glendale, CA ranks #1 for "Highest prevalence of Mediterranean Restaurants." But I am nearly certain the majority of these, given Glendale's demographics, are in fact Armenian or Persian restaurants. Both Iran and Armenia are of course quite far from the Mediterranean region, but for whatever reason (rice? flat breads? grilled things on a stick?) have gotten lumped in with some Americanized, genericized conception of "the Mediterranean" that's indistinguishable from "the Middle East." I would imagine you'd find the same thing happening on Yelp etc. |
|
The same happens with the food itself. I had a chat with a restaurateur in Switzerland, and he explained all the modifications he had to make in order to sell "Chinese" food. "They didn't have bean sprouts when I first came, and they will look like they are dying if there's any amount of spice in it."
The famous example of this is Chicken Tikka Masala, which is a British take on Indian food. You can't open an "Indian" restaurant in the UK and not put it on the menu, just as you must have the step-ladder of spice with Indian sounding names (Korma, Madras, Vindaloo). IIRC similar to General Tso's Chicken when it comes to ordering Chinese in the US, gotta be on the menu.
People simply come to expect certain things with certain foods, often disconnected with the the place that inspired it. When you open an ethnic restaurant, it's almost like joining a franchise. You aren't formally paying MacDonald's when you open a Chinese takeaway, but you do have to have things on the menu that people recognize, so the labels "Thai", "Ramen", "Japanese", etc function a bit like a franchise.