Quarto vs. R Markdown

Hello everyone! I’ve been using R for 99% of my work already and I want to dive deeper into automated reports and publishing. I have learned R Markdown through the Intro Course and that’s what I have been using to produce simple reports. However, I’ve encountered more online resources pointing to Quarto as the “upgrade” to R Markdown (but none from the applied epi niche). I’ve been playing around with it for a few days and for my purposes it seems that there isn’t much difference between the two. Any insights from other applied epis who have tried both or transitioned from R Markdown to Quarto?

Hi @iancgmd

I’ve recently switched to Quarto for everything. The biggest benefits for me are (1) you can integrate a bunch of different code (R, Python, Bash etc) in a single document and (2) it makes the process of rendering as books, websites etc so much easier.

It’s a big step forward in my opinion, but one that doesn’t require a huge amount of relearning as it is close enough to R markdown that you already know how to use it.

Also, the new visual WYSIWYG interface for RStudio is great. Much nicer for writing longer texts (ie. where code is secondary or minor part of the script) than having to do things in pure markdown.

1 Like

Hi, I also tried to us quarto, and it works great for visual editor; feels much better than rmarkdown, but for automatization, I haven’t learn how to use it with purrr or in for loops, probably there is a way but for now, Im sticking to knitr.

Thank you for your insights @chrissyhroberts and @leoneler ! I watched Neal’s keynote presentation in R/Medicine and it seems part of the plan is to transition the Epi R Handbook from R Markdown to Quarto.