blogdown

Vlad Fridkin (@vlad_fridkin; 1/1): Episode 5 in Journeys with data, we phone organisations that use billboards to validate our MVP https://t.co/1Z7FCEIGJO… written in R #blogdown this is the story of our experience in #MelbDatathon #MelbDatathon2018 ↪

bookdown

Athanasia Mowinckel (@DrMowinckels; 6/1): shout out to @xieyihui for making the #bookdown package, which just gave me some serious work cred because I adapted out 8-seperate word document manual into a single sleek github pages book.

Thanks a billion, man. Its true magic! Looking forward to seeing you at Rstuido::conf! ↪

Richard Torkar (@rtorkar; 1/1): Statistical Rethinking with brms, ggplot2, and the tidyverse https://t.co/us6OtVgF2d ↪

Solomon Kurz (@SolomonKurz; 0/0): @p_alab @rlmcelreath @paulbuerkner Glad to hear it! Yeah, I’m becoming a big fan of the bookdown format ↪

Paulius Alaburda (@p_alab; 0/0): @SolomonKurz @rlmcelreath @paulbuerkner Thank you! I put off learning brms for a month because of other priorities but a bookdown format is definitely enticing to get back into it! ↪

knitr

Saki.K (@sakikuzu; 3/0): @phoenix919jp knitrされた部分は違いが無いと思うので、全体の文書をlatexかRmarkdownどちらで作りたいかの違いかと…（私はproblem setの提出の指定でlatexで書けと書いてあったので、latexを使っています） ↪

baptiste (@baptiste_auguie; 1/0): @bhive01 @ClausWilke Oh absolutely! It’s not like I’m complaining – why haven’t I done anything about it then? :) Frustration over limitations can lead to better tools – knitr/sweave is a prime example – but sometimes the quantum leap occurs with unpredictable time, position, spin, and momentum ↪

Saki.K (@sakikuzu; 1/0): @ike_og_ike Sweaveは使ったことないのですが、Knitrしたあとのtex fileをコンパイルした時のエラーメッセージが読みづらいのはR markdownでKnitrした時も同じだったので、Knitrの問題のような気がします…。 ↪

yihui.name

Sigrid Keydana (@zkajdan; 7/2): Love this https://t.co/FJv2R6Lg7T https://t.co/9zxB7VGg38 ↪

Ingo Rohlfing (@ingorohlfing; 1/1): xfun::pkg_attach(): A Vectorized Version of library() https://t.co/QEbElM93Py by @xieyihui Makes little things a little bit easier #rstats ↪