Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
mathias's profile
Mathias Bynens
Mathias Bynens
Mathias Bynens
Verified account
@mathias

Tweets

Mathias BynensVerified account

@mathias

I work on @ChromeDevTools & @v8js at Google and on ECMAScript through TC39. ♥ JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.

Munich, Germany
mths.be
Joined January 2007

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Jake Archibald‏ @jaffathecake May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @DasSurma @rem

      Yeah, bytes -> JS string -> bytes is a lossy process

      1 reply 0 retweets 2 likes
    2. Surma‏ @DasSurma May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jaffathecake @rem

      Wait, is it? I was trying to claim the opposite 🤔 You can store any byte sequence in a JS string because they are unsanitized UTF-16. So invalid byte sequences will continue to sit there. But once you pipe it through TextEncoder/Decoder, you loose data.

      2 replies 0 retweets 0 likes
    3. Ingvar Stepanyan‏ @RReverser May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @DasSurma @jaffathecake @rem

      UTF-16 can't be unsanitized. JavaScript strings use UCS-2, which is "unsanitized" version of UTF-16, but technically a different encoding which is why actual UTF-16 is lossy in Text{Encoder,Decoder}.

      1 reply 1 retweet 2 likes
    4. Surma‏ @DasSurma May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RReverser @jaffathecake @rem

      That’s why I said “unsanitized UTF-16” (I wasn’t sure if UCS-2 is exactly that or not). I guess I’m trying to distinguish between build a JS string from bytes using String.fromCharCode et al and using TextEncoder (which doesn’t support UTF-16, interestingly enough)

      2 replies 0 retweets 0 likes
    5. Ingvar Stepanyan‏ @RReverser May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @DasSurma @jaffathecake @rem

      Heh yeah the problem is that Web specs (including Text*coder) can't deal with invalid Unicode in any encoding, while JS spec can.

      1 reply 0 retweets 0 likes
    6. Ingvar Stepanyan‏ @RReverser May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RReverser @DasSurma and

      I'm still strongly convinced that TextEncoder should at least have `fatal` option (see discussion at https://github.com/whatwg/encoding/issues/174#issuecomment-478959889 …) to make it easy to catch these mismatches, but not everyone agrees :(

      1 reply 0 retweets 0 likes
    7. Anne van Kesteren‏ @annevk May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RReverser @DasSurma and

      I was wondering today if @mathias’s String.wellFormed idea (though perhaps on the prototype?) could go through TC39. (Still not convinced to special case some APIs taking USVString over others.)

      1 reply 0 retweets 1 like
    8. Darien MV‏ @bhathos May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @annevk @RReverser and

      Is the proposed idea about something beyond str => !/[uD800-UDFFF]/u.test(str) ?

      1 reply 0 retweets 0 likes
    9. Darien MV‏ @bhathos May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @bhathos @annevk and

      (missing backslash typo, twitter is maybe not the best coding env)

      1 reply 0 retweets 0 likes
    10. Anne van Kesteren‏ @annevk May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @bhathos @RReverser and

      It’s slightly more complicated (see the @encodings issue for @mathias’s take) as surrogate pairs are fine.

      2 replies 0 retweets 0 likes
      Mathias Bynens‏Verified account @mathias May 5
      • Report Tweet
      • Report NetzDG Violation
      Replying to @annevk @bhathos and

      Actually, that regular expression makes use of the `u` flag to correctly match only lone surrogates. The way to do it without `u` is using lookbehind assertions.

      1:18 PM - 5 May 2020
      • 3 Likes
      • Surma Wellington Torrejais da Silva (em 🏡) Darien MV
      1 reply 0 retweets 3 likes
        1. New conversation
        2. Anne van Kesteren‏ @annevk May 5
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @bhathos and

          But now I have two problems!

          1 reply 0 retweets 3 likes
        3. Ingvar Stepanyan‏ @RReverser May 5
          • Report Tweet
          • Report NetzDG Violation
          Replying to @annevk @mathias and

          That's alright, you can make a combined regular expression to match both your problems.

          1 reply 0 retweets 1 like
        4. 1 more reply

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info