Comment by fullstop
3 days ago
My daughter has a chromebook for school. As a device, it's actually pretty nice and the administration aspects of it are fantastic. It can be wiped and re-imaged easily, her "files" are all stored on the network, and it's snappy. Except for PDF viewing.
When it comes to PDFs, it sometimes really struggles. I think that the device can handle them, but I'm pretty sure that the PDFs themselves are often a collection of scanned images and not text. Once she has more than a few tabs open, it takes longer and longer to switch between them and she ends up using a desktop to complete her work.
In this case, the school provides the tools for her to do her assignments but we have the means to provide better ones at home and not every child will have this advantage.
Personally, I can read data sheets all day on a monitor but I absolutely can not do the same with fiction. I either need a paper book or a Kindle, and I don't know why that is. Perhaps it's because I am looking ahead and not down?
Even on slow devices the only problem I have had with PDFs has been when they are rendered using the JS renderer.
The developer of pdf.js replied to my comments on performance somewhere once, and I think it might have been HN, but was quite happy to acknowledge (IIRC) that its not a high performance solution.
I'll have to look at it the next time she complains. It may very well be pdf.js.