I am not necessarily referring to the business model (though many people asking
this question are), but rather the install-to-bare-os deployment model that
controls the user experience throughout. You typically need to install R as a
separate product and use it interactively to kick your "application" into gear,
should you choose to develop such.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnew...@dcn.davis.ca.us> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
On September 28, 2015 6:26:57 AM PDT, John McKown
<john.archie.mck...@gmail.com> wrote:
>On Mon, Sep 28, 2015 at 8:15 AM, Jeff Newmiller
><jdnew...@dcn.davis.ca.us>
>wrote:
>
>> R is not designed as an application development programming language.
>
>
>This is an interesting statement to me. I don't really understand it.
>I
>have developed some applications in R. Do do you mean _commercial_
>applications (i.e. something paid for)? I think of R a bit like I
>think of
>SAS (which may be stupid of me). There are some commercial SAS
>applications
>(one that I know of is MXG for doing performance analysis and reporting
>on
>a specific OS - z/OS, which runs on IBM z series "mainframes").
>
><snip>
______________________________________________
R-help@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.
