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. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @MylesBorins

      We don't have a few years. We already spent them on killing Imports in favor of the never-ending Modules tease...and now appetite to finish the job re: fetch options looks weak. What cause for optimism is there?

      1 reply 0 retweets 0 likes
    2. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @MylesBorins

      It seems more responsible to both users, the community, and to the teams involved to re-build Imports on top of Web Packages and let JS catch up whenever the committee realizes the world changed around it.

      1 reply 0 retweets 0 likes
    3. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @MylesBorins

      That path decouples progress from TC39 (a perenially winning move, in my experience) but leaves a path for eventual convergence. Why wait? Why bet on JS-first here when it has failed so massively to date?

      1 reply 0 retweets 0 likes
    4. lukejacksonn‏ @lukejacksonn 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @MylesBorins

      Out of interest, what necessary components need working on to make "let's bet the farm on modules" story plausible?

      1 reply 0 retweets 0 likes
    5. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @lukejacksonn @MylesBorins

      Right now, we need a syntax for fetch options in module requests (particularly destination type, but also CORS, etc.). Had hoped to avoid, but looks necessary.

      1 reply 0 retweets 0 likes
    6. sMyle‏Verified account @MylesBorins 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @lukejacksonn

      Seems like good use cases for modules attribute proposal

      1 reply 0 retweets 0 likes
    7. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @MylesBorins @lukejacksonn

      Yep. What's the prognosis? Does committee grok it already burned through runway and is late to deliver?

      1 reply 0 retweets 0 likes
    8. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @MylesBorins @lukejacksonn

      But let's say it works out...what's the case that we will not just continue to pile more transpilation on? What evidence shows meanings reductions in it vs. now fast-moving 90% browser-reach baseline?

      1 reply 0 retweets 0 likes
    9. Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @MylesBorins @lukejacksonn

      I want to believe. I have spent a decade mining this vein...but community doesn't want to hear we can't afford profligate ways, and node/server/cli tools are only insulating devs from costs today (not minimizing and/or providing visibility). What drives change in that behaviour?

      1 reply 0 retweets 0 likes
    10. sMyle‏Verified account @MylesBorins 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @lukejacksonn

      This feels like the begining of "a new hope" 🤣🤣🤣🤣

      2 replies 0 retweets 2 likes
      Alex Russell‏ @slightlylate 11 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @MylesBorins @lukejacksonn

      I'm working on prods to change client dynamics (https://github.com/slightlyoff/never_slow_mode/blob/master/README.md …), but continuing to pitch "it'll be the same on the server and client" has been a massive loser. How do we enforce this sort of discipline server-side?

      7:27 AM - 11 Dec 2019
      • 1 Like
      • Karl Horky
      1 reply 0 retweets 1 like
        1. New conversation
        2. Alex Russell‏ @slightlylate 11 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @MylesBorins @lukejacksonn

          If the answer is "we'll move most of our heavy workload to the server and treat client as a scarce resource, but with more shared platform underpinnings", I'd buy it. But "universal" is a comforting lie so long as resource costs diverge wildly for client and server.

          1 reply 0 retweets 0 likes
        3. Alex Russell‏ @slightlylate 11 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @MylesBorins @lukejacksonn

          More to the point: if we're doing futurism that doesn't mention (nevermind solve) the existential perf crisis that a decade of JS-first has wrought, we're talking about a future that is smaller, serves fewer people, and retreats into gated communities of network and CPU wealth.

          0 replies 0 retweets 1 like
        4. 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

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