SYSTEM NOTICE

Auto translation by AI. Be sure, accuracy, nuances and authorial intent may not be fully reflected.
見出し画像

🥢 Why is there cabbage next to tonkatsu? — It wasn't a coincidence, but an 'evolved survivor' —

The mountain of shredded cabbage served at tonkatsu restaurants.

It's delicious. But it makes you wonder.

'Why cabbage?'

It could have been lettuce, cucumber, or potatoes, so why cabbage?

This sense of unease is actually very important, as it reveals the true nature of the dish known as tonkatsu.


🥩 Tonkatsu wasn't paired with cabbage from the start

The origins of tonkatsu lie in the Western-style food culture of the Meiji and Taisho eras.

At the time, it appeared as 'pork cutlet' in the context of Western cuisine, and the side dishes were different from what they are today.

Potatoes, green peas, and parsley.

In other words, early tonkatsu was still a 'European-style dish'.

The current 'tonkatsu + mountain of cabbage' combination was not a finished design from the beginning.


🥬 Cabbage wasn't 'invented,' it 'remained'

After the war, the dining-out environment in Japan changed.

This is when cabbage suddenly became a star player.

The reasons are very practical.

  • It's cheap

  • It can be supplied stably all year round

  • It can be served just by cutting it

  • It can be eaten raw

  • It absorbs the oil from fried foods

  • It adds volume

The important point is not that 'someone chose cabbage,' but rather,

👉 that other options were dropped by the environment

is the point.


🧠 What was happening here was 'cultural natural selection'

Tonkatsu side dishes were actually in a state of quiet competition.

  • Potatoes: Too heavy

  • Tomatoes: Moisture causes the structure to collapse

  • Lettuce: Weak in cost and stability

  • Cucumber: Does not pair well with oil or sauce

Among them, only cabbage remained.

In other words, this is

👉 Not 'the most delicious thing won'
👉 But 'the most resilient structure won'

a phenomenon.


🥢 A tonkatsu set meal is an 'ecosystem with divided roles'

If you break down a current tonkatsu set meal, it looks like this.

  • Tonkatsu: Energy (the star)

  • Cabbage: Reset device (neutralizing oil and flavor)

  • Sauce: Flavor integration (providing meaning)

  • Mustard: Stimulation/Restart

  • Rice and Miso Soup: The Stable Foundation

This is not just a dish, but a 'structure' with divided roles.


🧬 What happens when viewed through the lens of evolutionary theory?

Looking at this structure in a Darwinian way is very simple.

  • Mutation: Various side dishes are tested

  • Selection: The ones that survive in the market remain

  • Inheritance: Other restaurants imitate them

The result of that is what remains,

👉 the 'survivor pair' of tonkatsu + cabbage

is what we have.

What is important here is

👉 that it wasn't 'the best that was chosen' but
👉 'the form that could survive that remained'

is the point.


🌍 Here is the essence: What will happen in the future?

If that is the story of the past, this is the main topic.

If this is the result of 'evolution,' these questions arise for the future.

  • Will a side dish that surpasses cabbage be born?

  • Will tonkatsu not evolve any further?

  • Can deliciousness be designed?

And if we take it one step further, it becomes this.

👉 Could humans handle evolution itself?


🧪 Delusional idea: Cooking Evolution Wiki

I'm going to take a leap in logic here.

If we could treat cooking as an 'evolutionary system,' we should be able to create something like this.


📱 Cooking Evolution Wiki (tentative)

A platform that treats culinary elements from around the world like genes.

  • Frying / Boiling / Grilling

  • Fat / Acid / Sweetness / Saltiness

  • Crunchy / Thick / Crispy

  • Temperature / Aroma / Pungency

  • Meat / Fish / Vegetables / Grains

Register these as 'combinable elements.'


🧪 What you can do

  • Post new culinary structures

    • Example: Tonkatsu + Purple Cabbage + Yuzu

    • Example: Karaage + Yogurt Sauce

    • Example: Curry + Shredded Daikon

  • Actually make and eat them

  • Evaluate them (not by taste, but by 'survivability')

  • Only those that are reproduced repeatedly will remain


🧬 There is only one rule

👉 Do not decide on a correct answer

  • Whether it is delicious or not is not the initial criterion

  • "Will it be made again?" is the evaluation axis

  • What remains becomes the next-generation recipe


🌱 What is this doing?

This is not just recipe sharing.

👉 Recreating artificial natural selection in cooking

  • Recipe = Gene

  • Combination = Crossbreeding

  • New recipe = Mutation

  • Tasting and evaluation = Environmental selection

And what is important is,

👉 That no one controls the correct answer


🔚 Summary

The relationship between tonkatsu and cabbage was not a coincidence,

👉 It was an "evolutionary result" that remained after countless trials and errors.

And beyond that,

👉 A mechanism to observe, test, and accelerate evolution itself
👉 "A platform that handles the natural selection of cooking"

is possible.


The next time you eat tonkatsu, it will no longer be just a set meal,

👉 It should be seen as "a dish in the middle of evolution"

as you look at it.


▼ You can check out other articles on this theme in this magazine

If this article resonates with you, I would be happy if you could click the 'Like' button.
If you feel like sharing it with someone, it would be a great encouragement to me.


いいなと思ったら応援しよう!