[R-gui] Re: [R] The hidden costs of GPL software?
Mervyn Thomas
mervyn.thomas at emphron.com
Thu Nov 18 14:23:37 CET 2004
I have found this discussion interesting, and Michael's comments seem to me to
be right on the money :)
It seems to me that one thing we can learn from the commercial software world
is the benefit of defining the "market segments" for R, and of identifying
the needs and drivers of each segment.
A rough starting point for that definition might include the following
segments:
1) A Statistical or machine learning researcher needing a rapid development
framework to implement and prototype her research;
2) Consultant statisticians / data analysts needing a flexible modelling tool
in which to perform state-of-the-art analyses. A typical worker of this type
will use R daily; she will have a sophisticated knowledge of statistics, and
broad experience of programming.
3) Application builders or system integrators needing to use R to deliver
packaged, and specialist functionality. A typical user of this type will have
sophisticated knowledge of information systems and software engineering, and
some knowledge of statistics.
4) Scientists, or other non statistical and non IT professionals needing a
good solution for general purpose statistical analysis. Such a person will be
familiar with spreadsheets and other office productivity tools, will have
limited knowledge of statistics and limited knowledge of IT.
The needs of these segments are very different. Segments 1,2 and 3 will
probably have little need for a GUI - but may benefit enormously from an IDE.
Segment 3 will benefit from having a rapid development tool for building GUIs.
Segment 4 will be looking for a GUI which insulates them from the technical
details of the statistical models, and from the need to program analyses.
It seems to me that R addresses segments 1 and 2 brilliantly, that it has made
real progress in segment 3 (though much more could be done) and that in its
current form it makes little provision for segment 4.
If R were a commercial operation, the decision would be simple - what is the
size of each segment?, how much is each segment prepared to pay? what are the
emerging requirements of each segment? How easily can each segment be
supported with our existing architecture? what is the cost of providing for
each segment?
For a community it is more difficult - we all have a different profile in the
"market" and therefore have different needs and differences of opinion about
the best direction for the R project. I personally operate mostly in segment
2 - and I do not need and would not use a GUI. I don't want anything to get
in the way of the flexibility of a statistical language. I can't afford Splus
- so I just have to put up with the superior performance, stability and focus
of R :) Whilst I may have sympathy for the needs of segment 4, I can't say
that I feel especially motivated to do anything about them.
Kindest regards
Mervyn Thomas
More information about the R-SIG-GUI
mailing list