1,012 karma · joined January 8, 2018
It has a high-quality pathtracing renderer built-in (https://www.rayrender.net) that only requires a single line of R code to produce results similar to what's offered here (without all the manual work).
These features aren't of interest to practicing statisticians, which the parent comment was talking about.
> data.frame is just a giant chunk of c (c++) code that one must interact with in very specific ways
I don't understand this criticism: yes, data.table has an API.
Benchmarks: https://www.ritchievink.com/blog/2021/02/28/i-wrote-one-of-t...
The only difficulty with Rcpp-based R packages is you have to ensure the target system can compile the code, which means having a suitable compiler available.
I've been impressed with Julia, but it's hard to beat 25 years of package development.
Although this is a tangent from the above conversation, this isn't actually true: well-designed experiments can indeed change multiple variables at the same time. There's an entire field of statistics dedicated to experimental design (google "factorial designs" for more information). One-factor-at-a-time (OFAT) experiments are often the least efficient method of running experiments, although they are conceptually simple.
See the following article for a discussion: http://www.engr.mun.ca/~llye/czitrom.pdf
Also, PBR is getting a fourth edition this year that goes into fully GPU rendering—it's a great time to start learning about pathtracing!
*Rayrender Github: https://www.github.com/tylermorganwall/rayrender
Website/Docs: https://www.rayrender.net
I also provide instructions in my (free and open source!) masterclass on how to take LIDAR data from cities and build 3D surface models that includes buildings:
Github Course Materials:
And that video looks like a great resource--I'll put it on my watch list.
Github: https://www.github.com/tylermorganwall/rayshader
And browse the documentation (with rendered examples) and README on its website: https://www.rayshader.com