Data science has a two language problem. R and python are both the language for data science. This has lead to some pretty abstract, generic and sometimes absurd definitions between the two languages. The worst is probably this image:
Data science is such a wide term, with sometimes a very diverse or even poor understanding in business, that clickbaity titles giving superficial answers abound. I’ve tracked down the source of this image, which has also floated around on twitter once (2016) or twice (2018). To give the author of the post his dues, the article it’s derived from is interesting, and I hope the SEO bonus from publishing as the film hype cycle grew got him some extra book sales (the books he links to are actually really worth reading).
I first came across it on (a now removed) instagram post where it was literally captioned "How to pass any data-science interview" on an account specifically advertising it’s data science recruitment services. I’m not against pop-culture/programming bleed over in any form (I’ve done enough Pokemon programming talks that any horse I get on has to be less Rapidash and more Ponyta), but at the point that people who are trying to break into the industry are being told this is valuable information to tell an interviewer, then there is evidently a gap between needs and knowledge.
The difference, and decision for the ‘right’ tool for the job is actually defined by a mixture of internal and external factors. Both languages, in themselves, do the job of data ingest, processing, analysis, modelling and prediction equally well. Both can be deployed on-premises or on the cloud. Both Minor differences in syntax, and major differences in deployment tooling become the defining factors.
Any programming language is little more than syntax. Functional, Object-oriented, Imperative and more, in various combinations, with specific conventions and patterns. Curiously both R and Python are ‘Multi-paradigm’ according to Wikipedia. This means that multiple, different styles can be used depending on the problem at hand. You can write python in an OO way, or a functional way. R is often thought of as functional, though it allows the construction of classes, and objects with methods, and side-effects, so it’s not a ‘pure functional’ language.
In R, data science is a first class application (and maybe even sole aplication?). Tidyverse is arguably the de facto way to write most R projects now. With RStudio giving it full corporate support and funding an eco-system of tooling, most R I write, have seen others write, and I’ve taught people to write is in this style. Pipes
-> chain function calls with non-standard evaluation of arguments, Rmarkdown documents, ggplot visualisation and shiny apps are an R data scientists solution of choice. Tidyverse is itself functionally inspired, purrr explicitly states this and Hadley Wickham directly argues that "R, at its heart, is a functional programming (FP) language."
Python is everywhere. Data science in Python isn’t pythons only reason for existence. scipy is the python tool chain for data science. numpy and pandas are best of buddies, and matplotlib is a front runner for graphics. This collection of tools is far less cohesive though, with scikit learn, seaborn and jupyter notebooks also being hugely popular, but totally removed from the scipy ecosystem. These tools therefore need a bit more work to mould into a full product. Object Oriented programming is also more popular, even for data science. This means you’ll be calling objects more directly, and explicitly pulling out methods on objects with
myObject.method more often.
Do you understand functional programming or object oriented programming already, or is one immediately making sense over the other? Great, use that one. Do you already have an ecosystem of certain tools? Great, use whatever you already have. Do you already have colleagues that you need to work with? Great, use whatever they are. Do you already have a support network around you for one language but not the other? Great, don’t make life harder than it needs to be.
What if you don’t have an easy answer though? You’re starting a new project, or you are the only programmer in the business? Then the choice becomes harder to get right, but more clear the more experience you have. When you know both tools can achieve the same job, you have to choose which one does it more easily. I’ve found that I will reach for python and R equally now I’ve been working professionally in both for a while, however, which I use is defined pretty clearly.
R encapsulates statistic and mathematical ideas clearly and robustly. Depending on where you get your dependencies from you can have a very clear idea of the likely ‘correctness’ of the library. Roughly ROpenSci is more rigorous and stable than CRAN which is better than github. Tidyverse pipes, NSE, purrr give a tightly coupled working environment where syntax is consistent, terse, and trivially refactored. ggplot and RMarkdown give business consumable outputs from the start, where code can be kept tightly coupled to narrative and reporting, but also infinitely customisable to produce something that would get past marketing without a glance. Many academic publications rely on R and RMarkdown for both research and publication. If you need to make interactive output, shiny is a straightforward application framework, with a tight to everything else in this ecosystem.
R is for analysts who need to be certain of the underlying data processing immediately, produce and iterate on reporting outputs as fast as possible and write the least code for the most return. Hadley effectively said as much last week.
I think R Markdown is an amazing contribution to R. … When you are doing data analysis typing speed is actually a bottleneck.
Python is already used tonnes more than R because data science isn’t it’s only job. Data engineers use it very heavily, back-end and even front-end developers use it for all kinds of projects, wether it is data intensive or not. In many linux distributions (including Mac) it’s actually installed as part of your machine when you put the operating system on. It’s also arguably a cloud native language. AWS lambda functions support it out of the box, and Microsoft recently copied them. This is doubly interesting as Microsoft bought one of the biggest R consultancies in 2015, but as of yet R is not a natively supported language in much of Microsofts ecosystem. It’s definitely got more baked in R support than AWS (PowerBI and many others), but has made moves to potentially trim back MRAN. All this means that Python is spoken by most developers, that python is supported by most big cloud providers, and that python is probably already built into whatever you are working on.
Python is for developers who need to deploy software within a traditional software environment in a more traditional development workflow, where first-class cloud support matters, and integration with existing code is of top priority.
R doesn’t necessarily deploy easily into software development (not strictly related, but great talk that’s relevant to the problem), though it is definitely possible (I’ve done it), you have to put in more work to get a roughly similar result. In many situations, that trade off might not be worth it.
Python doesn’t necessarily fit into BI and academic workflows, thought it’s definitely possible (I’ve also done it), you have to put in more work to get a roughly similar result. In many situations, that trade off might not be worth it.
Superman, Batman, Detective Work, Intelligence, Cunning, Usage of Tools, More Brain than Muscles, Muscle Power, Super Strength, Elegance, Wide Range, More Muscles than Brain are not meaningful differentiators.