Skip to content
  • Home Home Home, current page.
  • Moments Moments Moments, current page.

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
propensive's profile
Jon Pretty
Jon Pretty
Jon Pretty
@propensive

Tweets

Jon Pretty

@propensive

Supporting Scala through professional training and open-source software. Responsible for Magnolia, Fury, Scala World and Functional Africa.

Europe
propensive.com
Joined July 2010

Tweets

  • © 2021 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. Dale Wijnand‏ @dwijnand 11 Feb 2020

      Dale Wijnand Retweeted Frank Thomas

      Controversial opinion: what a waste of attention. We should have a declared range of versions (we attest) our libraries support, and separately a freeze file for reproducible test running (and other code executions, like runMain, console, what have you).https://twitter.com/fst9000/status/1227149976196845569 …

      Dale Wijnand added,

      Frank Thomas @fst9000
      This was a little bit over a year ago. @ScalaSteward has now created over 45k PRs of which 30k have been merged and it is watching nearly 1000 repos. At this pace, there will be over 100 000 merged PRs at the end of the year. 😱 https://twitter.com/fst9000/status/1081268315731963906 …
      10 replies 2 retweets 14 likes
      Show this thread
    2. Jon Pretty‏ @propensive 12 Feb 2020
      Replying to @dwijnand

      It's a huge waste of attention, but orders of magnitude less than the waste of attention that would have been spent making those PRs manually. Though we shouldn't be deluded that the problem is now "fixed".

      5 replies 0 retweets 8 likes
    3. Daniel Spiewak‏ @djspiewak 12 Feb 2020
      Replying to @propensive @dwijnand

      Every solution to this problem boils down to one of those two. A non-persistent DAG, by definition, violates reproducibility in some form (note that freeze files simply choose a middle ground between the two extremes). A persistent DAG will be noisy without atomic updates.

      1 reply 0 retweets 1 like
      Jon Pretty‏ @propensive 12 Feb 2020
      Replying to @djspiewak @dwijnand

      I think there's a good compromise though: We can have builds which are immutable and repeatable, but where nonbreaking changes can be introduced trivially with the user's intervention, and larger changes less trivially (but, as necessary). (Full explanation won't fit in a tweet.)

      9:30 AM - 12 Feb 2020
      2 replies 0 retweets 0 likes
        1. New conversation
        1. Jon Pretty‏ @propensive 12 Feb 2020
          Replying to @propensive @djspiewak @dwijnand

          I'm also against the idea of build files living in git repositories. It means you can't update the build (e.g with new dependencies) without changing the repo.

          2 replies 0 retweets 0 likes
        2. Jon Pretty‏ @propensive 12 Feb 2020
          Replying to @propensive @djspiewak @dwijnand

          Instead, I want a file in the repo which points to the repeatable build which was known to work for that version of the code, but which can be trivially updated to the latest version published post-hoc which claims to be backwards compatible with that version.

          1 reply 0 retweets 0 likes
        3. Show replies
        2. New conversation
        1. Daniel Spiewak‏ @djspiewak 12 Feb 2020
          Replying to @propensive @dwijnand

          The "introduce non-breaking changes trivially with user intervention" bit is where I think the innovation can happen over the current state of affairs. Steward + Mergify is kind of a crude way of trying to get this, but it can be made much much smarter.

          1 reply 0 retweets 1 like
        2. Dale Wijnand‏ @dwijnand 12 Feb 2020
          Replying to @djspiewak @propensive

          What kind of things are you thinking?

          4 replies 0 retweets 0 likes
        3. Show 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

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