Navajo white

Navajo White
Color coordinates
Hex triplet	#FFDEAD
sRGBB (r, g, b)	(255, 222, 173)
CMYKH (c, m, y, k)	(0, 13, 32, 0)
HSV (h, s, v)	(36°, 32%, 100%)
Source	X11[1]
ISCC–NBS descriptor	Pale yellow
	B: Normalized to [0–255] (byte); H: Normalized to [0–100] (hundred)

Navajo White is an orangish white color, or pastel yellow orange, and derives its name from its similarity to the background color of the Navajo Nation flag. The name "Navajo White" is usually only used when referring to paint. As the name indicates, the color is often considered a shade of white, even though it is more properly categorized as a yellow.

The flag that the color is named after

From the 1970s to the 1990s it was, along with the color bone, one of the standard interior paint colors used in many tract homes in the United States and especially apartment complexes as, like the color bone, it does not easily show stains from cigarette smoke or fingerprints. In recent years it has lost favor to other shades of off-white, grey, and pastel colors.

Trivia

In 1989, the color "Navajo white" was included in the X11 color list.[2] As such, it became and continues to be (2019) part of the web colors.

gollark: I prefer Rust.

gollark: ```perl -wlne'END{print$n}eof&&$n++;/<title>([^<]+)/i&&$n--' *Contents 1 Interpretation 2 Implementations 2.1 In Perl 2.2 In shell scriptsInterpretationThe code in question (from the collection "The road to Perligata") is a lament over the coming apocalypse, an expression of the author's Weltschmerz and the futility of all human endeavors. Let us take it step by step:-wlne' The world is near its end.END{print$n} At the end the sum of all our sins and virtues will be reckoned and the judgement revealed.eof&&$n++; As the evil of mankind ends, perhaps the end itself is a positive thing./<title>([^<]+)/ We are preoccupied with fame and titlesi And insensitive to the suffering of others.&&$n-- All this is for nought, and only hastens our demise.' * For in the end, we are but stardust. ```

gollark: They'll probably say "lambdas are evil" because python hates functional programming a lot of the time.

gollark: *considers creating an esowiki page for haskell and golang*

gollark: ``` func AddInt32(addr *int32, delta int32) (new int32) func AddInt64(addr *int64, delta int64) (new int64) func AddUint32(addr *uint32, delta uint32) (new uint32) func AddUint64(addr *uint64, delta uint64) (new uint64) func AddUintptr(addr *uintptr, delta uintptr) (new uintptr) func CompareAndSwapInt32(addr *int32, old, new int32) (swapped bool) func CompareAndSwapInt64(addr *int64, old, new int64) (swapped bool) func CompareAndSwapPointer(addr *unsafe.Pointer, old, new unsafe.Pointer) (swapped bool) func CompareAndSwapUint32(addr *uint32, old, new uint32) (swapped bool) func CompareAndSwapUint64(addr *uint64, old, new uint64) (swapped bool) func CompareAndSwapUintptr(addr *uintptr, old, new uintptr) (swapped bool) func LoadInt32(addr *int32) (val int32) func LoadInt64(addr *int64) (val int64) func LoadPointer(addr *unsafe.Pointer) (val unsafe.Pointer) func LoadUint32(addr *uint32) (val uint32) func LoadUint64(addr *uint64) (val uint64) func LoadUintptr(addr *uintptr) (val uintptr) func StoreInt32(addr *int32, val int32) func StoreInt64(addr *int64, val int64) func StorePointer(addr *unsafe.Pointer, val unsafe.Pointer) func StoreUint32(addr *uint32, val uint32) func StoreUint64(addr *uint64, val uint64) func StoreUintptr(addr *uintptr, val uintptr) func SwapInt32(addr *int32, new int32) (old int32) func SwapInt64(addr *int64, new int64) (old int64) func SwapPointer(addr *unsafe.Pointer, new unsafe.Pointer) (old unsafe.Pointer) func SwapUint32(addr *uint32, new uint32) (old uint32) func SwapUint64(addr *uint64, new uint64) (old uint64) func SwapUintptr(addr *uintptr, new uintptr) (old uintptr)```Seen in standard library docs.

References

CSS Color Module Level 3:
JSConf (2014-07-16), Alex Sexton: Peachpuffs and Lemonchiffons [CSSConfUS2014], retrieved 2016-11-16

Navajo white

Trivia

References

See also