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. Jake Archibald‏ @jaffathecake 19 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rektide @thecraigmichael and

      That thread seems to be based on the assumption that "smoosh" was a serious proposal.

      1 reply 0 retweets 3 likes
    2. Alex Russell‏ @slightlylate 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jaffathecake @rektide and

      I should know better than to weigh in here, but a few things: - browsers have a responsibility towards their users and competitive pressure to render as much content as possible - browser teams fund most JS engine development - change sometimes involves breaking *some* things

      1 reply 0 retweets 4 likes
    3. Alex Russell‏ @slightlylate 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @jaffathecake and

      But being a responsible steward means understandng the scale and scope of impact of proposed changes -- if only as a proxy to the likely costs you're externalizing. Hence guidance like this: https://www.chromium.org/blink/removing-features …

      2 replies 0 retweets 9 likes
    4. rektide de la fay‏ @rektide 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @jaffathecake and

      In most situations I deeply appreciate the "dont break the web" sensibility, & these guidelines are great. But the way it is being used today feels like it is being used to trample those who feel MooTools 1.2 broke JS the language with it's slipshod monkeypatching of core JS.

      1 reply 0 retweets 0 likes
    5. rektide de la fay‏ @rektide 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rektide @slightlylate and

      The unwillingness of "dont break the web" advocates to acknowledge or recognize these pleas- that this is a very different case than usual- feels so wounding & aggravating. * MooTools 1.2 broke JS * Anyone monkeying /w the primitives of JS objects accepts a higher responsibility

      1 reply 0 retweets 0 likes
    6. Jake Archibald‏ @jaffathecake 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @rektide @slightlylate and

      From the article: In retrospect MooTools did the wrong thing — but breaking the web doesn’t punish them, it punishes users. These users do not know what a moo tool is. Alternatively, we can find another solution, and users can continue to use the web. The choice is easy to make.

      2 replies 0 retweets 5 likes
    7. craig martin‏ @thecraigmichael 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @jaffathecake @rektide and

      craig martin Retweeted z̢͠a̡ļg͡o͏ b̷e̛҉çk̕͞ơ͢nş̛͞

      Are we calling this wrong now? Could we (developers) have a contract governing how the language will evolve, rather than hoping our (private node or small website) code usage is incidentally used in some profiled package and, so only then, finally Safe.https://twitter.com/bterlson/status/973218284081315840 …

      craig martin added,

      z̢͠a̡ļg͡o͏ b̷e̛҉çk̕͞ơ͢nş̛͞ @bterlson
      Replying to @thecraigmichael
      You seem to be trying to draw a line between good usage of the language and bad usage of the language? Seems very arbitrary to me. How about: it's all usage and well try not to break your code unless we have to?
      2 replies 1 retweet 0 likes
    8. Alex Russell‏ @slightlylate 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @thecraigmichael @jaffathecake and

      The MooTools team was warned *at the time* that built-in monkeypatching was a baaaaaaad idea. There was no surprise here, only the passage of time.

      1 reply 0 retweets 4 likes
    9. Jake Archibald‏ @jaffathecake 20 Mar 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @thecraigmichael and

      Agreed. The expectation MooTools had from their for-in loop was incorrect. It was buggy code. Given that, and the mess we're in now, I don't think there's any doubt that MooTools did the wrong thing with that piece of code.

      0 replies 0 retweets 1 like
    10. This Tweet is unavailable.
      Alex Russell‏ @slightlylate 21 Mar 2018
      • Report Tweet
      • Report NetzDG Violation

      We didn't in Dojo. Nor did Closure. Nor did Glow. Etc. Etc.

      5:59 AM - 21 Mar 2018
      0 replies 0 retweets 0 likes

      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