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 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      Next, security updates will now require browser engineers to pay attention to all the ways in which a specific bit of 3p code can be subverted and tend to updates accordingly...updates that can break users. This is a big tax.

      1 reply 0 retweets 10 likes
      Show this thread
    2. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      But the biggest reason we never did this with jQuery (and it likely holds for React) is that *not enough people use the same version*. There's a constituency that looks like "all jQuery developers", but when you look at it closely, it's a small, narrow per-version constituency.

      2 replies 0 retweets 20 likes
      Show this thread
    3. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      ...which gets to our interest. The benefit to browsers from integration is potential for efficiency; less code on the wire. Current JS ecosystem practice (which @seldo's product has done more than any other to exacerbate) is to externalize costs onto users at runtime.

      1 reply 0 retweets 24 likes
      Show this thread
    4. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      That's not great for the ecosystem we tend, particularly at the low end (where most users but few developers are). So we'd need to be pretty convinced that we were picking the "right version" to pre-integrate. Thus far, there isn't strong reason to believe such a thing exists.

      1 reply 0 retweets 9 likes
      Show this thread
    5. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      As for bringing up the platform to meet libraries (#2), we've been hard at work on this! Modern, responsible frameworks have taken advantage of the work I and my team ("Parkour") did from '10-'15, removing polyfills and bloat in favour of modern ES and DOM. It's great!

      1 reply 0 retweets 17 likes
      Show this thread
    6. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      ...but React isn't on this list today, at least not as practiced by the tools their team recommends developers start with (Next being the best of the bunch): https://reactjs.org/docs/create-a-new-react-app.html … It's a bloody shame.

      2 replies 0 retweets 12 likes
      Show this thread
    7. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      React itself contains a ton of platform-level duplication, e.g. the events system:https://github.com/facebook/react/tree/master/packages/react-dom/src/events …

      1 reply 1 retweet 18 likes
      Show this thread
    8. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      ...which is in addition to a great deal of over-polyfilling by default in most of the available toolchains. If you pave a cowpath but nobody uses the road, which lesson should one take from the effort?

      1 reply 1 retweet 12 likes
      Show this thread
    9. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      Regardless, there are hardy folks on our team collaborating to add things that the React team says they want but which we don't expose, e.g. @shubhie's work on scheduling. Because we serve more than one framework (because option #1 isn't "The Plan"), this needs to be generic.

      1 reply 0 retweets 5 likes
      Show this thread
    10. Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      Capabilities we've added over the years live under identical constraints: - must be backwards compatible with existing syntax and semantics - must be usable by any/all developers in granular, layered ways (see: https://extensiblewebmanifesto.org ) - must serve more than one customer

      1 reply 2 retweets 16 likes
      Show this thread
      Alex Russell‏ @slightlylate 2 Jun 2019
      • Report Tweet
      • Report NetzDG Violation

      This, plus standards, makes "just putting something in the browser" much, much, much harder than it looks from the outside (unless you go with #1, which we don't for the previously discussed reasons). We pay a heavy tax for fairness. Is that the right thing to do? Usually, yes.

      5:53 PM - 2 Jun 2019
      • 16 Likes
      • Jean-Francois Hector (((Benny Powers))) 🇮🇱🇨🇦 Mu-An 慕安 Jacob Matthews lastmjs.eth 🕸 Saulius Kerusauskas Prabhdeep Singh 🇨🇦 Michael Prentice pixellipsis
      1 reply 0 retweets 16 likes
        1. New conversation
        2. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          ...which brings us to #3: starting from the syntax angle. This is where React is *least* able to be integrated. React-flavoured JSX (which is what most people mean by "React") is unlikely to be workable as an addition to the platform w/o major changes.

          1 reply 0 retweets 10 likes
          Show this thread
        3. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          JSX is neither HTML nor modern-JS supersetting, meaning you'll need new grammar and parsers. It may not even ben context free. A variant might work, but it *will not* be JSX compatible w/o developers changing their code. ...and if you have to change syntax, why not Lit (e.g.)?

          2 replies 2 retweets 14 likes
          Show this thread
        4. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          ...and all of that is before we bring in the question of data structures and "diffing". Turns out diffing is slow! Other frameworks are going faster (Svelte, Lit, Vue, etc.) by taking different approaches, but they get similar surface syntax and they are *much* smaller.

          2 replies 1 retweet 25 likes
          Show this thread
        5. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          Put yourself in the browser engineer's shoes: you tend a platform that's 20+ years old and which you compete tooth-and-nail on performance about. Someone pitches to you a plan that is slower than other known alternatives and not strict super/sub-setting. Hrm.

          1 reply 1 retweet 22 likes
          Show this thread
        6. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          This practice of zooming out ever-so-slightly explains most of the difference in platform vs. app developer behavior in my experience. Platform developers are like Ents; they have responsibility over long time-periods for the things app developers take for granted.

          5 replies 8 retweets 61 likes
          Show this thread
        7. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          App developers take it for granted that the language doesn't break whenever new browsers are released, that new features are iterative, that things get faster year-on-year without them needing to re-compile their code.

          1 reply 2 retweets 20 likes
          Show this thread
        8. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          Platform developers, meanwhile, have incentive to look at the totality of the web rather than the shouty, shiny bits. You know who's a *much* bigger community than React developers? WordPress-ecosystem web developers. What they need matters more, if we're being fair.

          5 replies 11 retweets 59 likes
          Show this thread
        9. Alex Russell‏ @slightlylate 2 Jun 2019
          • Report Tweet
          • Report NetzDG Violation

          But we listen regardless, and try to balance needs across these differently-geared timescales and balance them with the relatively limited resources available to each individual browser team. We'll keep doing that, no matter what names @seldo calls us.

          4 replies 0 retweets 26 likes
          Show this thread
        10. 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