
1. Installing Slidev, and the 554 MB Download That Waits Until Your First Export
Slidev installed in 59 seconds and redraws a slide in a median of 175 ms. Then the first PDF export asked for 554 MB of Chromium and five and a half more minutes.
Tag
14 pieces

Slidev installed in 59 seconds and redraws a slide in a median of 175 ms. Then the first PDF export asked for 554 MB of Chromium and five and a half more minutes.

We built a 9 slide talk from a real article: line by line code highlights, Mermaid, a photo and speaker notes, exported to 550 KB in 6.21 seconds. Three of our four deliberate mistakes still exited 0.

We built our Slidev talk into a 6.7 MB site in 1.95 seconds, then found the default build lets anyone read the speaker notes at /presenter/. We also exported without the 554 MB Chromium download.

Hugo installed in 7.86 seconds and rebuilt our site in 4 ms. Its first build also wrote zero HTML files and reported success, and that was the first of four silent failures.

We moved our own 128 published articles into Hugo and got clean builds in under 100 ms. The obvious route also rewrote code blocks in 8 of them, turning shell comments into headings, and exited 0.

Our 50,000 page Hugo build took 86 seconds until we moved one where filter into a cached partial, and then it took 16. We also fed it bad input on purpose: five of eight mistakes built with exit 0.

Hugo built our 10,000 article site in 2.45 seconds to Eleventy's 4.8 and won at every size we tried. It also used nearly twice the memory, and 17 of its last 42 releases flagged something breaking, deprecated or removed.

Typst installed in 2.20 seconds and compiled its first PDF in 90 milliseconds. Then we typed a Markdown heading into it and watched the whole thing fall over.

We pulled 8 repositories from the GitHub REST API into a CSV and had Typst typeset a table and a bar chart from it in 0.20 seconds. Two things broke on the way, and one of them took the longest to diagnose.