diff --git a/README.md b/README.md
index 510aa3ff9b801864a6eb84f85cfd9c8972d50f93..8de9428910e672a71bc3892f64495b8caf97009b 100644
--- a/README.md
+++ b/README.md
@@ -50,7 +50,7 @@ Programming:
     - End-to-end encryption
     - Your own ideas...
 
-See [2]-[6] for more practical information.
+See [2]-[7] for more practical information.
 
 ## Skills
 
@@ -77,6 +77,7 @@ During the project group, you will learn and apply the following skills:
 - [4] Google. The Raster Tragedy in Skia (blog post). https://skia.org/docs/dev/design/raster_tragedy/
 - [5] Nicolas Silva. List of vector graphics rendering approaches: https://github.com/nical/lyon/wiki/Related-projects
 - [6] Beat Stamm. The Raster Tragedy at Low-Resolution Revisited: Opportunities and Challenges beyond “Delta-Hinting”. http://rastertragedy.com/
+- [7] Stylus Labs. https://github.com/styluslabs/nanovgXC (rendering framework of the https://www.styluslabs.com/ software)
 
 
 
diff --git a/talk/chromevsinkscape.png b/talk/chromevsinkscape.png
new file mode 100644
index 0000000000000000000000000000000000000000..7407725151f0acff019c995edc2cfe3a689e9d70
Binary files /dev/null and b/talk/chromevsinkscape.png differ
diff --git a/talk/talk.tex b/talk/talk.tex
index 28f0071cc42ee13e71d61678a8fd06fadfa4537f..4115e17b195c4c10bfb3821ffb6aa27d13612a10 100644
--- a/talk/talk.tex
+++ b/talk/talk.tex
@@ -71,10 +71,19 @@
   \onslide<+->{\emph{Ok, so how can we build a better app?}}
   \begin{itemize}[<+->]
     \item Need to render vector graphics
-    \item Chrome uses skia, so let's try that...
+    \item Chrome uses Skia, so let's try that...
   \end{itemize}
-  
+\end{frame}
+
+\begin{frame}
+  \frametitle{Stroke rendering is hard}
+
+  \url{https://issues.skia.org/issues/40043907}: Filled paths of width less than 1px defeat GPU anti-aliasing\\[5mm]
 
+  \onslide<2->{
+  Chrome vs. Inkscape:
+  \includegraphics[width=\linewidth]{chromevsinkscape.png}
+  }
 
 \end{frame}