Why did Google not write their PDF Reader for Chrome in Javascript?
Google normally fully embraces web technologies. It is a bit of surprise then that the PDF viewing functionality in Chrome is implemented as a plugin rather than being written in Javascript.
Any ideas why they have taken this route?
(
7 comments
| 8 points
| on HN
)
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.
Google are exceptionally good at identifying problems that matter. They invest heavily in the stuff that yields the greatest results. When there are still so many glaring problems in web browsing, implementing a PDF engine from scratch is wasted effort.