<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webr on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/webr/</link>
    <description>Recent content in Webr on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 16 Mar 2023 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/webr/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Playgrounds with WebR and Quarto</title>
      <link>https://www.rostrum.blog/2023/03/16/webr-quarto/</link>
      <pubDate>Thu, 16 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2023/03/16/webr-quarto/</guid>
      <description>tl;dr WebR lets you run R in the browser(!). Now you can make WebR chunks in Quarto that render to editable, executable blocks(!).
 Sliding into tedium I wrote recently a simple introduction to how R parses code. I provided a function that I said the reader could go away and run themselves.
As in… copy-paste it into an instance of R running on their machine. Gross.
Wouldn’t it be better if people could just tinker with the code right there in the post?</description>
    </item>
    
  </channel>
</rss>