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
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

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. gankra's gay‏ @Gankra_ 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      noticing an interesting feedback loop in the web: all the major engines were built on software renderers, which leads to certain optimizations and perf characteristics, which leads to web pages which rely on that, which pushes web engines to need/want those opts, and so on

      2 replies 2 retweets 26 likes
      Show this thread
    2. gankra's gay‏ @Gankra_ 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      e.g. drawing things is so expensive that it's worth it to do lots of book-keeping to avoid drawing things twice. webdevs then see incredibly complex but static things are 'free'. now web engines *need* aggressive caching because tons of pages have super complex static elements

      1 reply 0 retweets 17 likes
      Show this thread
    3. gankra's gay‏ @Gankra_ 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation

      this feedback loop has been the biggest blow against the original "dream" of webrender, which was that *maybe* the win from gpu rendering was enough that you could just draw a page from scratch at 60fps without async scrolling, cached layers, invalidation, etc ya can't

      2 replies 0 retweets 10 likes
      Show this thread
    4. Patrick Walton‏ @pcwalton 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Gankra_

      The vast majority of pages do just fine with WebRender when repainting every frame. There are a bunch that don’t, but there are also a bunch that perform badly with the traditional stack.

      1 reply 0 retweets 2 likes
    5. gankra's gay‏ @Gankra_ 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton

      The percentages don't really matter; if important/major pages run fine in vanilla gecko but not webrender, but a bunch of oddball pages run great in webrender, I don't think that's a win (and I don't think we could politically sell shipping that either)

      2 replies 0 retweets 0 likes
    6. Patrick Walton‏ @pcwalton 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Gankra_

      I actually pretty much entirely disagree with your take—the biggest problem is that we don’t control the OS compositor, so we need invalidation and so forth in order to get good energy efficiency. We’ve already proven that you can get good FPS in the repaint-everything case.

      1 reply 0 retweets 0 likes
    7. gankra's gay‏ @Gankra_ 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton

      I am certain we haven't? Tons of cases where a page just slaps 5+ text-shadows on something and we fall over completely. *even* if we cache the blurs, just compositing them is too expensive. glenn is heads down working on picture caching because we have so many of these bugs!

      1 reply 0 retweets 0 likes
      Patrick Walton‏ @pcwalton 29 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Gankra_

      I knew you were going to bring up that case :) That is easy to fix: just cache the blurs together. Much easier than picture caching. The reason why we need picture caching, in my view, is energy efficiency, not to get 60 FPS.

      6:42 PM - 29 Oct 2018
      2 replies 0 retweets 0 likes
        1. New conversation
        2. gankra's gay‏ @Gankra_ 29 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          caching the blurs together *is* picture caching?

          1 reply 0 retweets 0 likes
        3. Patrick Walton‏ @pcwalton 29 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @Gankra_

          Picture caching is a lot more than just text shadows. That’s why it’s been so much work to implement.

          2 replies 0 retweets 0 likes
        4. 6 more replies
        1. Patrick Walton‏ @pcwalton 29 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton

          Traditional layerization heuristics have the exact same problem, by the way. That is why browsers have this delicate balancing act to avoid creating too many layers.

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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