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. Alex Russell‏ @slightlylate 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation

      Alex Russell Retweeted Chrome Developers

      This whole series is brilliant; ICYMI, here are parts 1, 2, and 3 as well: https://developers.google.com/web/updates/2018/09/inside-browser-part1 … https://developers.google.com/web/updates/2018/09/inside-browser-part2 … https://developers.google.com/web/updates/2018/09/inside-browser-part3 …https://twitter.com/ChromiumDev/status/1043149029755035650 …

      Alex Russell added,

      Hand drawn title card: Part 4 Input is coming to the compositor
      Chrome DevelopersVerified account @ChromiumDev
      💁‍♀️ ...and because rendering and input goes hand in hand 🤲how does browser archives smooth scrolling? 📐Meet compositor! I guarantee you it'll be your best friend for fast site performance💯 📚Part 4(the last one!): Input is coming to the Compositor https://developers.google.com/web/updates/2018/09/inside-browser-part4 … pic.twitter.com/B8j82wV67w
      Show this thread
      1 reply 46 retweets 185 likes
    2. Patrick Walton‏ @pcwalton 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate

      Too Chrome-specific. Firefox is moving away from the paint/compositor distinction—WebRender is already turned on in nightly for many users.

      1 reply 1 retweet 17 likes
    3. Alex Russell‏ @slightlylate 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton

      This architecture currently renders most web pages for most users across all form-factors, so it hopefully is relevant to web developers. Our compositor has changed a lot (and continues to). All of this will be out of date at some point...but so what?

      1 reply 0 retweets 4 likes
    4. Yehuda Katz  🥨‏Verified account @wycats 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @pcwalton

      Chrome is not the same thing as the web. Chrome is not the same thing as the web.

      2 replies 4 retweets 27 likes
    5. Alex Russell‏ @slightlylate 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wycats @pcwalton

      The architecture described here is ~roughly replicated in nearly all shipping browsers. FF, Edge, Safari, and Chrome all use variations on it -- the primary difference being the process host of the "compositor". Did you have substantive feedback?

      1 reply 0 retweets 1 like
    6. Alex Russell‏ @slightlylate 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @wycats @pcwalton

      But even if we scope the discussion to Chrome (which the post does), is there something bad or wrong in describing the layers that affect developers but appear to be "magic"?

      2 replies 0 retweets 1 like
    7. Alex Russell‏ @slightlylate 21 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @wycats @pcwalton

      We're all constrained by the same specs when it comes to input handling and the relationship to scrolling. You can quibble with terminology, but the described cause/effect are true globally (unless an engine breaks compat)

      1 reply 0 retweets 1 like
      Patrick Walton‏ @pcwalton 22 Sep 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @wycats

      One of the main ideas behind WebRender is the developers shouldn’t have to care about which CSS objects get layers—it’s our job as browser developers to make it fast, period.

      8:14 AM - 22 Sep 2018 from Dogpatch, San Francisco
      • 2 Likes
      • Ferdy James Willcox
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Mariko Kosaka‏ @kosamari 22 Sep 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @slightlylate @wycats

          Hi friends, just the point on "this is about Chrome" It kinda is. This every 1st sentence of this series should say that. So people know which one they are looking at (part3 don't atm and that's my over sight, fixing that).pic.twitter.com/3lqlFATcZO

          screen grab from article highlighted "this is the last of the 4 part bog series looking inside of Chrome"
          1 reply 0 retweets 6 likes
        3. Mariko Kosaka‏ @kosamari 22 Sep 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @kosamari @pcwalton and

          ...but I came to similar conclusion as Alex that post is roughly applicable to many web browsers in use. Thus title has "modern browser" not Chrome. I mean, I omitted a lot of what Chrome does (like slimming paint https://www.chromium.org/blink/slimming-paint …) & generalized it 🤷‍♀️

          1 reply 0 retweets 2 likes
        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