Skip to main content

Why are barns red?

I have always wondered why most barns are painted red. It is always an aesthetic sight to see one while driving in the countryside, both during the lush green days of summer, or the yellow arid days of winter. There is of course a chance that farmers chose the color red for its aesthetics value, but I wondered if there was a more practical reason for the choice.


An online search produced a bevy of results with equally reasonable choices. One of the sites argues that in the older days, one of the practical methods to seal the barn wood and protect it from the elements was to paint it with a mixture of linseed oil, and  additions of milk and line. The red color would come from adding either the blood of a recent slaughter or from ferrous oxide--rust. As the paint would dry it would turn into a dark red color. I buy the rust theory, since there is a lot of rust to be had everywhere, and the blood theory is a bit weird.
The Smithsonian magazine adds a physics spin to the answer, by explaining why rust or ferrous oxide is an abundant material in the universe, and that this abundance is the most likely reason farmers used it in the barn paint mixture. The article explains why iron is abundant through the evolution of stars, as they go from collapse to explosion, and the reactions that combine protons and neutrons into heavier materials as the cycles progress, and finally stopping when the atomic mass becomes 56 (iron). I like the explanation, although it begs the question why the reactions stop at 56. But that's a question for another search.




Comments

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...