R is actually a nice language (also with multiple dispatch!), but it's basically useless for any actual numerical work. Too slow. There have been efforts in the past to introduce a JIT compiler, but nothing has become mainline yet. The GC is also very poor.
The actual base system in R is also very small. The built-in vector types helped the language mitigate the issue due to the fact that it's very easy to build a C extension that does the actual computation by just taking the underlying memory pointer (it's actually easier to do than python and it maps much better). But it stops there. If it wasn't for the large swath of statistical packages, R wouldn't have much traction. Not to mention that the code quality of the typical CRAN package is quite low, coming from people with a background in statistics and very little CS knowledge.
The hope with Julia is being able to actually develop methods in Julia itself. I personally looking forward to replace python&c++ with Julia&Rust in the future.
It's been included in the default install of R since version 2.14. You can compile any function you want, and in some cases you can get a speedup of several times. Sure, you're not getting the speed of C, but it's there, it works, and in the future it will lead to much larger speedups.
Some info and timings are here: http://www.rinfinance.com/agenda/2014/talk/LukeTierney.pdf
The experimental version of the compiler can achieve speedups in the neighborhood of 20x.
Not really. That's an example of one R's rough edges. I did the same thing.
[1] See page 7 of the presentation I linked above.
I agree, but Community & Ecosystem are critical to any language's success. R's community is great and getting better [1].
You could make very similar criticisms about JavaScript, which is a lousy language that has accomplished amazing things thanks to third-party extensions and a very active development community.
[1] http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
Rust is filling the same niche I'm using c/c++ for, where I need absolute control of every detail: not necessarily for performance.
For the JVM, Clojure and Incanter seem like a better statistical bet. I heard they're moving toward a 2.0 release of Incanter too...
Julia's sweet spot seems to be anyone who needs to do statistical work who also has an existing C ABI based environment.
The ability to seamlessly plug in Julia to your production system via C code is a boon for those of us who have to use R in an "offline" capacity and then feed data to production systems.
The downside of alot of the Julia posts is that its not R. R, for better and worse, has many years of bug fixing and library design behind it.
I have yet to stump cran (http://cran.r-project.org/) when looking for a library and after 5+ years of using R I still am amazed that I can learn some new ability that ggplot can do.
My advice to people who ask what language to use is always, I think Julia is still a bit too early on to use unless you already know what code you want to write and are using a C based enviroment.
The reason is that most programmers just want to get one task done. They aren't an expert on the mathematical domain they are trying to use, they just want to plug their values into a library and get their results and maybe print them in a nice format. With Julia I still run into issues too often where you have to second guess the langugage or library and if you aren't fully sure that your math is right you tend to assume you are wrong:)
Otherwise use R. It just works and it will make googling for answers much easier.
EDIT replaced jvm with C ABI. Not sure how I made that big of a typo:(.