Half hull model ship

A half hull model ship (also known as a "half hull" or "half ship") is a wooden model ship featuring only one half of a boat's hull without rigging or other fixtures.

Several half hull model ships hanging on wall

Background

Prior to the twentieth century, half hull model ships were constructed by shipwrights as a means of planning a ship's design and sheer and ensuring that the ship would be symmetrical. The half hulls were mounted on a board and were exact scale replicas of the actual ship's hull. With the advent of computer design, half hulls are now built as decorative nautical art and constructed after a ship is completed.[1][2]

Early half hull models (built 1809–1870 of Salem, Massachusetts ships) at the Peabody Essex Museum
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
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.

See also
  • Wooden model ship
  • Marine Art

References
  1. "Encyclopedia of American Folk Art," By Gerard C. Wertkin, Lee Kogan, American Folk Art Museum Contributor Gerard C. Wertkin, Lee Kogan Edition: illustrated Published by Taylor & Francis, 2004 ISBN 0-415-92986-5, 978-0-415-92986-8 (accessed Google Book search January 14, 2009)
  2. "Half-Hull Modeling," (The Apprenticeshop, Bath, ME USA:1980)


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