For context, this article has probably been posted as it is linked to by the "Astra for Coding: Why Are We Doing This Again?" blog post [1] currently being discussed [2].
I also dislike the title ("What we learned when a user tried to load a massive GML file in a browser") - it's hard to imagine that someone who had tried to build a viewer for geospatial data would not already know the answer (paraphrasing, "tiling the data will be necessary to achieve acceptable performance, and there are standard methods to do this")
This one's website (and a dead comment replying to you) suggests that processing the PDF in the browser, rather than uploading to a server, is a point of differentiation.
However, there are older tools that do this, such as BentoPDF (which is also open source) [1].
I was about to link to the same "What's on the Menu" site, which I remembered being an impressive site for library digitization project years ago, but it was apparently retired in January 2025.
Now [1] redirects to [2], essentially an About page with links to the data.
To be fair we were done transcribing and double verifying in about 2015. We’d get a batch of new menus from the imaging team, tweet it and no matter the size it’d be gone in about an hour.
One later variant is the Valiant Roamer https://www.computinghistory.org.uk/det/30545/Valiant-Roamer...
reply