Post #1839168

2026-04-07 16:44 UTC

@mattiem @rhysmorgan @akbashev Or “under what conditions would the subtleties of this code be understood by everyone on our team?” On my own private project, I’d happy dive deep into this. But at work we have 100 iOS devs, many of whom don’t have the same level of deep curiosity. (Sorry for interrupting with this cheeky reply, but it is a factor!)

Replies (2)

@rhysmorgan@mastodon.social 2026-04-07 17:04

@matthew @mattiem @akbashev If anything, I think scale and the simplicity of *not* having to worry about MainActor-isolation, speeding up your tests, etc. by actually being able to run in parallel, fewer overall constraints on your types – I think that's a factor in favour of using this pattern (in a year or two once Approachable Concurrency has been fully baked, these patterns detailed a lot more, etc.)

Open ##1839169
@mattiem@mastodon.social 2026-04-07 17:04

@matthew @rhysmorgan @akbashev no I think this is a super-good question! In this case, we're talking about a decision that has pretty extensive technical implications. And real, large code bases tend to benefit even more from relaxing constraints. So, I would argue in favor of some upfront learning in exchange for significant longer-term wins.

Open ##1839170