Let's try it with individual info pages that are included

1 files changed, 23 insertions, 0 deletions

diff --git a/2020/info/12.md b/2020/info/12.md
new file mode 100644
index 00000000..71de0c05
--- /dev/null
+++ b/2020/info/12.md
@@ -0,0 +1,23 @@
+Many discussions have been had over the years on the debate between
+using few big files versus many small files.  However, more often than
+not, those discussions devolve in a collection of anecdotes with
+barely any science to them.
+
+Once and for all (or, at least until org-element.el get overhauled), I
+would like to settle the debate by explaining why the way we parse
+Org-mode files becomes slower as our files grow in size or numbers,
+and how that affects their browsing and the building of custom-agenda
+views.
+
+I feel qualified to talk about this topic for two reasons:
+
+-   I went through the trouble of optimising my agenda-views by
+    implementing clever regex-based skips, so I know the ceiling that
+    can be reached with the current tech.
+-   My work on Org-roam has led me to consider the use of an external
+    parser for Org-mode files, and whilst we are only at the prototyping
+    stage, we know what is at stake.
+
+I intend the talk to be fairly light-hearted and humorous, which is the
+only way we can do true justice to the topic.
+