3 ms·

I'm glad PDF.js' development continues. I completely missed that they have abandoned the plan to move to PDFium (https://wiki.mozilla.org/Mortar_Project https:/

• zinekeller 5y ago
  Mozilla developers at the time actually have other plans with the Pepper plugin support: Adobe Flash (since that Chrome's Pepper Plugin API (PPAPI) is actually miles better and secure than the Netscape [-era - ed.] Plugin API or NPAPI). They abandoned Mortar when Adobe have announced that it will retire Flash. (Also, PDF.js is now a misnomer: it now mainly uses WebAssembly.)
  • muizelaar 5y ago
    It doesn't. -------------------------------------------------------------------------------- Language Files Lines Blank Comment Code -------------------------------------------------------------------------------- JavaScript 355 144428 13069 16759 114600 JSON 12 24385 2 0 24383 CSS 12 3302 407 183 2712 HTML 32 1638 176 230 1232 Markdown 19 733 221 0 512 TypeScript 1 20 4 2 14 CoffeeScript 1 15 2 0 13 YAML 1 4 0 1 3 -------------------------------------------------------------------------------- Total 433 174525 13881 17175 143469 --------------------------------------------------------------------------------
    • zinekeller 5y ago
      I'm referring to the one built-into Firefox, not the HTML version. Even comparing the HTML one, this is misleading: the PDF.js compilation step means that there are WebAssembly code written nominally in JavaScript, namely those that handles font rendering and complex graphics (before pushing into the canvas, which by necessity is done in JS).
      • glandium 5y ago
        There is no wasm in the version built-into Firefox.
    • twodave 5y ago
      I think it's funny that someone added 1 CoffeeScript file to the codebase and didn't write a single comment about it.