Nick just brought up the topic of adding a second compact string representation to the JS engine (motivated by string memory use). One question was whether to use ASCII (which V8 does, iirc) or UTF8. Several DOM people have pointed out over the years that if SM would accept UTF8 it'd be really good for Gecko, so I was leaning toward UTF8 but hoping for some measurement of how much it'd win over ASCII to back this up. Sounds like UTF8 would serve Servo well too.
Another question is how much of the total win would result from adding the ability to parse UTF8 directly (technically, the JSAPI accepts utf8 chars, but they are immediately inflated) vs. JS strings passed in/out through JSAPI. ----- Original Message ----- > On Tue, Apr 1, 2014 at 3:18 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > > > On 4/1/14 3:07 PM, Keegan McAllister wrote: > > > >> Who should I talk to about JS string representation changes? > >> > > > > Eddy Bruel. ejpbruel at mozilla dot com. > > > If we could get the JS engine to use evil-UTF8 with some hack to handle > charAt and friends efficiently (e.g. tacking on a UCS-2 version of the > string when necessary), then we could use evil-UTF8 exclusively in Servo > and that would be awesome. > > Rob > -- > Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni > le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa > stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, > 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp > waanndt wyeonut thoo mken.o w > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
