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
stjepang's profile
Stjepan Glavina
Stjepan Glavina
Stjepan Glavina
@stjepang

Tweets

Stjepan Glavina

@stjepang

async runtimes and concurrency primitives in @rustlang he/they (available for hire)

Berlin, Germany
stjepang.github.io
Joined October 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. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      After demonstrating how to build block_on() and an executor, the intention was then to explain work stealing, an async mutex and channel, timers, a reactor, and finally a complete runtime... 2/12

      1 reply 1 retweet 14 likes
      Show this thread
    2. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      However, while researching how to teach those topics in an approachable manner, I kept reducing the complexity of async Rust until all that remained is something so simple I never thought was even possible... 3/12

      1 reply 1 retweet 14 likes
      Show this thread
    3. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Imagine if the entirety of async-std, tokio, and mio fit into 1K lines of 100% safe code, with the same number of features and same performance! Here's why this is so important: 4/12

      2 replies 1 retweet 30 likes
      Show this thread
    4. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      When runtimes are so simple, the ability to build a best-in-class one is then not in the hands of a few concurrency experts anymore, but rather in everyone's hands. 5/12

      2 replies 0 retweets 17 likes
      Show this thread
    5. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Furthermore, less complexity means fewer bugs, API easier to learn, and code that is easier to maintain and extend. 6/12

      1 reply 1 retweet 14 likes
      Show this thread
    6. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Safe code inspires confidence. No need to anxiously test runtimes with thread sanitizer, miri, or loom. No need to even use those tools because safe code is immune to the kinds of bugs they catch! 7/12

      1 reply 1 retweet 13 likes
      Show this thread
    7. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Don't worry about tunables because you can tune everything in a custom runtime. 8/12

      1 reply 1 retweet 12 likes
      Show this thread
    8. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Because there is freedom to tune all the moving parts, you should be able outperform all other runtimes by yourself! 9/12

      1 reply 1 retweet 14 likes
      Show this thread
    9. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      If you look at how big the presently popular runtimes are, I want to reduce the complexity 10-20x in terms of lines of code and the size of API. 10/12

      1 reply 1 retweet 12 likes
      Show this thread
    10. Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      I'm also excited to see more people building more async runtimes in Rust! I really think so far we've only been scratching the surface and there is so much yet to explore. 11/12

      1 reply 1 retweet 16 likes
      Show this thread
      Stjepan Glavina‏ @stjepang Feb 28
      • Report Tweet
      • Report NetzDG Violation

      Curious to hear thoughts and happy to answer questions! 12/12

      11:16 AM - 28 Feb 2020
      • 1 Retweet
      • 12 Likes
      • Stephen Belanger #![feature(🦄)] #![allow(🌈)] Pratyush Mishra ʟʟoɢiq Rhaladriel Jonathan Frank serzhiio | capitalist Aaron Turon miss rabbits
      4 replies 1 retweet 12 likes
        1. New conversation
        2. CryZe‏ @CryZe107 Feb 28
          • Report Tweet
          • Report NetzDG Violation
          Replying to @stjepang

          That sounds great, but we definitely need to make sure that libraries can easily support all these various custom runtimes. At the moment there's too many different types between the different runtimes, so most libraries just get forked entirely instead.

          1 reply 0 retweets 0 likes
        3. Stjepan Glavina‏ @stjepang Feb 28
          • Report Tweet
          • Report NetzDG Violation
          Replying to @CryZe107

          I agree this is a real problem, but I also think it's not as big as is commonly believed. The solution is to use types from the futures crate instead, and when tempted to use types from a runtime, try to push that use onto the user of your library instead.

          1 reply 0 retweets 2 likes
        4. 5 more replies
        1. New conversation
        2. ragona‏ @ryanragona Feb 28
          • Report Tweet
          • Report NetzDG Violation
          Replying to @stjepang

          Sounds neat, where can we read the code?

          1 reply 0 retweets 0 likes
        3. Stjepan Glavina‏ @stjepang Feb 28
          • Report Tweet
          • Report NetzDG Violation
          Replying to @ryanragona

          I will be gathering feedback over the next week or two and publish after that.

          1 reply 0 retweets 4 likes
        4. 1 more reply
        1. New conversation
        2. ʟʟoɢiq‏ @llogiq Feb 28
          • Report Tweet
          • Report NetzDG Violation
          Replying to @stjepang

          If this works out, it would be a real game changer. Providing best-in-class perf tailored to the use case with a modest amount of safe code *and* ability to change runtimes from under user code to match changing perf tradeoffs would cement #RustLang's place as premier async lang.

          1 reply 0 retweets 6 likes
        3. ʟʟoɢiq‏ @llogiq Feb 29
          • Report Tweet
          • Report NetzDG Violation
          Replying to @llogiq @stjepang

          With that said, this will require even better compiler UX (vulgo: error messages) to make sense of the generics soup. 🎶Toss a coin to your @ekuber, o valley of plenty...🎶

          0 replies 0 retweets 1 like
        4. End of conversation
        1. Ted Mielczarek‏ @TedMielczarek Feb 29
          • Report Tweet
          • Report NetzDG Violation
          Replying to @stjepang

          Super excited to read this! I've been reading through your blog posts trying to digest them with an eye towards building a custom executor for our codebase at work. We had @Argorak in to give a training and while chatting with him he suggested this might be the best way to go.

          0 replies 0 retweets 2 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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