matloff / matloff/R-vs.-Python-for-Data-Science
Data.table being sidelined by Rstudio?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 448
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for the great write up, it surely provided some food for thought.
I have a question though:Under language unity you write:
"For instance, consider the lightning-fast data.table package. Rather than welcoming it as a hugely valuable contribution to R, RStudio has treated it as a competitor, downplaying it and promoting their own product, dplyr. This is simply not healthy for an open-source language."
I wonder if you could give examples or elaborate on that. I've actually seen some evidence to the contrary in the [dtplyr](https://github.com/hadley/dtplyr) package which is actively being developed by Hadley Wickham and is designed to integrate both packages.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the quoted “Under language unity” passage in the article and review the issue’s question about RStudio, data.table, dplyr, and dtplyr. Done would require deciding on specific examples or elaboration to add, but the issue does not identify an article file or a defined content change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100