This mailing list seems to steadily get messages that some see as not relevant to this forum. In particular, some see it as wrong to bring up some things here and keep reminding people of some ground rules. So I want to know, briefly, if it is reasonable to ask a person with a question or problem to reproduce their problem another way. If using RSTUDIO or one of many IDE, can they run the code on a naked R interpreter by sourcing the file or copying it in or typing it anew, or perhaps using IDLE which comes by default with many installations of R? If using a library (which I like so I am not really in agreement about the unsuitability) like the tidyverse which is free and available to all even if loosely associated with the RSTUDIO folks and that can be run on any version of R that I am aware of, then some questions may still be fair if they are really about more general R issues as much of the rest of the code may be base R and may be the cause of whatever issue is being reported. And, some simple requests like pointing out a missing comma, ... I have stated my thought before and it boils down to the reality that there are some things about earlier versions of R that were far from perfect or complete and a little healthy competition is not a bad thing and may help base R evolve. Not everything in the tidyverse is better and it keeps evolving and deprecating older features, but it cannot really be ignored any longer. If you apply for a job at some company as something of an R expert, you may well be asked by all kinds of people about their programs that use the tidyverse for help or to help them solve a problem. You don't have to like it, but if you cannot read it, you no longer are really qualified in many places. Ask yourself if a language like R was created from scratch, what graphics might be built into the base distribution? Would you rather have lattice or ggplot or perhaps both as well as base R graphics? Would you make many of the built-in functions more consistent, so for instance, the data being worked on would be the first argument whenever possible? One reason there are so many packages is not so much due to the superiority of R but because people find it lacks quite a bit. Much of that should not be included, of course, if R is meant to be somewhat on the lean side, and yes, packages are a deliberate way to extend it when needed. But when people use it and think they are programming in R, ...
On 27/02/2022 21:34, Avi Gross via R-help wrote:> This mailing list seems to steadily get messages that some see as not relevant to this forum. In particular, some see it as wrong to bring up some things here and keep reminding people of some ground rules. > So I want to know, briefly, if it is reasonable to ask a person with a question or problem to reproduce their problem another way. If using RSTUDIO or one of many IDE, can they run the code on a naked R interpreter by sourcing the file or copying it in or typing it anew, or perhaps using IDLE which comes by default with many installations of R? If using a library (which I like so I am not really in agreement about the unsuitability) like the tidyverse which is free and available to all even if loosely associated with the RSTUDIO folks and that can be run on any version of R that I am aware of, then some questions may still be fair if they are really about more general R issues as much of the rest of the code may be base R and may be the cause of whatever issue is being reported. And, some simple requests like pointing out a missing comma, ... > > I have stated my thought before and it boils down to the reality that there are some things about earlier versions of R that were far from perfect or complete and a little healthy competition is not a bad thing and may help base R evolve. Not everything in the tidyverse is better and it keeps evolving and deprecating older features, but it cannot really be ignored any longer. If you apply for a job at some company as something of an R expert, you may well be asked by all kinds of people about their programs that use the tidyverse for help or to help them solve a problem. You don't have to like it, but if you cannot read it, you no longer are really qualified in many places.There's an easy way to test this: There are already several r-sig-* lists. I might suggest to create a new r-sig-base list. Those who want to ask and answer issues dealing with base R only would be invited to migrate to that list. Then this current list could be broadened to address questions about R as well as other (popular) packages. Yes, the list might get flooded with questions about obscure packages, or about statistics. But if no one answers, posters will eventually learn to go straight to the package maintainers, or elsewhere. And, along the way, it would save the numerous "irrelevant, off topic..." responses that you refer to. Kind regards,> Ask yourself if a language like R was created from scratch, what graphics might be built into the base distribution? Would you rather have lattice or ggplot or perhaps both as well as base R graphics? Would you make many of the built-in functions more consistent, so for instance, the data being worked on would be the first argument whenever possible? > > One reason there are so many packages is not so much due to the superiority of R but because people find it lacks quite a bit. Much of that should not be included, of course, if R is meant to be somewhat on the lean side, and yes, packages are a deliberate way to extend it when needed. But when people use it and think they are programming in R, ... > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.-- Micha Silver Ben Gurion Univ. Sde Boker, Remote Sensing Lab cell: +972-523-665918 https://orcid.org/0000-0002-1128-1325
Hi Avi, I just sent in an answer to a very simple question. In many cases it seems to me that the real problem isn't apparent from the request. ektaraK appears to have almost no experience with R (sorry if I'm wrong). A person in this position may sort of know what they want to do but do not know how to ask the question. What's a reproducible example? So I often submit really dumb looking answers that show the person how to ask the question. If I'm successful, the OP learns how to do some basic operation, but also learns how to ask the next question. Until they get there, most responses just give them a typing exercise. Jim On Mon, Feb 28, 2022 at 6:35 AM Avi Gross via R-help <r-help at r-project.org> wrote:> > This mailing list seems to steadily get messages that some see as not relevant to this forum. In particular, some see it as wrong to bring up some things here and keep reminding people of some ground rules. > > So I want to know, briefly, if it is reasonable to ask a person with a question or problem to reproduce their problem another way. If using RSTUDIO or one of many IDE, can they run the code on a naked R interpreter by sourcing the file or copying it in or typing it anew, or perhaps using IDLE which comes by default with many installations of R? If using a library (which I like so I am not really in agreement about the unsuitability) like the tidyverse which is free and available to all even if loosely associated with the RSTUDIO folks and that can be run on any version of R that I am aware of, then some questions may still be fair if they are really about more general R issues as much of the rest of the code may be base R and may be the cause of whatever issue is being reported. And, some simple requests like pointing out a missing comma, ... > > I have stated my thought before and it boils down to the reality that there are some things about earlier versions of R that were far from perfect or complete and a little healthy competition is not a bad thing and may help base R evolve. Not everything in the tidyverse is better and it keeps evolving and deprecating older features, but it cannot really be ignored any longer. If you apply for a job at some company as something of an R expert, you may well be asked by all kinds of people about their programs that use the tidyverse for help or to help them solve a problem. You don't have to like it, but if you cannot read it, you no longer are really qualified in many places. > > Ask yourself if a language like R was created from scratch, what graphics might be built into the base distribution? Would you rather have lattice or ggplot or perhaps both as well as base R graphics? Would you make many of the built-in functions more consistent, so for instance, the data being worked on would be the first argument whenever possible? > > One reason there are so many packages is not so much due to the superiority of R but because people find it lacks quite a bit. Much of that should not be included, of course, if R is meant to be somewhat on the lean side, and yes, packages are a deliberate way to extend it when needed. But when people use it and think they are programming in R, ... > > ______________________________________________ > R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code.
FWIW my brief answer to your brief question is "of course" it is okay. The real problem however are the questions that can only be answered by people with detailed understanding of non-R-related issues, such as the workings of the custom interactive graphics device used by RStudio or the broken behavior of some random GitHub-hosted package. There are a continuum of possible "degrees of relevance" that a question can have to the topic of a given discussion area (e.g. web forum or mailing list). The people who don't use RStudio don't gain benefit from wading through discussions that only have relevance to that tangential topic, and the more of that there is the lower the signal-to-noise ratio is from their perspective... and the sooner they leave. Ideally we will be kind in our redirection of the uninitiated, but an actual answer may not be feasible here... going elsewhere for a specific question should not be viewed as a negative outcome. Since there are various interpretations of where the line should be drawn, it is best that it be drawn as the discussion area charter says it should... in this case, about R, the language. It is pretty explicit that discussion of contributed packages is not on-topic... presumably because allowing that can easily lead to highly arcane discussions that don't necessarily help people understand the R language better. I think the existence of contributed packages and various development tools is hugely beneficial and I depend on many of them... but that doesn't automatically give any of them carte blanche to become actual topics of discussion here. On February 27, 2022 11:34:33 AM PST, Avi Gross via R-help <r-help at r-project.org> wrote:>This mailing list seems to steadily get messages that some see as not relevant to this forum. In particular, some see it as wrong to bring up some things here and keep reminding people of some ground rules. > >So I want to know, briefly, if it is reasonable to ask a person with a question or problem to reproduce their problem another way. If using RSTUDIO or one of many IDE, can they run the code on a naked R interpreter by sourcing the file or copying it in or typing it anew, or perhaps using IDLE which comes by default with many installations of R? If using a library (which I like so I am not really in agreement about the unsuitability) like the tidyverse which is free and available to all even if loosely associated with the RSTUDIO folks and that can be run on any version of R that I am aware of, then some questions may still be fair if they are really about more general R issues as much of the rest of the code may be base R and may be the cause of whatever issue is being reported. And, some simple requests like pointing out a missing comma, ... > >I have stated my thought before and it boils down to the reality that there are some things about earlier versions of R that were far from perfect or complete and a little healthy competition is not a bad thing and may help base R evolve. Not everything in the tidyverse is better and it keeps evolving and deprecating older features, but it cannot really be ignored any longer. If you apply for a job at some company as something of an R expert, you may well be asked by all kinds of people about their programs that use the tidyverse for help or to help them solve a problem. You don't have to like it, but if you cannot read it, you no longer are really qualified in many places. > >Ask yourself if a language like R was created from scratch, what graphics might be built into the base distribution? Would you rather have lattice or ggplot or perhaps both as well as base R graphics? Would you make many of the built-in functions more consistent, so for instance, the data being worked on would be the first argument whenever possible? > >One reason there are so many packages is not so much due to the superiority of R but because people find it lacks quite a bit. Much of that should not be included, of course, if R is meant to be somewhat on the lean side, and yes, packages are a deliberate way to extend it when needed. But when people use it and think they are programming in R, ... > >______________________________________________ >R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see >https://stat.ethz.ch/mailman/listinfo/r-help >PLEASE do read the posting guide http://www.R-project.org/posting-guide.html >and provide commented, minimal, self-contained, reproducible code.-- Sent from my phone. Please excuse my brevity.