43 karma · joined December 9, 2017
My employer is using R to crunch numbers enbeded in a large system based on microservices.
The only thing to keep in mind is that most people writing R are not programmers by trade so it is good to have one person on the project who can refactor their code from time to time.
The only meaningful alternative I see is Python with maybe Polars or DuckDB.
Even if most people use R interactively, having contributers working on compiler has many positive spillovers for the language.
Also note that the R code running behind the scenes of your scripts (powering the functions of your favourite packages) is quite a different language, using less dynamic features. This is where a better compiler would always be appreciated.
My first computer too. Got it from my uncle without any manuals, we spend a whole afternoon writing down a code of a game from a magazine letter by letter. We thought we will just press the "Start" functional key on the right side. To our surprise, sadly, absolutely nothing happened! After few more hours, my dad came home and it took him few guesses to finally type "RUN" in the console...
* tight connection to insurance
* typical consumer-producer relation relation broken into consumer(patient)-prescriber(doctor)-producer-payer(insurance or government)
* large externalities
These factors led to health care being provided by the public sector in most of the countries.
that rules out any Adobe product :)
R is single-threaded.
Its not a coincidence that the author gives an example from the tidyverse ecosystem. Authors and users of tidyverse value other things like consistency and new features over API stability and backward compatility. The base-R ecosystem is actually very stable and so the original package manager is very simple.
With R spreading out from the academic environment and with many new authors breaking their packages' APIs we observe new attempts to solve the issues with dependencies (such as renv or https://rsuite.io)
What do you think of the new renv package?
If you write a function and need stable behavior use m[x,, drop = FALSE]. Problem solved.
No need of tideverse (which comes with its own surprises).
But its still much better experience to use RStudio markdown than Jupyter for me.
mydt[, newvar := oldvar1/oldvar2]
I could not resist.