21–30 of 61 posts
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.
For info, Rmd also uses pandoc under the covers. Agree it's the power tool, quite a wonderful thing.
Background: https://blog.jupyter.org/survey-jupyterlab-and-beyond-88c7fb...
R Markdown/Notebooks, IMO, has evolved to be the key value proposition of RStudio over the years. From a productivity standpoint when both working with R and publishing pretty reports/PDFs it has been incredible. (that said, if VS Code gets more robust R Markdown support, I may consider switching from RStudio) I wrote a blog post a few years ago comparing R Markdown/Notebooks to Jupyter Notebooks: https://minimaxir.c…
Funny thing is this has actually motivated me to move away from using rmarkdown. To the point that I went "backwards" and wrote several reports and an academic paper in Sweave after using rmarkdown for years. My primary motivation was that I needed to know the documents could be built by any R session, not just from within RStudio. I didn't want to be in a situation where my "reproducible" document relied on a specif…
Anyway, this feeling set me off on an exploration of alternative tools and packages. Instead of rmarkdown I'm now exploring the pander[1] package, which seems to do most of what I'm looking for, perhaps only a little limited in output formats.
Edit: The Pandoc.brew examples might be most interesting from a direct alternative to rmarkdown for document creation context.[2]
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.
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.
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.
As an occasional R user, I think R markdown one of the things that R does really well. For data scientists who want to output reports (mix of text and calculations), I haven't come across anything as mature or easy to use in the Python ecosystem. I'm a big user of Jupyter notebooks, but version control issues put me off, and I've never got to grips customising the formatting of jupyter nbconvert. It's worth highlight…
This has been discussed before but I am watching the development of https://github.com/fonsp/Pluto.jl so that it can provide some solid alternative.
https://github.com/melling/ISLR/blob/main/chapter08/08_Lab02...
https://github.com/melling/ISLR/blob/main/chapter08/08_Lab02...
I need to figure out how to better fit images so I don’t have pages with large gaps
Also, you can now embed executable Python in the files.
This has been discussed before but I am watching the development of https://github.com/fonsp/Pluto.jl so that it can provide some solid alternative.
If you're interested in Pluto.jl, I recently saw an announcement about Neptune.jl[1], which appears to remove some of the reactive nature of Pluto. It's a fork of Pluto and executes code sequentially one cell at a time instead. An interesting read anyway and maybe worth trying. [1] https://github.com/compleathorseplayer/Neptune.jl