Re: DOMString UTF-16 from Tab Atkins Jr. on 2014-01-16 (www-dom@w3.org from January to March 2014)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 16 Jan 2014 14:16:14 -0800
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Graham Houston <housty.g@gmail.com>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <CAAWBYDBmh31wX8L3AaNzBZ99qrNQ7FhhvuoiiDgYP=Q2nA5Oxg@mail.gmail.com>

On Thu, Jan 16, 2014 at 12:08 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> There are, as an aside, various ways to use UTF-8
> internally while exposing UTF-16-like behavior externally without notab-
> ly affecting performance. It is entirely possible some of the major web
> browsers will do that at some point.

Blink does, for example - it'll store strings internally as 8-bit
ASCII when it can.

~TJ

Received on Thursday, 16 January 2014 22:17:01 UTC