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.
  • 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
wycats's profile
Yehuda Katz 🥨
Yehuda Katz 🥨
Yehuda Katz  🥨
Verified account
@wycats

Tweets

Yehuda Katz  🥨Verified account

@wycats

Tilde Co-Founder, OSS enthusiast and world traveler.

Portland, OR
yehudakatz.com
Joined August 2007

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • 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. Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
      Replying to @dan_abramov @jlongster

      It's nicer to pull values when you need them than to reduce eagerly into one value, I think.

      2 replies 0 retweets 2 likes
    2. James Long‏ @jlongster 19 Oct 2017
      Replying to @wycats @dan_abramov

      At this point I think the most important thing is consistency: however you do it all of the app works that way (mixing them = worst of both)

      1 reply 0 retweets 1 like
    3. Adam Rackis‏ @AdamRackis 19 Oct 2017
      Replying to @jlongster @wycats @dan_abramov

      Wait I thought cWRP *just* to help interop w/ 3rd party, non-react utilities? Isn't manually updating state from props in cWRP anti-pattern?

      2 replies 0 retweets 0 likes
    4. James Long‏ @jlongster 19 Oct 2017
      Replying to @AdamRackis @wycats @dan_abramov

      I don't think so. If you use `setState`, that depends on props, you have to. Forbidding that makes apps even uglier imho

      1 reply 0 retweets 1 like
    5. Dan Abramov‏ @dan_abramov 19 Oct 2017
      Replying to @jlongster @AdamRackis @wycats

      Updating state based on props (not very common but happens) is the only supported use case for cWRP

      1 reply 0 retweets 9 likes
    6. Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
      Replying to @dan_abramov @jlongster @AdamRackis

      But shouldn't that state be derived and pulled in render()?

      2 replies 0 retweets 2 likes
    7. Adam Rackis‏ @AdamRackis 19 Oct 2017
      Replying to @wycats @dan_abramov @jlongster

      Right - not very common, like he said :)

      1 reply 0 retweets 0 likes
    8. Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
      Replying to @AdamRackis @dan_abramov @jlongster

      But then you don't need the hook at all

      1 reply 0 retweets 0 likes
    9. James Long‏ @jlongster 19 Oct 2017
      Replying to @wycats @AdamRackis @dan_abramov

      It's useful, rarely, when processing the props is CPU-intensive. Can happen in certain situations

      1 reply 0 retweets 2 likes
    10. Brandon Dail‏ @aweary 19 Oct 2017
      Replying to @jlongster @wycats and

      You also have access to both current *and* next props in cWRP, which you don't have in render.

      1 reply 0 retweets 2 likes
      Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
      Replying to @aweary @jlongster and

      You do if you stash them. Better to do that when you need it then make the framework snapshot them always, I think.

      2:20 PM - 19 Oct 2017
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Brandon Dail‏ @aweary 19 Oct 2017
          Replying to @wycats @jlongster and

          I don't think it makes forces the framework to snapshot them, it's just a lifecycle that's called at the right moment when both exist

          1 reply 0 retweets 0 likes
        3. Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
          Replying to @aweary @jlongster and

          Depends on the architecture, but Glimmer can avoid work in the general case if we don't have to unconditionally pass the old snapshot.

          1 reply 0 retweets 1 like
        4. Adam Rackis‏ @AdamRackis 19 Oct 2017
          Replying to @wycats @aweary and

          I mean, if the component doesn't actually implement the hook the framework doesn't have to do anything, right?

          1 reply 0 retweets 0 likes
        5. Adam Rackis‏ @AdamRackis 19 Oct 2017
          Replying to @AdamRackis @wycats and

          And that of course assumes @aweary is wrong, which I don't think he is - prolly just a method the fw calls with values it already has.

          2 replies 0 retweets 0 likes
        6. Brandon Dail‏ @aweary 19 Oct 2017
          Replying to @AdamRackis @wycats and

          I think that the old props (internally, memoizedProps) would exist at the point cWRP is called regardless due abortable work in Fiber

          2 replies 0 retweets 1 like
        7. Yehuda Katz  🥨‏Verified account @wycats 19 Oct 2017
          Replying to @aweary @AdamRackis and

          I think that's probably true, but it's not inherent. "I have this state lying around" is a good way to lock into hard-to-optz APIs.

          1 reply 0 retweets 1 like
        8. Brandon Dail‏ @aweary 19 Oct 2017
          Replying to @wycats @AdamRackis and

          Agreed, but backwards compat was a goal for 16 w/ Fiber so it was already ~locked in, maybe that could change if a better API is proposed

          1 reply 0 retweets 0 likes
        9. 14 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

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