On Oct 6, 2014, at 9:00 AM, Simon Sapin <simon.sa...@exyr.org> wrote:
>> For me, absent evidence, it's much easier to believe that using WTF-8 >> instead of potentially ill-formed UTF-16 would be a win for the JS >> engine than to believe that using WTF-8 instead of UTF-8 in the DOM >> would be a win. > > So you’re suggesting Servo could get away with UTF-8 in the DOM? I hadn’t > considered it. I remove my proposal at the start of this thread, I’d like us > to try this instead. UTF-8 strings will mean that we will have to copy all non-7-bit ASCII strings between the DOM and JS. This is an increase in memory usage over all existing engines, so why would we want to do this in Servo? That seems difficult to swallow, especially since the only way to remove the copies is to make SpiderMonkey handle something like WTF-8 natively. >From the discussion in the other part of the thread, it sounds like it should >be possible to avoid copies if we used a split UTF-16 / Latin1 representation >like SpiderMonkey. Cameron _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
