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.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • 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
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

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. Ivo Georgiev‏ @Ivshti 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ianfoo @pcwalton and

      I agree, but we're yet to see a constructive and concrete example of when try reduces Go's readbility characteristics

      1 reply 0 retweets 0 likes
    2. ✕✕✕✕✕‏ @peterbourgon 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Ivshti @ianfoo and

      literally any example where try is used more than once per line. or when try and if err are mixed in the same function. if you don’t think that’s less readable then 🤷‍♀️ but it’s pretty clearly so to a lot of us. go isn’t rust, what works in one doesn’t necessarily translate

      1 reply 0 retweets 2 likes
    3. Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @peterbourgon @Ivshti and

      There is absolutely nothing wrong with using try more than once per line, or mixing try and if err. Nobody has ever had trouble understanding Rust code that used the equivalents to those features. And yes, our experiences do translate. Why wouldn’t they?

      1 reply 0 retweets 0 likes
    4. ✕✕✕✕✕‏ @peterbourgon 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @Ivshti and

      Go programmers expect and value that escape analysis is trivial: scan for the return keyword. Other conventions of the language reinforce that: early returns and happy path indent alignment. Languages aren’t interchangeable. Expectations and idioms differ.

      1 reply 0 retweets 1 like
    5. Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @peterbourgon @Ivshti and

      Same in Rust, before we added ?. Rust users “expected and valued” that returns could be visible by just seeing “return” or “try”. We saw people swear up and down that the language would be ruined when we added ?. Now everyone loves the feature.

      1 reply 0 retweets 1 like
    6. Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @peterbourgon and

      Like I said, I’ve seen all this before.

      1 reply 0 retweets 1 like
    7. ✕✕✕✕✕‏ @peterbourgon 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @Ivshti and

      I do t know how else to tell you that you can’t just take a conclusion from one context/dataset and insist it applies equally to another 🤷‍♂️

      1 reply 0 retweets 1 like
    8. Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @peterbourgon @Ivshti and

      Because nobody has given me a reason why the experiences should be different. All I’ve heard is that Go users care about readability more than Rust users, which is silly.

      1 reply 0 retweets 1 like
    9. ian molee‏ @ianfoo 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @peterbourgon and

      It's clear enough to me that Go and Rust are solving different problems, just based on the language design/complexity/features themselves. This draws different user bases that place different priority on different things. I don't think it can be dismissed as easily as you think.

      1 reply 0 retweets 0 likes
    10. Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @ianfoo @peterbourgon and

      Read pretty much any RFC thread. Rust users care tremendously about readability.

      1 reply 0 retweets 1 like
      Patrick Walton‏ @pcwalton 8 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @ianfoo and

      I think some Gophers’ idea of Rust users as people who don’t care about readability to the same degree is a stereotype, nothing more.

      11:25 AM - 8 Jul 2019
      • 1 Like
      • Random Firefox User
      1 reply 0 retweets 1 like
        1. New conversation
        2. ✕✕✕✕✕‏ @peterbourgon 8 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @ianfoo and

          This is your strawman, not anything anyone has expressed. Readability means different things in different contexts. And it’s pretty unarguable that most Go is easier to grok than most Rust.

          1 reply 0 retweets 2 likes
        3. Michael Aaron Murphy‏ @mmstick 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @peterbourgon @pcwalton and

          I know both Go and Rust. I find it much easier to write readable Rust than Go. Readability means the same thing in every context: how easy it is to understand the code being read. Due to Go's lack of expressiveness, and excessive need for boilerplate, intent is often unclear.

          1 reply 0 retweets 2 likes
        4. 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

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