4 ms·
I tried loading that and it worked pretty well for me. Not fully native speed, but just a couple seconds to draw complex pages. Certainly not a "throw the compu
by TwoBit 12y ago
I tried loading that and it worked pretty well for me. Not fully native speed, but just a couple seconds to draw complex pages. Certainly not a "throw the computer out the window" experience.
- acqq 12y agoIt's really minutes to see all the drawings, i7, Win 8.1, FF 29 (to compare the CPU speeds, jslinux boots in 7.9 secs on my computer). Adobe Reader is immediate to see all the 20 pages. Have you tried to see all the pages, all the drawings? How many minutes you needed, on which setup? Are you using Firefox? Does it use pdf.js? Is it something OS dependent, or you just didn't look at all the pages? Now I see, Gracana mentions manuals on AutomationDirect.com. Look at this one for example: http://www.automationdirect.com/static/specs/dl0506select.pdf http://www.automationdirect.com/static/specs/dl0506select.pd...
- Dylan16807 12y agoI'm on firefox nightly, using pdf.js, windows. The first pdf takes about 4-5 seconds to render a page, and it always does the page I have onscreen so it doesn't matter how many pages there are.
- acqq 12y agoWhen measure only the first page you will completely miss a lot of problematic PDFs.
- Dylan16807 12y agoI looked at all the pages, picking them at random. It always did the one I had onscreen in seconds.
- vanderZwan 12y agoSo about two or three orders of magnitude slower than native.
- Dylan16807 12y agoApples and oranges. This is a young implementation and nothing considers its performance when generating a PDF. Until it's had significant optimization you can't draw very good conclusions about html+js vs. native.
- keehun 12y agoThis is wrong because PDF.js is Firefox's default way of presenting PDFs. If it's a young unoptimized code base, then maybe Firefox shouldn't make it the default. It is Apples to Apples comparison here because it's the default and how young it may be is irrelevant to the user experience.
- acqq 12y agoIt's a very dangerous attitude "I don't read PDF's and I don't care but the customers who read them should tolerate our young poor implementation that needs more than two minutes for just 15 pages." (The documents like this http://www.automationdirect.com/static/specs/dl0506select.pdf http://www.automationdirect.com/static/specs/dl0506select.pd... ) They won't. As soon as you prevent them doing their job (and it's so if they used their PDF's normally before you changed the defaults) they will have to search for the solution. The solution is either switch the handler (still a little better for browser writers) or the browser. By making the opening and looking at the 15-page PDF which was before instantaneous taking two minutes, you prevent them doing their job (the slowdown from subjectively 0 seconds to minutes is also subjectively infinitely worse experience!) and they must respond. They can't open just the first page. They actually care. They need all the pages.
- Dylan16807 12y agoWhy do you keep acting like a document cannot be interacted with until every single page is fully rendered? Especially when it goes out of order to get the onscreen pages ready first.