4 ms·
I write in R for much of my work days, and perhaps because I learned when the tidyverse was in its infancy (or before) I don't use much at all of its packages b
by kuhewa 4y ago
I write in R for much of my work days, and perhaps because I learned when the tidyverse was in its infancy (or before) I don't use much at all of its packages besides ggplot2. With the base r pipe operator I use zero dplyr and find most of its functionality has long existed in base R with functions like transform(). lubridate has a few good convenience functions (that ultimately I could do without), and I do like plotting in ggplot2 - in fact the latter is the only place I reckon there has been too much of a takeover because most plotting development effort I imagine is based on the grid and ggplot2 framework now. I do like tidyr::pivot_longer(), although it wouldn't change much if I had to use the less intuitive base R versions for dataframe manipulation.
Your colleagues are probably a symptom of how low the barrier to entry has been made by the tidyverse moreso than indicative of a total capture of the language.
- jhbadger 4y agoI like the tidyverse in general, but I have to admit I've never gotten the hang of tibbles. I use dataframes because I like row names and pretty much every non-tidyverse package uses dataframes and row names too. I really don't understand why row names (a basic feature of R) are viewed with such disdain by the ecosystem and can't be set using tidyverse functions like read_tsv. I generally end up converting them to dataframes after using them.