Skip to main content

In Into the Wild, why did Chris McCandless keep to himself?

Without being able to directly ask Chris McCandless, the answer to this question will probably forever remain a mystery.  Krakauer does a nice job of trying to "get inside" McCandless and figure out what makes him tick, but it's still Krakauer's best guess.  Krakauer also does a nice job of illustrating how McCandless wasn't the only ascetic to be drawn to the road and Alaska.  Krakauer spends chapters eight and nine comparing McCandless to Gene Rosselini, John Waterman, Carl McCunn, and Everett Reuss.  All of those men felt the pull of a solitary life.  They all died in that life too.  That doesn't mean that they were unsuccessful though.  Similarly, I don't think that McCandless failed in his quest either.  


But why exactly McCandless wanted to live the life that he chose to live might best be explained by using a Henry David Thoreau quote.  



"I wanted to live deep and suck out all the marrow of life, to live so sturdily and Spartan-like as to put to rout all that was not life, to cut a broad swath and shave close, to drive life into a corner, and reduce it to its lowest terms."



I think that is exactly why McCandless kept to himself.  He wanted to live his life to the fullest.  For McCandless that meant paring his life down to the bare essentials.  It also meant that he needed to be free to make his own decisions about his own life direction all of the time.  In order to do that, McCandless had to live a solitary life.  Being around people always resulted in those people trying to force their will and opinion on McCandless.  Even Ronald Franz tried to do that to McCandless at one point. 



After attending church that Sunday, Franz decided to talk to Alex “about how he was living. Somebody needed to convince him to get an education and a job and make something of his life.”



By living alone, McCandless is free to do what he wants to do. 

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...