toad.social

WNB.rbMeet Harriet Oughton! Senior full stack developer at Zivio, Rails Foundation contractor, and the brilliant mind behind "Depeche Code" (developer rock band - how cool is that?!).On August 26th at Noon Eastern, Harriet will demystify Rails concurrency in a way that's actually understandable. No more wondering what's happening behind the Rails magic curtain!🔗 RSVP: <a href="https://discord.gg/ZuRU2WQG?event=1407366305480183830" rel="nofollow noopener" translate="no" target="_blank">https://discord.gg/ZuRU2WQG?event=1407366305480183830</a><a href="https://ruby.social/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener" target="_blank">#RubyOnRails</a> <a href="https://ruby.social/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> <a href="https://ruby.social/tags/WomenInTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#WomenInTech</a> <a href="https://ruby.social/tags/WNBrb" class="mention hashtag" rel="nofollow noopener" target="_blank">#WNBrb</a>

WNB.rb🚀 WNB.rb Meetup Alert! 🚀 Join us Tuesday, August 26th at Noon Eastern for "Spinning Multiple Plates: A Guide to Concurrency in Rails" with Harriet Oughton!Ever wondered how Rails keeps your app performant behind the scenes? Harriet will peel back the curtain on Rails magic and show us the threading and concurrency that powers it all.Senior developer at Zivio + Rails Foundation contractor🔗 Join us: <a href="https://discord.gg/ZuRU2WQG?event=1407366305480183830" rel="nofollow noopener" translate="no" target="_blank">https://discord.gg/ZuRU2WQG?event=1407366305480183830</a><a href="https://ruby.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ruby</a> <a href="https://ruby.social/tags/Rails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rails</a> <a href="https://ruby.social/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> <a href="https://ruby.social/tags/WomenInTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#WomenInTech</a> <a href="https://ruby.social/tags/NonbinaryInTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#NonbinaryInTech</a>

Eric Maugendre"Choreographic programming is a paradigm for concurrent and distributed software, whereby descriptions of the intended communications (choreographies) are automatically compiled into [decentralized code. It is difficult to combine w/higher-order functions]: compilation is not modular (editing a part might require recompiling everything) and the generated code can perform unexpected global synchronisations." <a href="https://portal.findresearcher.sdu.dk/en/publications/modular-compilation-for-higher-order-functional-choreographies" rel="nofollow noopener" translate="no" target="_blank">https://portal.findresearcher.sdu.dk/en/publications/modular-compilation-for-higher-order-functional-choreographies</a><a href="https://hachyderm.io/tags/computing" class="mention hashtag" rel="nofollow noopener" target="_blank">#computing</a> <a href="https://hachyderm.io/tags/compilation" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilation</a> <a href="https://hachyderm.io/tags/CS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CS</a> <a href="https://hachyderm.io/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://hachyderm.io/tags/distributed" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributed</a> <a href="https://hachyderm.io/tags/semantics" class="mention hashtag" rel="nofollow noopener" target="_blank">#semantics</a> <a href="https://hachyderm.io/tags/computerScience" class="mention hashtag" rel="nofollow noopener" target="_blank">#computerScience</a>

Interesting Links<a href="https://www.percona.com/blog/how-to-make-schema-changes/" rel="nofollow noopener" target="_blank">How To Make Schema Changes and Not Die Trying</a> "The most important things to consider while preparing a schema change." OK, I've got to admit I like the title.<a href="https://bookmarks.kvibber.com/tagged/MySQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#MySQL</a> <a href="https://bookmarks.kvibber.com/tagged/Percona" class="mention hashtag" rel="nofollow noopener" target="_blank">#Percona</a> <a href="https://bookmarks.kvibber.com/tagged/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://bookmarks.kvibber.com/tagged/database" class="mention hashtag" rel="nofollow noopener" target="_blank">#database</a> <a href="https://bookmarks.kvibber.com/tagged/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://bookmarks.kvibber.com/tagged/servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#servers</a>

Joe Seigh<a href="https://mastodon.social/@bruces" class="u-url mention" rel="nofollow noopener" target="_blank">@bruces</a> It's possibly the one thing, other than <a href="https://mastodon.social/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a>, that programmers are worse at. Even supposedly smart ones.

