TC39 will also discuss:
🔶 Async Iterator Helpers
🔶 Class composition
🔶 Composites
🔶 Concurrency Control
🔶 Decorators
🔶 Temporal
🔶 test262
🔶 Trailing zeros in Intl.NumberFormat
🔶 WHATWG Stages
You can see the full agenda here:
github.com/tc39/agendas...
🔶 Async Iterator Helpers
🔶 Class composition
🔶 Composites
🔶 Concurrency Control
🔶 Decorators
🔶 Temporal
🔶 test262
🔶 Trailing zeros in Intl.NumberFormat
🔶 WHATWG Stages
You can see the full agenda here:
github.com/tc39/agendas...
github.com
November 11, 2025 at 9:00 AM
TC39 will also discuss:
🔶 Async Iterator Helpers
🔶 Class composition
🔶 Composites
🔶 Concurrency Control
🔶 Decorators
🔶 Temporal
🔶 test262
🔶 Trailing zeros in Intl.NumberFormat
🔶 WHATWG Stages
You can see the full agenda here:
github.com/tc39/agendas...
🔶 Async Iterator Helpers
🔶 Class composition
🔶 Composites
🔶 Concurrency Control
🔶 Decorators
🔶 Temporal
🔶 test262
🔶 Trailing zeros in Intl.NumberFormat
🔶 WHATWG Stages
You can see the full agenda here:
github.com/tc39/agendas...
Over the last few months, a bunch of promising leads haven't worked out. These things can take months, so who knows? But in the meantime, I have room for more work.
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
Consulting
I write stuff here.
www.massicotte.org
November 10, 2025 at 4:16 PM
Over the last few months, a bunch of promising leads haven't worked out. These things can take months, so who knows? But in the meantime, I have room for more work.
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
My writeups on the idea so far:
Designing Async First Framework
hackmd.io/@0u1u3zEAQAO...
Different Take on Async/Concurrency?
hackmd.io/@0u1u3zEAQAO...
Deferred Disposal Reactivity
hackmd.io/@0u1u3zEAQAO...
Designing Async First Framework
hackmd.io/@0u1u3zEAQAO...
Different Take on Async/Concurrency?
hackmd.io/@0u1u3zEAQAO...
Deferred Disposal Reactivity
hackmd.io/@0u1u3zEAQAO...
November 7, 2025 at 11:13 PM
My writeups on the idea so far:
Designing Async First Framework
hackmd.io/@0u1u3zEAQAO...
Different Take on Async/Concurrency?
hackmd.io/@0u1u3zEAQAO...
Deferred Disposal Reactivity
hackmd.io/@0u1u3zEAQAO...
Designing Async First Framework
hackmd.io/@0u1u3zEAQAO...
Different Take on Async/Concurrency?
hackmd.io/@0u1u3zEAQAO...
Deferred Disposal Reactivity
hackmd.io/@0u1u3zEAQAO...
Trio: a friendly Python library for async concurrency and I/O — Trio 0.32.0 documentation
trio.readthedocs.io
November 10, 2025 at 1:22 AM
If your company needs help with any Swift concurrency issues / actors / Sendable and stuff like that, there are really few people outside of Apple who understand all this stuff better than Matt
Over the last few months, a bunch of promising leads haven't worked out. These things can take months, so who knows? But in the meantime, I have room for more work.
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
I help teams adopt Swift 6/Concurrency with confidence and success. More info about me here:
www.massicotte.org/consulting
Consulting
I write stuff here.
www.massicotte.org
November 10, 2025 at 4:22 PM
If your company needs help with any Swift concurrency issues / actors / Sendable and stuff like that, there are really few people outside of Apple who understand all this stuff better than Matt
First post on Bluesky! 👀
Day 4 of building a distributed event-stream service
- Mostly just read about Rust concurrency and the multiple ownership model (Mutexes, Arc)
- Using Claude Code to understand why it's necessary and how it fits into the service architecture
Day 4 of building a distributed event-stream service
- Mostly just read about Rust concurrency and the multiple ownership model (Mutexes, Arc)
- Using Claude Code to understand why it's necessary and how it fits into the service architecture
November 7, 2025 at 5:10 AM
First post on Bluesky! 👀
Day 4 of building a distributed event-stream service
- Mostly just read about Rust concurrency and the multiple ownership model (Mutexes, Arc)
- Using Claude Code to understand why it's necessary and how it fits into the service architecture
Day 4 of building a distributed event-stream service
- Mostly just read about Rust concurrency and the multiple ownership model (Mutexes, Arc)
- Using Claude Code to understand why it's necessary and how it fits into the service architecture
Reading @donnywals.bsky.social's article about Swift 6.2 and ended up clicking every related link.
Clearly shows how "much" I really know about concurrency in Swift 😅
www.donnywals.com/should-you-o...
Clearly shows how "much" I really know about concurrency in Swift 😅
www.donnywals.com/should-you-o...
Should you opt-in to Swift 6.2’s Main Actor isolation? – Donny Wals
Swift 6.2 comes with some interesting Concurrency improvements. One of the most notable changes is that there’s now a compiler flag that will, by default, isolate all your (implicitly nonisolated)…
www.donnywals.com
November 10, 2025 at 3:32 AM
Reading @donnywals.bsky.social's article about Swift 6.2 and ended up clicking every related link.
Clearly shows how "much" I really know about concurrency in Swift 😅
www.donnywals.com/should-you-o...
Clearly shows how "much" I really know about concurrency in Swift 😅
www.donnywals.com/should-you-o...
Luckily, there are a ton of articles on this. I read both yours and Donny's.
I'm to blame for this. I didn't catch up when Swift 6 was introduced. I was waiting for the approachable concurrency to release to catch up at once. That's why.
This feels like Swift 3 all over again.
I'm to blame for this. I didn't catch up when Swift 6 was introduced. I was waiting for the approachable concurrency to release to catch up at once. That's why.
This feels like Swift 3 all over again.
November 10, 2025 at 7:04 PM
Luckily, there are a ton of articles on this. I read both yours and Donny's.
I'm to blame for this. I didn't catch up when Swift 6 was introduced. I was waiting for the approachable concurrency to release to catch up at once. That's why.
This feels like Swift 3 all over again.
I'm to blame for this. I didn't catch up when Swift 6 was introduced. I was waiting for the approachable concurrency to release to catch up at once. That's why.
This feels like Swift 3 all over again.
Maybe I'm an idiot, but what if I keep using Swift 5?
Yes, Swift 6 is supposed to help make concurrency safer, but it definitely comes with its own challenge. And also, my apps are generally small apps anyway.
Yes, Swift 6 is supposed to help make concurrency safer, but it definitely comes with its own challenge. And also, my apps are generally small apps anyway.
November 8, 2025 at 3:48 PM
Maybe I'm an idiot, but what if I keep using Swift 5?
Yes, Swift 6 is supposed to help make concurrency safer, but it definitely comes with its own challenge. And also, my apps are generally small apps anyway.
Yes, Swift 6 is supposed to help make concurrency safer, but it definitely comes with its own challenge. And also, my apps are generally small apps anyway.
matklad.github.io/2021/04/26/c...
concurrency vs state clarity
concurrency vs state clarity
Concurrent Expression Problem
I am struggling with designing concurrent code.
In this post, I want to share a model problem which exemplifies some of the issues.
It is reminiscent of the famous expression problem in that there's a...
matklad.github.io
November 5, 2025 at 9:15 AM
matklad.github.io/2021/04/26/c...
concurrency vs state clarity
concurrency vs state clarity
These lessons compound in #rustdev:
> Cleaner APIs
> Safer concurrency
> Fewer assumptions
> Better architecture
Rust doesn’t just teach syntax.
It rewires how you think about systems.
> Cleaner APIs
> Safer concurrency
> Fewer assumptions
> Better architecture
Rust doesn’t just teach syntax.
It rewires how you think about systems.
November 6, 2025 at 12:04 PM
These lessons compound in #rustdev:
> Cleaner APIs
> Safer concurrency
> Fewer assumptions
> Better architecture
Rust doesn’t just teach syntax.
It rewires how you think about systems.
> Cleaner APIs
> Safer concurrency
> Fewer assumptions
> Better architecture
Rust doesn’t just teach syntax.
It rewires how you think about systems.
All courses on sale at:
gocode.ca
Use this coupon code at checkout:
NVSL25
Code expires:
November 8, 2025.
#go #golang #Vue #websockets #react #python #laravel #ubuntu #microservices #concurrency #Fyne
gocode.ca
Use this coupon code at checkout:
NVSL25
Code expires:
November 8, 2025.
#go #golang #Vue #websockets #react #python #laravel #ubuntu #microservices #concurrency #Fyne
November 3, 2025 at 2:50 PM
All courses on sale at:
gocode.ca
Use this coupon code at checkout:
NVSL25
Code expires:
November 8, 2025.
#go #golang #Vue #websockets #react #python #laravel #ubuntu #microservices #concurrency #Fyne
gocode.ca
Use this coupon code at checkout:
NVSL25
Code expires:
November 8, 2025.
#go #golang #Vue #websockets #react #python #laravel #ubuntu #microservices #concurrency #Fyne
I made a video where I explore fundamental concepts for swift concurrency, like isolation domains, Sendable, etc.
Understanding these concepts helps a lot when it comes to migrating to swift 6.2 and to choose the right tool for the job when solving compiler errors
www.youtube.com/watch?v=tgtc...
Understanding these concepts helps a lot when it comes to migrating to swift 6.2 and to choose the right tool for the job when solving compiler errors
www.youtube.com/watch?v=tgtc...
Mastering the concurrency concepts for Swift 6.2
YouTube video by Crafting Swift
www.youtube.com
November 5, 2025 at 6:11 PM
I made a video where I explore fundamental concepts for swift concurrency, like isolation domains, Sendable, etc.
Understanding these concepts helps a lot when it comes to migrating to swift 6.2 and to choose the right tool for the job when solving compiler errors
www.youtube.com/watch?v=tgtc...
Understanding these concepts helps a lot when it comes to migrating to swift 6.2 and to choose the right tool for the job when solving compiler errors
www.youtube.com/watch?v=tgtc...
wish i had learned how to make clothes instead of forming nuanced opinions about all the different ways to implement concurrency in a programming language
October 31, 2025 at 11:46 PM
wish i had learned how to make clothes instead of forming nuanced opinions about all the different ways to implement concurrency in a programming language
yeah, message passing is cool
nah, channel spaghetti isn't cool
I still think cancellation and structured concurrency is good
I'm still thankful that async rust was written in a way I can run on a bare metal MCU
nah, channel spaghetti isn't cool
I still think cancellation and structured concurrency is good
I'm still thankful that async rust was written in a way I can run on a bare metal MCU
November 1, 2025 at 12:36 AM
yeah, message passing is cool
nah, channel spaghetti isn't cool
I still think cancellation and structured concurrency is good
I'm still thankful that async rust was written in a way I can run on a bare metal MCU
nah, channel spaghetti isn't cool
I still think cancellation and structured concurrency is good
I'm still thankful that async rust was written in a way I can run on a bare metal MCU
Rust futures' ability to do intra-task concurrency (see @without.boats' "Let futures be futures") is a superpower, but cancellation and "futurelock" (as this RFD coins) are both challenging code review problems.
October 31, 2025 at 8:13 PM
Rust futures' ability to do intra-task concurrency (see @without.boats' "Let futures be futures") is a superpower, but cancellation and "futurelock" (as this RFD coins) are both challenging code review problems.
It's end of the year, so I'm again... looking into how Swift concurrency works w/ SwiftNIO. The funny thing is that in the OpenGroupware port I'm working on I don't actually need any concurrency 🙂 Most of the work/logic it does is PostgreSQL queries running in a transaction. So nothing you'd put […]
Original post on mastodon.social
mastodon.social
November 2, 2025 at 12:17 PM
It's end of the year, so I'm again... looking into how Swift concurrency works w/ SwiftNIO. The funny thing is that in the OpenGroupware port I'm working on I don't actually need any concurrency 🙂 Most of the work/logic it does is PostgreSQL queries running in a transaction. So nothing you'd put […]
While useful, LLMs struggle with concurrency bugs and require careful prompt engineering to yield accurate results. Incorrect suggestions can lead to significant wasted time if not critically evaluated. #PromptEngineering 3/6
November 2, 2025 at 2:00 PM
While useful, LLMs struggle with concurrency bugs and require careful prompt engineering to yield accurate results. Incorrect suggestions can lead to significant wasted time if not critically evaluated. #PromptEngineering 3/6
🎯 JEP 525 proposed to target JDK 26
Title: Structured Concurrency (Sixth Preview)
Type: feature
Component: core
Release: 26
See openjdk.org/jeps/525
Title: Structured Concurrency (Sixth Preview)
Type: feature
Component: core
Release: 26
See openjdk.org/jeps/525
October 31, 2025 at 12:50 PM
🎯 JEP 525 proposed to target JDK 26
Title: Structured Concurrency (Sixth Preview)
Type: feature
Component: core
Release: 26
See openjdk.org/jeps/525
Title: Structured Concurrency (Sixth Preview)
Type: feature
Component: core
Release: 26
See openjdk.org/jeps/525
Performance tests show how your app will perform in terms of load, concurrency, & throughput. And here, Noor helps you build an end-to-end performance test in Apache JMeter. Your test suite will be dynamic & one-click executable, & you'll analyze the results too.
www.freecodecamp.org/news/how-to-...
www.freecodecamp.org/news/how-to-...
November 1, 2025 at 8:01 AM
Performance tests show how your app will perform in terms of load, concurrency, & throughput. And here, Noor helps you build an end-to-end performance test in Apache JMeter. Your test suite will be dynamic & one-click executable, & you'll analyze the results too.
www.freecodecamp.org/news/how-to-...
www.freecodecamp.org/news/how-to-...
This looks like an incredible tool for testing concurrent #Java code: github.com/cmu-pasta/fray
Also has research papers published and some presentations (now on my To Watch list!).
#Testing #Concurrency
Also has research papers published and some presentations (now on my To Watch list!).
#Testing #Concurrency
GitHub - cmu-pasta/fray: A controlled concurrency testing framework for the JVM
A controlled concurrency testing framework for the JVM - cmu-pasta/fray
github.com
October 30, 2025 at 5:47 PM
This looks like an incredible tool for testing concurrent #Java code: github.com/cmu-pasta/fray
Also has research papers published and some presentations (now on my To Watch list!).
#Testing #Concurrency
Also has research papers published and some presentations (now on my To Watch list!).
#Testing #Concurrency
Book of the Day: C++ Concurrency in Action by Anthony Williams
meetingcpp.com/mcpp/books/b...
#cplusplus
#cpp
meetingcpp.com/mcpp/books/b...
#cplusplus
#cpp
Anthony Williams
This book is an in-depth descrition of the multithreading and concurrency support in C++ and how to use it
meetingcpp.com
October 29, 2025 at 9:12 PM
Book of the Day: C++ Concurrency in Action by Anthony Williams
meetingcpp.com/mcpp/books/b...
#cplusplus
#cpp
meetingcpp.com/mcpp/books/b...
#cplusplus
#cpp
Move fast break and concurrency.
October 28, 2025 at 1:32 PM
Move fast break and concurrency.
Just like how human are bad at writing correct concurrent code, we are also bad at solving concurrent problems in our lives (both leads to *panic*, lol)
So the advice of only introduce concurrency if you must applies as life advice too: solve one problem at a time, multitask only if you must.
So the advice of only introduce concurrency if you must applies as life advice too: solve one problem at a time, multitask only if you must.
October 30, 2025 at 6:09 AM
Just like how human are bad at writing correct concurrent code, we are also bad at solving concurrent problems in our lives (both leads to *panic*, lol)
So the advice of only introduce concurrency if you must applies as life advice too: solve one problem at a time, multitask only if you must.
So the advice of only introduce concurrency if you must applies as life advice too: solve one problem at a time, multitask only if you must.