't Koetshuis

't Koetshuis is a defunct restaurant located in Rhenen, Netherlands. It was a fine dining restaurant that was awarded one or two Michelin stars in the period 1957–1970.

't Koetshuis
Restaurant information
Established1945
Closed1988
Rating Michelin Guide
Street addressVeenendaalsestraatweg 50
CityRhenen
Postal/ZIP Code3921 EC
CountryNetherlands
Coordinates51°59′55″N 5°31′49″E
Seating capacityn/a

The restaurant was established in 1945 in the stable of the former hotel "Berg en Bos". The hotel had fallen victim to the Second World War. The Frisch family, of Swiss origin, just started all again and started a rotisserie. This restaurant went very well, until it burned down in 1964. Henri Frisch wanted to start over again, but he died a month after the fire. His children went on with the rebuilding and the restaurant reopened in 1965.[1][2]

Owners of the restaurant were Henri Frisch (1957–1964) and his daughter Marianne Frisch (1964–1970). Marianne Frisch sold the restaurant in 1988.[3] Henri Frisch was also head chef. In 1967, J. van Heusden was head chef.[4]

't Koetshuis was in 1967 one of the founding members of Alliance Gastronomique Néerlandaise, an association of quality restaurants in the Netherlands and Belgium.[5]

Star history

- 1957–1964: two stars[6]
- 1965–1966: one star[7]
- 1967–1970: two stars[7]

gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.
gollark: Oh, and the strings are terrible.

See also

References


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.