3 ms·
> PDF.js is slow, buggy, and can’t edit documents. That is leagues ahead of native PDF plugins which are slow, buggy, full of vulnerabilities, closed source, r
by scrollaway 9y ago
> PDF.js is slow, buggy, and can’t edit documents.
That is leagues ahead of native PDF plugins which are slow, buggy, full of vulnerabilities, closed source, require a deprecated plugin infrastructure and usually can't edit documents either.
PDF.js is one of the better things to come out of Mozilla.
- throwaway2048 9y agoPDF.js has had a huge amount of its own vulnerabilities.
- superkuh 9y agoOkay. But the solution is to not involve the browser at all. It's there to browse. Once you find and download the file have it open in a real application designed for reading pdf.
- geraltofrivia 9y agoIdeally, yeah. But often PDFs are integrated with the web experience as another web page. Or atleast that's how I treat them. I have 2-5 research papers open in my tabs at all times, and I browse through them like I would with any other article. Sure if it piques my interest I would download it, organize it but I wouldn't go through the pains of doing that for every pdf I lay my eyes upon.
- superkuh 9y ago>download it, organize it but I wouldn't go through the pains of doing that for every pdf I lay my eyes upon. You don't have to do that. Just set your browser to open the file in a real application. It'll automagically download to some temp dir (ie, /tmp) and you won't have to care about file paths or organization at all (unless you want to). I have tens of research papers open in my tabs at all times. But for a good experience reading I open the full text in my pdf reader.