Ever tried interacting with a GraphQL server in R and felt like giving up even before getting anywhere? Well, I have been there and I wrote this blog post to assist others.

• Packages
• API
• ghql
• graphql
• community

Using mcbette to pick the best evolutionary model for your DNA

• Software Peer Review
• packages
• community
• phylogenetics
• Bayesian
• model selection
• mcbette

At rOpenSci, we encourage R package developers to take advantage of Continuous Integration services to automatically check the package on different platforms, with different versions of R. The rOpenSci dev guide dedicates chapter 2 to the topic of Continuous Integration Best Practices, and recommends a few common CI vendors, including Travis CI.

Travis CI has been a pioneer in free public CI services, and made the concept popular in the open-source community. The service started to get wide adoption in 2012, and native support for R was added by Craig Citro in 2015, with more contributions from current maintainers Jim Hester and later Jeroen. In 2016 we wrote a blog post about using a build-matrix in order to check your packages on multiple versions of Linux and MacOS, which is super powerful for R package development.

• CI
• Travis
• packages
• tech notes
• r-universe

Behind the scenes of getting article full text.

• literature
• textmining
• fulltext
• packages
• tech notes

Google’s amazing V8 JavaScript/WASM engine is probably one of the most sophisticated open-source software libraries available today. It is used to power the computation in Google Chrome, NodeJS, and also CloudFlare Workers, which make it possible to run code for your website inside the CDN edges.

The R package V8 exposes this same engine in R, and has been on CRAN since 2014. It is used by many R packages to wrap JavaScript libraries, such as geojsonio, jsonld, DiagrammeR, or almanac. Recently we have seen an increase in usage because the latest version of rstan now uses V8 for their parser.

• V8
• Linux
• tech notes