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.

    Yehuda Katz  🥨‏Verified account @wycats Mar 20

    I wrote up some thoughts on the proposal to replace the current Stage 3 class proposals with a clean slate design: https://gist.github.com/wycats/b1c96c67074396a239abd60f55087adc … Should be a major topic of this week's TC39 meeting. Very interested in feedback. Lots of links if you need context 😄

    12:50 AM - 20 Mar 2018
    • 38 Retweets
    • 122 Likes
    • Arindam Paul Brian Dordevic 📲📷📈 Maksim Kuklin defmyfunc Louis DeScioli Patrick A douxsey ba🇸🇳 Ankeet Maini Richard Su
    22 replies 38 retweets 122 likes
      1. New conversation
      2. register and vote!‏ @jacobrothstein Mar 20
        Replying to @wycats

        Clean slate looks significantly better on initial read. Did I miss mention of why `var ids = []` inside of class body wouldn't work in clean slate as initializers? Have there been any discussions of variable access of private state? (Like [] notation but for private state only)

        1 reply 0 retweets 2 likes
      3. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @jacobrothstein

        Clean slate rejects initializers (and therefore fields). I think I left links to the rationale; if not, follow to the repo and search the issue tracker.

        1 reply 0 retweets 1 like
      4. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @wycats @jacobrothstein

        What do you think about `var` as the way to declare private instance variables?

        5 replies 0 retweets 0 likes
      5. register and vote!‏ @jacobrothstein Mar 20
        Replying to @wycats

        It's less offensive than # on the surface, but I wonder if it might be confusing since it doesn't behave like folks have learned `var` does (access and assignment without `this->`). If `hidden concatIds(){}`, why not also `hidden ids;` for consistency?

        2 replies 0 retweets 2 likes
      6. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @jacobrothstein

        In principle they could both be "private", which I think would improve the proposal. Out of curiosity, why is @foo ok in Ruby but #foo not ok in JS? Is the # that much worse of a sigil?

        1 reply 0 retweets 2 likes
      7. register and vote!‏ @jacobrothstein Mar 20
        Replying to @wycats @foo

        I would object to `this.@foo` also. I think enough languages use # for comments that it doesn't read naturally. I imagine a language that used // as an operator would have the same trouble. But `this.#something` is the worst part for me

        1 reply 0 retweets 1 like
      8. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @jacobrothstein @foo

        Can you imagine getting used to it as analogous to leading `_`?

        1 reply 0 retweets 1 like
      9. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @wycats @jacobrothstein @foo

        Incidentally, when I originally worked on this proposal, I had a shorthand syntax like Ruby (`#foo`), and `x.#foo` is only needed for situations where you'd use instance_variable_get in Ruby (but only allowed in the class body that declared it)

        1 reply 0 retweets 0 likes
      10. 6 more replies
      1. New conversation
      2. marco sparagna‏ @thetallestuser Mar 20
        Replying to @wycats

        I think 'var' is very confusing there, also having a different way of handling instance variables (this->prop) is unnecessary. The hash for private fields is a bit 'ugly' (no code shaming) i wish it was an underscore.

        1 reply 0 retweets 6 likes
      3. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @thetallestuser

        Do you think you could get used to #? The problem with `_` is it's already valid in public properties.

        2 replies 0 retweets 1 like
      4. marco sparagna‏ @thetallestuser Mar 20
        Replying to @wycats

        Or a private keyword and no special syntax?

        1 reply 0 retweets 1 like
      5. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @thetallestuser

        https://github.com/tc39/proposal-class-fields/blob/master/PRIVATE_SYNTAX_FAQ.md#why-not-do-a-runtime-check-on-the-type-of-the-receiver-to-determine-whether-to-access-the-private-or-public-field-named-x … Read the whole thing :) @littledan and others did a great job writing this all down.

        1 reply 0 retweets 1 like
      6. marco sparagna‏ @thetallestuser Mar 20
        Replying to @wycats @littledan

        Hash it is!

        1 reply 0 retweets 0 likes
      7. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @thetallestuser @littledan

        Not to stir a hornet's nest, but it was almost `@` (from ruby and a little bit coffeescript), but decorators got there first in adoption in transpilers.

        1 reply 0 retweets 0 likes
      8. marco sparagna‏ @thetallestuser Mar 20
        Replying to @wycats @littledan

        I think @ is too confusing for private fields, it's kind of a standard to have `@decorator`. Same rationale behind the use of `var`. It's better to learn something new than giving new meanings to something old. And # is better than %

        1 reply 0 retweets 5 likes
      9. Yehuda Katz  🥨‏Verified account @wycats Mar 20
        Replying to @thetallestuser @littledan @Decorator

        Honestly, yep!

        0 replies 0 retweets 1 like
      10. End of conversation
      1. New conversation
      2. Ray Booysen‏ @raybooysen Mar 22
        Replying to @wycats @dan_abramov

        Out of interest, why is there seemingly so much resistance to keywords like private or public?

        2 replies 0 retweets 1 like
      3. Dan Abramov‏ @dan_abramov Mar 22
        Replying to @raybooysen @wycats

        Because they’re taken by TS

        6 replies 0 retweets 1 like
      4. Yehuda Katz  🥨‏Verified account @wycats Mar 22
        Replying to @dan_abramov @raybooysen

        I disagree strongly with this. If we tried, I think we could make it work. I plan to propose `private #foo` declarations at the next meeting :)

        1 reply 0 retweets 3 likes
      5. 1 more reply

    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