4 ms·
My guess is: 1) Speed. JS may be too slow to quickly parse such a complicated file format. Remember that may PDFs may be very large in size 2) Complexity. Thi
by zzleeper 15y ago
My guess is:
1) Speed. JS may be too slow to quickly parse such a complicated file format. Remember that may PDFs may be very large in size
2) Complexity. This is the big one. PDFs are full of quirks that make html pale. Thus, it was smarter to just use Foxit's already tested codebase than start from zero.
- hoodoof 15y agoFirefox is bulding their PDF reader functionality using Javascript. I would have thought that Google would have the technical chops to do it without it being too slow.
- melling 15y agoWhich one is faster? One of the goals of Chrome is to run on older hardware. Also, if you're sticking with XP for a while longer, you'll need to move to Firefox or Chrome, if you want a modern browser. The fastest browser for all those legacy XP machines is Chrome.