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. James Long‏ @jlongster 29 Aug 2017
      Replying to @slightlylate @wycats and

      Totally agree about this. Some bad stuff you can get into, and we should make JS-powered sites more bulletproof by default.

      1 reply 0 retweets 1 like
    2. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @jlongster @wycats and

      Honestly, I'd love to see "SSR"d sites simply not ship JS on first load and only pull in JS when served from SW.

      3 replies 0 retweets 5 likes
    3. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @slightlylate @jlongster and

      That'd make the TTFB hit you usually pay for "SSR" more reasonable and prevent invisible breakage.

      1 reply 0 retweets 0 likes
    4. Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
      Replying to @slightlylate @jlongster and

      What's the problem with background loading JS? Why does it affect TTFB?

      1 reply 0 retweets 1 like
    5. Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
      Replying to @wycats @slightlylate and

      Honestly, nobody should use SSR if it makes TTFI worse. TTFB also shouldn't be worse but if worse TTFB improves TTFI, seems ok?

      1 reply 1 retweet 0 likes
    6. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @wycats @jlongster and

      Most SSR solutions I've traced do not flush() early, delaying delivery of markup to request critical resources; critical path pushed out.

      2 replies 0 retweets 1 like
    7. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @slightlylate @wycats and

      This seems particularly framework-centric. Excited to see streaming pulled into this discussion to avoid the TTFB delays.

      2 replies 0 retweets 1 like
    8. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @slightlylate @wycats and

      The approach that I've seen that works around this isn't much better: statically SSRing an "entrypoint", rehydrating full app for content

      1 reply 0 retweets 0 likes
    9. Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
      Replying to @slightlylate @jlongster and

      Hm that doesn't seem like a useful SSR solution. The point of user facing SSR is to get them Googlable content fast.

      1 reply 0 retweets 1 like
    10. Alex Russell‏ @slightlylate 29 Aug 2017
      Replying to @wycats @jlongster and

      Googlebot runs JS; so that works fine. Anyway, we agree that SSR should not delay TTFB = )

      3 replies 0 retweets 1 like
      Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
      Replying to @slightlylate @jlongster and

      Fine bingable. Also Googlebot runs some godawful old version of chrome that nobody wants to target (yay evergreen!)

      10:09 AM - 29 Aug 2017
      • 2 Likes
      • busticated Alex Russell
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Alex Russell‏ @slightlylate 29 Aug 2017
          Replying to @wycats @jlongster and

          today it's Cr41.

          1 reply 0 retweets 0 likes
        3. Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
          Replying to @slightlylate @jlongster and

          Godawful old version. Where's the @slightlylate that bet his career on evergreen ;)

          1 reply 0 retweets 1 like
        4. Sebastian Markbåge‏ @sebmarkbage 29 Aug 2017
          Replying to @wycats @slightlylate and

          We recently had to revert a polyfill clean up and delay release b/c of it. I don't want to make it a broader argument than that it matters.

          1 reply 0 retweets 3 likes
        5. Yehuda Katz  🥨‏Verified account @wycats 29 Aug 2017
          Replying to @sebmarkbage @slightlylate and

          I'm hopeful Google will get on a more evergreen path for Googlebot.

          0 replies 0 retweets 2 likes
        6. End of conversation

      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