As someone who fwded initial story to both SAS and R lists, I find the
messages on this forum and on SAS-L forum (which are publicly available) a
contrast  ( One list is partying like they won the World Series -the other
one talks of either self denial.....or of self appraisal and anguish)
http://www.listserv.uga.edu/cgi-bin/wa?S2=sas-l&q=&s=New+York+Times+&f=&a=Dec+2008&b=

Having said that, can we get back to coding.....

Ajay

The best things in life are free.

On Thu, Jan 8, 2009 at 9:17 AM, Gabor Grothendieck
<ggrothendi...@gmail.com>wrote:

> On Wed, Jan 7, 2009 at 10:26 PM, Dirk Eddelbuettel <e...@debian.org> wrote:
> >
> > On 7 January 2009 at 18:24, Gabor Grothendieck wrote:
> > | By running the code below we see that the:
> > | - sum of the three seems to be rising at a constant rate
> > | - S is declining
> > | - SAS and R are rising
> > | - R is rising the fastest through its completed its phase
> > | of highest growth which ended around 2004
> >
> > I wonder whether we need to account for traffic on all the additional
> r-sig-*
> > mailing lists ?
> >
> > Of the handful that I follow, some seem to have taken traffic from
> r-help.
> > This could account for (at least parts of) the apparent traffic growth
> > slowdown since 2004 as many of these added lists appeared only in the
> last
> > few years.
> >
>
> Good observation.  It would be interesting to combine the data from all
> the lists to see what the effect is.
>
> ______________________________________________
> R-help@r-project.org mailing list
> 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.
>

        [[alternative HTML version deleted]]

______________________________________________
R-help@r-project.org mailing list
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.

Reply via email to