Why Learn R? It's the language of Statistics

In the Introduction to his book “R for SAS and SPSS Users” (Springer 2009) Robert Muenchen offers ten reasons for learning R if you already know SAS or SPSS. All ten reasons say something important about R. However, his fourth reason: “R’s language is more powerful than SAS or SPSS. R developers write most of their analytic methods using the R language; SAS and SPSS developers do not use their own languages to develop their procedures” is fundamental. To me, this expresses something about R that should speak to anyone who does statistical modeling no matter what tools she or he may be using. What is so compelling about R’s powerful language? I think that there is a direct analogy here with natural language. Every language enables thoughts peculiar to the culture in which it developed. If you speak more than one language, how many times have you labored to say something in another language that just comes so naturally in your mother tongue? Whether by design, or historical accident, some languages are just better than others for saying certain things. I propose that in the same way that English is the language of business , and that French may still be the language of diplomacy, R is the language of Statistics. I don’t just mean that R “is spoken” by many or even most statisticians. R’s superiority for statistics is deeper than that. R is a language with syntax and structure that have been explicitly designed to formulate expressions about statistical objects. At this time, it may be le premier langue for statistical thinking that enables the formulation of ideas, and notions about statistical models and data that are difficult to express succinctly in other languages including mathematical notation. For example, suppose you want to discuss multiple regression. A mathematical exposition might begin with the equation:

(1)    Y = X(beta) + epsilon  

A statistician will naturally interpret this as an expression of the regression model, but (1) is primarily a statement about the relationship of random variables, abstract mathematical entities not statistical models. In contrast, the R expression

(2)    model <- lm(y ~ x)

is a statement about the linear model that relates the data structures x and y. For a person who “speaks” some R, (2) “means” the model object coefficients, residuals etc. that result from fitting a linear model to the data structures x and y. Moreover, (2) actually makes “model” an object, packed with information that describes the regression and can be thought about as a whole and  “talked about” with other R expressions. There is certainly some overlap, but expressions (1) and (2) are really about different concepts.

As another example of the expressive power of the R language, consider how difficult it is to formulate multi-level hierarchical models in standard mathematical notation. With the aid of the notation “j[i]” which is used to encode group membership (j[10] = 2 means the tenth element in the data indexed by i belongs to group 2) Gelman and Hill (Cambridge 2007: a must read for anyone new at multi-level modeling) write the simple varying intercept model with one additional predictor as yi =( alpha)j[i] + (beta)xi +(epsilon)i. This nonstandard notation gets messy quickly as complexity increases, and as Gelman and Hill point out it doesn’t enable the unique specification of the model. (They discuss five ways to write the same model.) By way of contrast, their R code using the lmer function (now lme4):

model <- lmer(y ~ x + (1 | group) )

is succinct, preserves the syntax for linear models, and generalizes reasonably well with complexity. Just like there are some things that come naturally in your mother tongue but are awkward to express in another language, R enables concise statements about statistical models that are difficult to express otherwise.

R’s syntax is not the only feature that contributes to its expressive power. The interplay of R’s objects (nouns) with methods (verbs) facilitates formulating expressions that make sense under many different circumstances. For example, one can use the same R function “summary” to  form statements that talk about data: summary(x),  as well as statements that talk about models: summary(model). This ability of functions to have methods for different kinds of objects is a hallmark of R that greatly eases the process of learning the language.  It is easy to say statistical things in R, and just a little bit of language skill goes a long way in turning statistical thoughts into action packed, working statistical sentences.

Comments

[Pafy]

Your french is wrong.
It's "le premier langage" or "la première langue".

Interesting article :)

[Frederick Ross]

Saying R lets you formalize things that would be hard to do in mathematical notation just means you need to get better notation. R is a poorly designed language with brittle semantics. Code bases of more than trivial size are less likely to implode than in MATLAB, but that's not saying much.

The linear model example you are so fond of is simple to implement in a variety of languages. The other notations you point out are horrible, and I would never consider them for day to day work. And here we find the only reason anyone uses R: the libraries. Despite the failures of the language, enough people have cobbled enough useful code together in it where it's usually the path of least resistance in statistics to do it in R.

[Bob Muenchen]

I'm sure the vast library of add-on packages that R has is the thing that attracts the most people to it. Today's count is 3,691 and the number is increasing at close to an exponential rate. But why ARE there so many packages? Because programmers love to work in such an elegant language!

To be fair, the folks at SAS Institute have pointed out that I overstated the case in that quote from my book. While SAS developers do not write SAS procs using the SAS language, they do indeed use their language to write other applications such as Enterprise Miner. Still, I agree with the main premise that much of R is written in R itself and developers turn to other languages such as C and FORTRAN only when forced by computational needs.

Bob Muenchen

[John "Z-Bo" Zabroski]

See language discussion on Lambda the Ultimate:
http://lambda-the-ultimate.org/node/3726

A more balanced question would be, what are the pros and cons of choosing R?

Off the top of my head:
* R is not written in R.
* R cannot automatically do certain optimizations, because it cannot make certain static analysis gaurantees
* R does all of its operations in memory and does not have good support for enormous data sets
* Although the quality of the graphics for information visualization produced by R are good, they are limited, and extending R to support new visualizations is painful at best (pass me the Advil).

My claim to R fame is being chewed out on the R mailing list by the head of the Vanderbilt stats department.

[guest]

Is clojure the R we are looking for?

[batterie]

R is a poorly designed language with brittle semantics.

[Fabrice LOTY]

It is obvious programming languages tend to specialize.
C++ for system programming, Java for networking, and VBA for Windows. It is even more likely to expect specialization beyond the IT industry. So R is useful as it currently fills the gap.

[learn english online]

"Every language enables thoughts peculiar to the culture."i take your point.learning is a long term.