Jan :rust: :ferris:<a href="https://genomic.social/@kloetzl" class="u-url mention" rel="nofollow noopener" target="_blank">@kloetzl</a> You can use a concept called "Borrow Splitting" in combination with scoped threads.This way, your slices that your threads operate on, can have a lifetime shorter than 'static and you don't need to use <a href="https://floss.social/tags/unsafe" class="mention hashtag" rel="nofollow noopener" target="_blank">#unsafe</a> shenanigans. :ferris: Please see this playground with comments on how to do this: <a href="https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=6b028d5bab84d739d34d76d66a750578" rel="nofollow noopener" translate="no" target="_blank">https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=6b028d5bab84d739d34d76d66a750578</a>On Borrrow Splitting: <a href="https://doc.rust-lang.org/nomicon/borrow-splitting.html" rel="nofollow noopener" translate="no" target="_blank">https://doc.rust-lang.org/nomicon/borrow-splitting.html</a>On scoped threads API: <a href="https://doc.rust-lang.org/std/thread/fn.scope.html" rel="nofollow noopener" translate="no" target="_blank">https://doc.rust-lang.org/std/thread/fn.scope.html</a><a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://floss.social/tags/BorrowChk" class="mention hashtag" rel="nofollow noopener" target="_blank">#BorrowChk</a> <a href="https://floss.social/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> <a href="https://floss.social/tags/Threads" class="mention hashtag" rel="nofollow noopener" target="_blank">#Threads</a>

Matej Cerny"The best way to approach concurrency is to master the fundamentals" <a href="https://witter.cz/tags/scala" class="mention hashtag" rel="nofollow noopener" target="_blank">#scala</a> <a href="https://witter.cz/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://lukastymo.com/posts/022-concurrency-basic-synchronization/" rel="nofollow noopener" translate="no" target="_blank">https://lukastymo.com/posts/022-concurrency-basic-synchronization/</a>

Ivan Enderlin 🦀parking_lot: ffffffffffffffff…, <a href="https://fly.io/blog/parking-lot-ffffffffffffffff/" rel="nofollow noopener" translate="no" target="_blank">https://fly.io/blog/parking-lot-ffffffffffffffff/</a>.Excellent article from the Fly.io team about a locking bug they encountered in their codebase, and how it has resulted in a bug fix in parking_lot. Well written.Kudos to the engineers involved.<a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://floss.social/tags/lock" class="mention hashtag" rel="nofollow noopener" target="_blank">#lock</a> <a href="https://floss.social/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a>

Eric VitielloIn this article, we'll explore how actors work, how they differ from classes, and how to use them to protect the app's state from race conditions. <a href="https://oldbytes.space/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://oldbytes.space/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://oldbytes.space/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> <a href="https://oldbytes.space/tags/Actors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Actors</a> <a href="https://oldbytes.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> <a href="https://oldbytes.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://tanaschita.com/swift-actors-basics/" rel="nofollow noopener" translate="no" target="_blank">https://tanaschita.com/swift-actors-basics/</a>

Jaanus Kase<a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://iosdev.space/tags/AsyncAlgorithms" class="mention hashtag" rel="nofollow noopener" target="_blank">#AsyncAlgorithms</a> <a href="https://iosdev.space/tags/WTF" class="mention hashtag" rel="nofollow noopener" target="_blank">#WTF</a> <a href="https://iosdev.space/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a>Today’s Swift Xcode Apple packages WTF of the dayI added async-algorithms as a dependencyWhy is throttle showing me only the underscored API-s but debounce looks normal(The throttle APIs work ok, just the underscore is weird)

Sven RuppertJust published a longform article on parallel collectors in Java Streams.✅ Covers correctness, performance, pitfalls 🛠 Custom collectors with CONCURRENT semantics 🔬 JMH benchmark TL;DR: .parallelStream() is not a magic wand. <a href="https://svenruppert.com/2025/04/08/synchronous-in-chaos-how-parallel-collectors-bring-order-to-java-streams/" rel="nofollow noopener" translate="no" target="_blank">https://svenruppert.com/2025/04/08/synchronous-in-chaos-how-parallel-collectors-bring-order-to-java-streams/</a><a href="https://mastodon.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a> <a href="https://mastodon.social/tags/StreamsAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#StreamsAPI</a> <a href="https://mastodon.social/tags/OpenJDK" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenJDK</a> <a href="https://mastodon.social/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> <a href="https://mastodon.social/tags/FunctionalProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#FunctionalProgramming</a>

