Hatago

Hatago (旅籠) were Edo period lodgings for travelers at shukuba (post stations) along the national highways, including the Edo Five Routes and the subroutes. In addition to a place to rest, hatago also offered meals and other foods to the travelers. They were also called hatagoya (旅籠屋).

A hatago in Japan which today functions as a museum

Name origin

Hatago means "traveling basket." The word itself originally derived from baskets that contained food for horses and were carried by travelers. From there, it became a tool with which travelers were carry their own food and goods. Shops that began preparing and selling food for travelers gained the suffix ya (屋), meaning "shop," but this was eventually shortened to just hatago.

Preserved hatago
Akasaka-juku's Ōhashi-ya

Because many post stations along the Tōkaidō, Nakasendō and other historical routes have been either preserved or rebuilt, there are many traditional hatago still in existence today. While some have only been preserved as public buildings and museums, others have continued to operate for the past few hundred years.

Lodgings

Museums
gollark: PETA will destroy you.
gollark: At least it has generics.
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.

See also

References
  1. Ōhashi-ya. Aichi Prefectural Education Center. Accessed November 6, 2007.
  2. Nagano-ken no Kaidō to Shukuba Archived 2007-10-25 at the Wayback Machine. Yasunao Hayashi. Accessed November 6, 2007.
  3. Nagano no Onsen-shuku. Accessed November 6, 2007.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.