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
slightlylate's profile
Alex Russell
Alex Russell
Alex Russell
@slightlylate

Tweets

Alex Russell

@slightlylate

Chrome Project 🐡 & Web Standards TL; Blink API OWNER Named PWAs w/ @phae; probably making her ☕ DMs open. Tweets my own; press@google.com for official comms.

San Francisco, The Internet
infrequently.org
Joined December 2010

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. xnoɹǝʃ uɐıɹq‏ @brianleroux 28 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      xnoɹǝʃ uɐıɹq Retweeted Gary Bernhardt

      This is because of async/await and promise. Not a new problem (over five years old from my vantage) and entirely avoidable if you write Node as it was written instead of piling on browser framework 'best practice'.https://twitter.com/garybernhardt/status/1101202093715517441 …

      xnoɹǝʃ uɐıɹq added,

      Gary Bernhardt @garybernhardt
      I frequently see Node generate errors where the traceback doesn't contain any lines of code that I wrote, so I can't tell what I did that caused the error. Is this the state of the art in Node: not knowing where errors came from? What if it happens in production?
      Show this thread
      7 replies 2 retweets 12 likes
    2. Rick Waldron‏ @rwaldron 28 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @brianleroux

      ❤️pic.twitter.com/zwORak0HCZ

      1 reply 0 retweets 6 likes
    3. xnoɹǝʃ uɐıɹq‏ @brianleroux 28 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rwaldron

      Sorry forgot my taking points! all the work tc39 has done is flawlessly executed and any critical ideas are only reflects on my amateur / ignorant perspective

      1 reply 0 retweets 1 like
    4. Rick Waldron‏ @rwaldron 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @brianleroux

      Dude... chill out, I wasn't even thinking about anything TC39 related. I just thought you jumped to a conclusion pretty quickly. I've experienced what Gary described, but in completely different, non-async circumstances :P

      1 reply 0 retweets 4 likes
    5. xnoɹǝʃ uɐıɹq‏ @brianleroux 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rwaldron

      Apologies. This one isn't new to me but alt ways of it happening are. What other circumstances cause error swallowing? (It's the only place I've experienced it amd I have no doubt it happens a lot more the dialects/ecosystem Gary is working in.)

      2 replies 0 retweets 1 like
    6. Mikeal Rogers‏ @mikeal 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @brianleroux @rwaldron

      Anytime you throw away the stack or have a handler on something that gets spit out of the platform. So: callbacks, promises, and regular old event handlers, all have this. At least with async/await we have long tracebacks as a potential solution.

      2 replies 0 retweets 3 likes
    7. Mikeal Rogers‏ @mikeal 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mikeal @brianleroux @rwaldron

      We actually tried to implement long tracebacks in Node.js for callbacks back in the 0.2 days. Ryan had a branch with a working prototype, but it was plagued with edge cases and perf issues :(

      1 reply 0 retweets 2 likes
    8. xnoɹǝʃ uɐıɹq‏ @brianleroux 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mikeal @rwaldron

      We should probably not be recommending stuff until the "amazing feature X that fixes everything" actually ships eh.. just a thought.

      1 reply 0 retweets 2 likes
    9. Mikeal Rogers‏ @mikeal 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @brianleroux @rwaldron

      Again, this is the exact same problem callbacks have, except with async/await error propogation is a bit more sane (cause it's mostly language level). The thing that confuses all this was the Promise API error propogation when chaining, which is legit awful. Worst ever.

      2 replies 0 retweets 4 likes
      Alex Russell‏ @slightlylate 1 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mikeal @brianleroux @rwaldron

      So long as all your promises are native (not library) promises, devtools should be able to catch most of the error chains. Goal for Promises async/await was to create a global contract that tools could tier-up understanding of. Happening, albeit unevenly (better in browser).

      7:14 AM - 1 Mar 2019
      • 3 Likes
      • Irvan Putra Domenic Denicola Aaron Boodman
      1 reply 0 retweets 3 likes
        1. New conversation
        2. xnoɹǝʃ uɐıɹq‏ @brianleroux 1 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @mikeal @rwaldron

          Didn't sound like Gary was doing anything approaching browser dev. But then again..I am clearly not in the majority of thinking on how that is best done these days! 😬

          1 reply 0 retweets 1 like
        3. BrendanEich‏Verified account @BrendanEich 1 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @brianleroux @slightlylate and

          BrendanEich Retweeted Gary Bernhardt

          ICYMI,https://twitter.com/garybernhardt/status/1101330412196966400?s=21 …

          BrendanEich added,

          Gary Bernhardt @garybernhardt
          This seems to be going much better since I turned on tslint's promise-function-async and no-floating-promises rules.
          Show this thread
          1 reply 0 retweets 2 likes
        4. 4 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