Jesper Agdakx 🔸With the NWO XL consortium on Cyclic Structures in Programs and Proofs, we are looking for 6 highly motivated and talented PhD students starting in September (with some flexibility). The topics range from Modal logic, proof theory, and coalgebras to Programming languages, concurrency, and type systems and Proof assistants (#Agda, <a class="hashtag" href="https://agda.club/tag/rocq" rel="nofollow noopener" target="_blank">#Rocq</a>). Information about the positions and application procedure can be found on the website: <a href="https://cyclic-structures.gitlab.io/vacancies/" rel="nofollow noopener" target="_blank">cyclic-structures.gitlab.io/vacancies/</a> Applications will be evaluated on a rolling basis but should be submitted by the 23rd of May for full consideration. Please forward to any strong candidates you know! <a class="hashtag" href="https://agda.club/tag/typetheory" rel="nofollow noopener" target="_blank">#TypeTheory</a> <a class="hashtag" href="https://agda.club/tag/modallogic" rel="nofollow noopener" target="_blank">#ModalLogic</a> <a class="hashtag" href="https://agda.club/tag/concurrency" rel="nofollow noopener" target="_blank">#Concurrency</a> <a class="hashtag" href="https://agda.club/tag/programminglanguages" rel="nofollow noopener" target="_blank">#ProgrammingLanguages</a> <a class="hashtag" href="https://agda.club/tag/typesystems" rel="nofollow noopener" target="_blank">#TypeSystems</a> <a class="hashtag" href="https://agda.club/tag/proofassistants" rel="nofollow noopener" target="_blank">#ProofAssistants</a> <a class="hashtag" href="https://agda.club/tag/cyclicstructures" rel="nofollow noopener" target="_blank">#CyclicStructures</a> <a class="hashtag" href="https://agda.club/tag/phd" rel="nofollow noopener" target="_blank">#PhD</a> <a class="hashtag" href="https://agda.club/tag/netherlands" rel="nofollow noopener" target="_blank">#Netherlands</a> <a class="hashtag" href="https://agda.club/tag/universityofgroningen" rel="nofollow noopener" target="_blank">#UniversityOfGroningen</a> <a class="hashtag" href="https://agda.club/tag/leidenuniversity" rel="nofollow noopener" target="_blank">#LeidenUniversity</a> <a class="hashtag" href="https://agda.club/tag/universityoftwente" rel="nofollow noopener" target="_blank">#UniversityOfTwente</a> <a class="hashtag" href="https://agda.club/tag/tudelft" rel="nofollow noopener" target="_blank">#TUDelft</a> <a class="hashtag" href="https://agda.club/tag/radbouduniversity" rel="nofollow noopener" target="_blank">#RadboudUniversity</a>

Clément AubertThe <a href="https://lipn.info/tags/Interaction" class="mention hashtag" rel="nofollow noopener" target="_blank">#Interaction</a> and <a href="https://lipn.info/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a> Experience <a href="https://lipn.info/tags/workshop" class="mention hashtag" rel="nofollow noopener" target="_blank">#workshop</a> (ICE 🧊) 2025 Call for paper is out! <a href="https://lipn.info/tags/CFP" class="mention hashtag" rel="nofollow noopener" target="_blank">#CFP</a> ➡ <a href="https://ice-workshop.github.io/cfp.txt" rel="nofollow noopener" translate="no" target="_blank">https://ice-workshop.github.io/cfp.txt</a> ⬅ICE 🧊 will be co-located with <a href="https://lipn.info/@DisCoTecConf" class="u-url mention" rel="nofollow noopener" target="_blank">@DisCoTecConf</a> and take place in <a href="https://lipn.info/tags/Lille" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lille</a> , <a href="https://lipn.info/tags/France" class="mention hashtag" rel="nofollow noopener" target="_blank">#France</a> 🇫🇷 on June 16th (<a href="https://www.discotec.org/2025/satellite/ice" rel="nofollow noopener" translate="no" target="_blank">https://www.discotec.org/2025/satellite/ice</a>).This workshop is very dear to me: instead of the usual "submission ⇉ (rebuttal ⇉) review" flow, it uses a very original selection procedure (<a href="https://www.discotec.org/2025/satellite/ice#the-ice-selection-procedure" rel="nofollow noopener" translate="no" target="_blank">https://www.discotec.org/2025/satellite/ice#the-ice-selection-procedure</a>), where PC members and authors discuss and collaborate for the greater good ⇆.This year again we have an amazing program committee (<a href="https://www.discotec.org/2025/satellite/ice#programme-committee" rel="nofollow noopener" translate="no" target="_blank">https://www.discotec.org/2025/satellite/ice#programme-committee</a>), an amazing invited speaker (Kirstin Peters, from Augsburg University) and welcome submissions until April 9th, 2025 ⌛.

Ben EvansThere are an indeterminate number of wolves inside of you. One has a large patch to apply, and the others have a steady stream of small patches to apply. All patches must be rebase-clean before they apply for audit reasons.The probability of the wolves livelocking asymptotically approaches 1.<a href="https://mastodon.social/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://mastodon.social/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#java</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Joachim<a href="https://hachyderm.io/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftUI</a> and <a href="https://hachyderm.io/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> question:I see a lot of online recommendations online that say to always use `@MainActor` with `@Observable` and ObservableObject including <a href="https://mastodon.social/@twostraws" class="u-url mention" rel="nofollow noopener" target="_blank">@twostraws</a>, here: <a href="https://www.hackingwithswift.com/quick-start/concurrency/important-do-not-use-an-actor-for-your-swiftui-data-models" rel="nofollow noopener" translate="no" target="_blank">https://www.hackingwithswift.com/quick-start/concurrency/important-do-not-use-an-actor-for-your-swiftui-data-models</a> But it sounds wrong to me. Am I missing something?Let’s talk about the Observable macro first: It seems like the recommendation to use a MainActor annotation here comes from people a) having been bit by the runtime issue seen for ObservableObject (see below) and b) people having learned the lesson from UIKit of „don’t touch the UI from a background thread“.But when we modify a property on an Observable-macro-object from a background thread, which in turn triggers a UI update, the `body` property still executes on the main thread. (Verified via breakpoints) There is no runtime issue or anything that suggests this would be wrong. People just seem to believe it is?For ObservableObject, if you modify a `@Published` property from a background thread, you see a runtime issue in Xcode that says „Publishing changes from a background thread is not allowed.“, so people annotate their ObservableObjects with a main actor annotation or use DispatchQueue.main.async to make changes to the property. But afaict this is a Combine warning not a SwiftUI warning and the Observable macro doesn’t use Combine.But even in the ObservableObject case why is that an issue? The docs for the Combine property wrapper don’t state that it must only be modified on the main thread. Afaik, in Combine the observer chooses where to receive an update, you can simply receive(on:) to another queue. And it seems that SwiftUI does. Even in that case the body property of an observing view is not executed on a background thread, even if the property change is.So even there I don’t see why dispatching model updates to the main queue is necessary, SwiftUI should handle that and at first glance it seems like it does, Combine just complains anyway. So I can’t find a compelling reason why that’s necessary (except for „we‘ve always done it this way“). Yet, there is a runtime issue for the Published case and everyone seems to be convinced it’s necessary. What am I missing?

Jason YipWhat every systems programmer should know about <a href="https://mastodon.online/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://assets.bitbashing.io/papers/concurrency-primer.pdf" rel="nofollow noopener" translate="no" target="_blank">https://assets.bitbashing.io/papers/concurrency-primer.pdf</a>

Chris Woody WoodruffConcurrency showdown! C# brings tasks and async/await, while Rust rocks fearless concurrency with ownership and thread safety. Dive into 'Threads, Tasks, and Ownership: C# and Rust Concurrency Explored' <a href="https://woodruff.dev/threads-tasks-and-ownership-c-and-rust-concurrency-explored/" rel="nofollow noopener" translate="no" target="_blank">https://woodruff.dev/threads-tasks-and-ownership-c-and-rust-concurrency-explored/</a> <a href="https://mastodon.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://mastodon.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://mastodon.social/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a>

burakemir<a href="https://discuss.systems/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://discuss.systems/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a> I sometimes tell this story of how async made it into programming languages over dinner. Anyone who wants to fact check or debate me on this? Little thread.

Paul Houle😅 How Much Memory Do You Need in 2024 to Run 1 Million Concurrent Tasks?<a href="https://hez2010.github.io/async-runtimes-benchmarks-2024/" rel="nofollow noopener" translate="no" target="_blank">https://hez2010.github.io/async-runtimes-benchmarks-2024/</a><a href="https://mastodon.social/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#concurrency</a> <a href="https://mastodon.social/tags/threads" class="mention hashtag" rel="nofollow noopener" target="_blank">#threads</a> <a href="https://mastodon.social/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a>

Jaanus Kase<a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://iosdev.space/tags/Concurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Concurrency</a>Has something changed in concurrency warnings between Xcode 16.1 and Xcode 16.2 beta 3? Here is an example of a warning that I get in 16.1 but not 16.2b3. (I think not getting it is correct?) I can’t find any release notes or such about this.(I put such explicit captures there because 16.2b3 was warning about implicit captures.)

Recent searches

Search options

Administered by:

Server stats:

#concurrency