Yeah - for the small data sets, Ruby or Python is often easier easier to use to whip a data set into a form that can be simply slurped into R as a dataframe.
Has to be said I cheated a bit on the Coursera course, I used Ruby to clean up some of the data. Seemed a lot easier, and it's a lot more likely I'd use some kind of scripting language (be it Perl, Ruby, Grep, ...) to do a first clean up than head directly to R to do the job.
With pandas / statsmodels / patsy, it's getting easier to stick with python for everything.
Re:The R learning curve
by GrumpySimon on Friday February 08, 2013 @12:02AM
(#5186378)
Don't forget Bokeh[1] - a replacement for ggplot2
Re:The R learning curve
by banachtarski on Friday February 08, 2013 @12:26AM
(#5186450)
This is a good point. Usually, I use haskell or something to do large scale transformations prior to a plot or something. However, I still use plyr from time to time to do quick one offs on smaller samples.
data.table is much faster. It's an extension to data.frames that adds some additional constrains/rules that allows for much faster operations including aggregating, subsetting, and merging data.
Cleaning data, however, does not have a steep learning curve or high difficulty level in R-- it has a steep learning curve and high difficulty level period. Implementing good procedures for data munging is 80% of the job.