I developed an #RStats package to get data from a remote service. Functions allow caching results, so that they will just return the saved files if the request is the same. I tend to be conservative and set the cache option to FALSE by default, but now I'm wondering if it would be more user friendly (and friendlier to the remote API) to set the default to TRUE.

What say the R community?

Use cache by default
75%
Don't use cache by default
25%
Poll ended at .

@eliocamp When I talked the maintainer of {ranger} into setting the default of num.threads to 2 rather than "all available cores", my argument was that the default scenario should prevent users from "causing damage", which in that context meant accidentally overparallelizing and overloading a shared workstation. His argument was that people don't read the docs and complain why ranger is so slow when the default is lower.

I'd still argue in favor of "do less and make people read docs" 😬

@jemsu Is "doing less" caching by default or not caching by default in this context? 😅
@eliocamp Cache once and do less API calls afterwards 😅