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. getify‏ @getify 5 May 2019
      • Report Tweet
      • Report NetzDG Violation

      wondering aloud... perhaps we need something like WASM, but for HTML... in other words, a way for a server to ship pre-compiled DOM (not an html string) directly to the layout engine, bypassing the HTML parser -- same way WASM bypasses the JS parser with pre-compiled byte code.

      21 replies 24 retweets 165 likes
      Show this thread
    2. Saam Barati‏ @saambarati 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @getify @rwaldron

      Wasm doesn’t parse faster than JS IIRC

      1 reply 0 retweets 1 like
    3. Rick Waldron‏ @rwaldron 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @saambarati @getify

      Sure, but Kyle wants to circumvent parse altogether

      1 reply 0 retweets 2 likes
    4. getify‏ @getify 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rwaldron @saambarati

      specifically, I musing about circumventing stupid wasted work where SSR builds a DOM in memory on the server, serializes that DOM back down to a string of HTML (costly), transfers the string of HTML over the wire, then has to re-parse that string of HTML back into the same DOM.

      2 replies 0 retweets 1 like
    5. getify‏ @getify 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @getify @rwaldron @saambarati

      also... whether WASM "is faster" than JS is less the point and more that WASM was, in fact, despite some attempts (like this one) to re-author history, sold as cutting out a lot of "JS parse overhead", such as this post.pic.twitter.com/VnRLgXIFQi

      1 reply 0 retweets 1 like
    6. getify‏ @getify 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @getify @rwaldron @saambarati

      It's both amusing and frustrating that some people seem to think that we can't remember from just 2-3 years ago that this -- cutting down/out JS parse times -- was absolutely one of the main selling points for WASM. Just google search to find dozens/hundreds of such mentions.

      4 replies 0 retweets 3 likes
      Mathias Bynens‏Verified account @mathias 5 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @getify @rwaldron @saambarati

      I’m not sure why history is even relevant. You’re musing about a new feature to avoid JS parse cost. Multiple implementers are telling you that in 2019, this is not the dominating cost anymore. Parse cost is just not a problem in need of a solution.

      1:11 PM - 5 May 2019
      • 6 Likes
      • Tomasz Wegrzanowski Saam Barati Steven Myers Matthew Phillips hazin Robin Drexler
      2 replies 0 retweets 6 likes
        1. New conversation
        2. Rick Waldron‏ @rwaldron 5 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @getify @saambarati

          Are you still talking about HTML? Kyle's original post was about avoiding parse of "giant string of HTML". Don't get stuck on parsing JS, that was a side note

          1 reply 0 retweets 1 like
        3. Mathias Bynens‏Verified account @mathias 5 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @rwaldron @getify @saambarati

          Mathias Bynens Retweeted getify

          That’s not what https://twitter.com/getify/status/1125124825905807360 … says 🤷🏼‍♂️

          Mathias Bynens added,

          getify @getify
          Replying to @getify @rwaldron @saambarati
          also... whether WASM "is faster" than JS is less the point and more that WASM was, in fact, despite some attempts (like this one) to re-author history, sold as cutting out a lot of "JS parse overhead", such as this post. pic.twitter.com/VnRLgXIFQi
          2 replies 0 retweets 0 likes
        4. 2 more replies
        1. New conversation
        2. getify‏ @getify 5 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @rwaldron @saambarati

          I am NOT contemplating anything about JS parse time. I used that historical fact as an illustration of similar motivation that could support an entirely different thing (shipping already-build DOM). And I only mentioned cutting HTML parse time as part of the motiviation.

          1 reply 0 retweets 1 like
        3. getify‏ @getify 5 May 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @getify @mathias and

          the main motivation for my idea was in the next tweet, which was about avoiding the silly extra cost of SSR serializing DOM down to HTML only to have the browser re-parse it back to the same DOM on the other side.

          1 reply 0 retweets 2 likes
        4. 5 more replies

      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