Re:R Markdown: The Definitive Guide
by runningmike on Wednesday February 03, 2021 @02:58PM
(#26018370)
Jupyter Book is more flexible, simpler and tested to death since it is build upon Sphinx and docstrings. Since jupyter uses pandoc for converting notebooks, pandoc is the power tool for publication creations nowadays.
[ Parent
| on HN ]
Re:R Markdown: The Definitive Guide
by spinningslate on Wednesday February 03, 2021 @03:05PM
(#26018454)
Jupyter has downsides too, e.g. version control. An R Markdown document "in the raw" is just a text file.
For info, Rmd also uses pandoc under the covers. Agree it's the power tool, quite a wonderful thing.
Re:R Markdown: The Definitive Guide
by ideamotor on Wednesday February 03, 2021 @07:29PM
(#26021112)
I haven't use it myself but apparently jupytext (https://github.com/mwouts/jupytext) allows you to save Jupyter notebooks as R markdown files.
Re:R Markdown: The Definitive Guide
by qbasic_forever on Wednesday February 03, 2021 @03:52PM
(#26018942)
Jupyter Book (and the larger jupyter ecosystem now) are starting to standardize on MyST notebooks as a version-control friendly all text notebook format. It's similar to r markdown and uses fenced code blocks to represent code cells. You can diff them, edit in any text editor, etc. See: https://myst-nb.readthedocs.io/en/latest/
I'm familiar with both Rmarkdown and Jupyter Book. Rmarkdown also uses pandoc. Both are very flexible.