From 6738dce6a99f3863b5257e08a1af997349eb134d Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Thu, 22 Oct 2020 00:49:30 -0400 Subject: First try at schedule --- 2020/schedule/12.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 2020/schedule/12.md (limited to '2020/schedule/12.md') diff --git a/2020/schedule/12.md b/2020/schedule/12.md new file mode 100644 index 00000000..3a5bca3a --- /dev/null +++ b/2020/schedule/12.md @@ -0,0 +1,35 @@ +# One Big-ass Org File or multiple tiny ones? Finally, the End of the debate! +Saturday, Nov 28 2020, 1:52 PM - 2:02 PM +Leo Vivier + +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. + + + + +Back to the [[schedule]] + +All times are approximate, and we might shuffle talks around as needed. Please check https://emacsconf.org/2020 a few days before the start of the conference for instructions on how to watch and participate. + +[[!meta title="One Big-ass Org File or multiple tiny ones? Finally, the End of the debate!"]] -- cgit v1.2.3