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. Allen Wirfs-Brock‏ @awbjs Apr 12

      I’m beginning to think that the best thing for the future of JavaScript would be for TC39 to go back to a 5-10 year release cycle.

      21 replies 61 retweets 202 likes
    2. 𝕓𝕠𝕠rian.d.mtsx‏ @bterlson Apr 12
      Replying to @awbjs

      I've felt at least some kind of choke point toward the latter stages would be helpful. A time where we can apply some amount of vision and executive control over mostly finished proposals (ensure they work great together, have cohesive semantics, etc).

      5 replies 0 retweets 20 likes
    3. 𝕓𝕠𝕠rian.d.mtsx‏ @bterlson Apr 12
      Replying to @bterlson @awbjs

      There exists a requirement to consider cross-cutting concerns, but the process could encode this more forcefully and ensure sufficient "bake" time is dedicated to uncovering and addressing these issues (even if no one knows of any issues prima facie).

      2 replies 0 retweets 6 likes
    4. Allen Wirfs-Brock‏ @awbjs Apr 12
      Replying to @bterlson

      Right, it takes more than considering cross-cutting concerns. A good language design is a carefully considered set of features selected to be useful and powerful in combination. You can’t get there one feature at a time.

      2 replies 2 retweets 14 likes
    5. 𝕓𝕠𝕠rian.d.mtsx‏ @bterlson Apr 12
      Replying to @awbjs

      How about: 1. Keep yearly releases. 2. Define "waves". Waves are created by committee consensus up-front, have defined vision and scope, and represent a group of mutually beneficial features. 3. Proposals need to be bug fixes, very minor features (lib only), or in a wave.

      3 replies 0 retweets 11 likes
    6. Allen Wirfs-Brock‏ @awbjs Apr 12
      Replying to @bterlson

      Yes, something like that. The upfront plan is very important. I suspect that most TC390 delegates haven’t seen the plan that ES6/Harmony operated under https://web.archive.org/web/20100701214135/http://wiki.ecmascript.org:80/doku.php?id=harmony:harmony …

      2 replies 1 retweet 4 likes
    7. Daniel Ehrenberg‏ @littledan Apr 12
      Replying to @awbjs @bterlson

      I've been so jealous of that plan as I've been working on class features. It'd be great to recuperate something like that. At the same time, I imagine we'll come up with the feature set differently this time, with input from a much broader group.

      2 replies 0 retweets 3 likes
    8. Yehuda Katz  🥨‏Verified account @wycats Apr 13
      Replying to @littledan @awbjs @bterlson

      It's important to remember there there were enough flaws in that plan that TC39 quickly accepted the staged proposal. That said, at the time, we expressed worry about cross-cutting concerns, and it's time we revisited that question.

      2 replies 0 retweets 1 like
    9. Sam Tobin-Hochstadt‏ @samth Apr 13
      Replying to @wycats @littledan and

      I haven't been around enough to have a strong sense, but maybe there's a need for some periods where the language moves in big ways, and other periods where change is more incremental. Big steps, then consolidation.

      1 reply 0 retweets 1 like
    10. Yehuda Katz  🥨‏Verified account @wycats Apr 13
      Replying to @samth @littledan and

      I think we also need a stronger sense that a feature might be good in isolation, but nonetheless not gonna make it right now. Increasingly, it feels like a very serious personal affront to object to an early stage feature.

      2 replies 0 retweets 2 likes
      Yehuda Katz  🥨‏Verified account @wycats Apr 13
      Replying to @wycats @samth and

      I personally try to push back against features I think are "good but not good right now" before Stage 2, and then focus on fine-tuning after Stage 2.

      9:25 AM - 13 Apr 2018
      • 2 Likes
      • Brenton Daniel Ehrenberg
      1 reply 0 retweets 2 likes
        1. New conversation
        2. Allen Wirfs-Brock‏ @awbjs Apr 13
          Replying to @wycats @samth and

          and not just “right now”. Not every good language features idea is necessarily a good fit to every language.

          1 reply 0 retweets 2 likes
        3. Yehuda Katz  🥨‏Verified account @wycats Apr 18
          Replying to @awbjs @samth and

          But you can't always tell whether a feature will never be a good fit for a language (many bets on that front have been wrong, such as Shared Array Buffer), so I try to focus on what I know now.

          1 reply 0 retweets 1 like
        4. Marco Rogers‏ @polotek Apr 18
          Replying to @wycats @awbjs and

          This conversation is weirdly abstract. Can someone talk about which recent language changes are causing concern and why?

          2 replies 0 retweets 3 likes
        5. Yehuda Katz  🥨‏Verified account @wycats Apr 18
          Replying to @polotek @awbjs and

          I think @awbjs has a problem with decorators, but I don't want to speak on his behalf.

          1 reply 0 retweets 0 likes
        6. Yehuda Katz  🥨‏Verified account @wycats Apr 18
          Replying to @wycats @polotek and

          More generally, there's a LOT of features in flight and people are getting pretty (legitimately) concerned about landing them so quickly that we don't have time to react to feedback: - class fields - private fields and methods - pipeline - null coalescing - safe navigation

          1 reply 0 retweets 1 like
        7. Yehuda Katz  🥨‏Verified account @wycats Apr 18
          Replying to @wycats @polotek and

          And that's not to mention other pretty meaty features that are pretty new, like Shared Array Buffer, async iterators, rest and spread properties, async function itself.

          1 reply 0 retweets 1 like
        8. Daniel Ehrenberg‏ @littledan Apr 18
          Replying to @wycats @polotek and

          It'd true that you can list the things TC39 has been working on and can be presented in an intimidating way. But I think what we've promoted to late stages fits together well and can be learned piece by piece over time.

          1 reply 0 retweets 2 likes
        9. Daniel Ehrenberg‏ @littledan Apr 18
          Replying to @littledan @wycats and

          For new proposals, I'm happy to see that many come with early implementations in transpilers and polyfills. I think we can spend time getting more feedback from the JS developer community on these to make sure we are not making a mistake.

          1 reply 0 retweets 1 like
        10. 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

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