3 ms·
R is my go-to for ad-hoc data science as well. And you’re right, deprecations are generally replaced with something nicer. From the perspective of a language us
by adeelk93 5y ago
R is my go-to for ad-hoc data science as well. And you’re right, deprecations are generally replaced with something nicer. From the perspective of a language used for ad-hoc analysis, these are all great features. Hadn’t thought of it that way.
Which further emphasizes the idea of: R might not be the right tool for production processes. I used to fight that concept, but in the past year or so I’ve come to embrace it.
- 555watch 5y agoIt's not that difficult to fix package versions for any prod deployment, as long as you deploy the projects as R packages. You can fix the versions in the ``DESCRIPTION`` files, which are easy to manage through, e.g., Docker and ``devtools::install_version``. Essentially, not a huge difference from ``requirements.txt`` that we're used to.
- adeelk93 5y agoDESCRIPTION files don't actually solve this problem - if you're trying to peg a package version, and it inevitably ends up an outdated version in the future, you'll be greeted with that error "Package 'xxx' is not available". Why? That version has been archived. I'm sure you've run into this error at some point. devtools I guess is a solution (write some code to iterate over package requirements), but let me ask you this - how do you protect against breaking changes in devtools? I have yet to encounter something more reliable than MRAN snapshots https://mran.microsoft.com/documents/rro/reproducibility https://mran.microsoft.com/documents/rro/reproducibility