Re: Is there a pure JS implementation of the WOFF2 Brotli codec?

"Robert O'Callahan" <[email protected]> Wed, 15 Jul 2015 14:37:26 +1200
Newsgroups gmane.comp.web.fonts
Message-ID <CAOp6jLaboAQ7mrnz1kWr+VP5fyFrnAhR2iVXEgAyN0idF9Oywg@mail.gmail.com>
--001a1141cad6d9d8bf051ae0d5a1
Content-Type: text/plain; charset=UTF-8

On Wed, Jul 15, 2015 at 11:25 AM, Mike Kamermans <[email protected]> wrote:

> On the off-chance that anyone knows, fontkit (
> https://github.com/devongovett/fontkit) is currently using an
> emscripten'ed version of the Brotli codec for handling WOFF2 decoding,
> which turns what is a 34MB footprint process without WOFF2 decoding into a
> ~1000MB footprint process with... making it rather unusable for dealing
> with WOFF2 files in any meaningful production setting.
>

That overhead sounds way too high. I guess something is wrong with
emscripten or some other part of the workflow.

Rob
-- 
lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
toD
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
rdsme,aoreseoouoto
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
lurpr
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
esn

--001a1141cad6d9d8bf051ae0d5a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jul 15, 2015 at 11:25 AM, Mike Kamermans <span dir=
=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">nihongo=
@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>=
On the off-chance that anyone knows, fontkit (<a href=3D"https://github.com=
/devongovett/fontkit" target=3D"_blank">https://github.com/devongovett/font=
kit</a>) is currently using an emscripten&#39;ed version of the Brotli code=
c for handling WOFF2 decoding, which turns what is a 34MB footprint process=
 without WOFF2 decoding into a ~1000MB footprint process with... making it =
rather unusable for dealing with WOFF2 files in any meaningful production s=
etting.<br></div></div></div></blockquote><div><br></div><div>That overhead=
 sounds way too high. I guess something is wrong with emscripten or some ot=
her part of the workflow.<br></div></div><br clear=3D"all"></div><div class=
=3D"gmail_extra">Rob<br></div><div class=3D"gmail_extra">-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr">lbir ye,ea yer.tnietoehr=C2=A0 rdn rd=
sme,anea lurpr=C2=A0 edna e hnysnenh hhe uresyf toD<br>selthor=C2=A0 stor=
=C2=A0 edna=C2=A0 siewaoeodm=C2=A0 or v sstvr=C2=A0 esBa=C2=A0 kbvted,t rds=
me,aoreseoouoto<br>o l euetiuruewFa=C2=A0 kbn e hnystoivateweh uresyf tulsa=
 rehr=C2=A0 rdm=C2=A0 or rnea lurpr =C2=A0<br>.a war hsrer holsa rodvted,t=
=C2=A0 nenh hneireseoouot.tniesiewaoeivatewt sstvr=C2=A0 esn<br></div></div=
>
</div></div>

--001a1141cad6d9d8bf051ae0d5a1--