[hatch_q]

I don't see it having any better performance than integrated chrome pdf viewer. Furthermore, with it using wasm i'd expected it to have custom renderer, but it's just pdf to html converter.

And loading times are quite bad (10 times slower - compared to firefox or chrome pdf viewers).

[keepamovin]

Loading the mupdf.js bundle is slow right now. When I checked it out it was super fast. Guess it's a server/ratelimit/caching issue with the HN hug being top of front page.

Which is what I guess you mean about 10x slower -- so you're making an unfair comparison as you're counting the network at peak, whereas browser plugins load from disk or memory.

But I actually thought the load of the PDF (once the app was loaded) was, for MuPDF.js, slightly faster than the browser plugin. When I watched it, tho I have not benched it. Do you have any benchmarks?

[SiempreViernes]

I downloaded this file https://indico.cta-observatory.org/event/5245/contributions/... and tried timing how long it took for the standard firefox vs this MuPDF viewer to render the first slide and there is like at least 3 second difference.

As others in the thread also report significant speed gains I think you either have some weird issue with your setup or how you measure performance.

[CryZe]

It uses a custom renderer, which seems to just blit its image data onto a canvas. The HTML is just there so you can actually select the text.

[dsp_person]

Does this generally satisfy accessibility needs too?