Replying to
@joe@f.duriansoftware.com @designatednerd@mastodon.social the word “seal” slayed in my grade 3 class
Remote
Matt Massicotte
@mattiem@mastodon.social
mastodon 4.8.0-nightly.2026-10-06apple platform dev, outdoors, justice, games, he/him
every problem has a simple wrong answer
0 Followers
0 Following
50 Posts
Joined August 10, 2018
Boosted by @jwz@mastodon.social
MAY the 4th be with you
MUST the 4th be with you
SHALL NOT the 4th be with you
MUST NOT the 4th be with you
I cannot figure out if understanding programming no longer matters or matters more than ever.
And the worst part is every response I might get to this will somehow make it more unclear.
Recently, I was asked an interesting question. If the purpose of an actor is to protect mutable state, is a stateless actor pointless?
It is definitely something to look at closely, but there are some uses that can make sense.
I am having feelings today.
oh look @swiftconnection@mastodon.world has announced some speakers
Something I want to point out, perhaps primarily to myself.
It can be difficult to walk the line between "here is something that you might take interest in" and "endorsement". I *like* to think I'm quite sensitive to tone and approach to communication. But I don't get it right all the time.
I have tremendous respect for the point-free folks, and I just wanted to more publicly apologize for not being more careful today.
I have long-believed AI is not “just a tool” and hearing stories about how it has helped people manage loneliness is not helping to change my mind
Boosted by @joe@f.duriansoftware.com
The day's plans have gone sideways. So! Do you have any Swift Concurrency questions? Or, (dare I ask) ideas on things you'd like changed?? Hit me with it!
Replying to
@saagar@federated.saagarjha.com how dare you insult the swan lord mark my words you shall rue this day
Replying to
@bigzaphod@mastodon.social i think it really is getting better, but when it comes to typed throws, problems abound…
Replying to
@tonyarnold@mastodon.social funny, I was actually messing around with the SwiftPM codebase today (but on a completely different area…)
Replying to
@darrylhthomas@mastodon.social I believe it is parody. But, it also could be totally real too…
Replying to
@wigging@fosstodon.org if it’s static text I *think* you can copy it from another program and paste it to retain colors (as long as the copying app does it as rich text)
Replying to
@griotspeak@soc.mod-12.com I felt like that Kimmel thing was a) extremely easy and b) low personal cost as well
Replying to
@romy@mastodon.berlin recently, someone generated a video (based on an image) of me. It was an interesting discovery.
Replying to
@kasrababaei@mastodon.social very common to want this, but unfortunately no. There is no way to do this that is guaranteed not to deadlock.
While not necessarily helpful for practical problems, the need for synchronous access can be a very useful design hint. Especially if actors are involved (and perhaps should not be)
Replying to
@kasrababaei@mastodon.social yes. You can use a local “noniolsated(unsafe)”. This is a very useful technique.
But like with all unsafe opt-outs, have to use with care.
Replying to
@samdeane@mastodon.org.uk yeah there are elements that give it away. But the problem is this is probably already very common and will only get worse.
Replying to
@AshtonDev@mastodon.social many of Apple’s own APIs do not support timeout/cancellation, so this is not a straightforward thing. But something is coming:
https://github.com/swiftlang/swift-evolution/blob/main/proposals/0526-deadline.md
Replying to
@patters@mastodon.social ordering is absolutely a challenge!
I have found either a queue or a tool to prevent actor reentrancy (which is fundamentally also a queue internally) to be essential. And I agree that something like this should be in the language/stdlib. It has been discussed!
Your AsyncStream example, however, does not sound like normal behavior. Are you sure it wasn't a buffering problem?
Replying to
@agarrharr@mstdn.social What you have here is an arrangement that fundamentally need *synchronous* access to MainActor state. Synchronous access => must be the same isolation.
So the compiler is forcing you to decide. Does everything become MainActor, or should some accesses become asynchronous?
Replying to
@agarrharr@mstdn.social that is expected for anything preconcurrency. That attribute downgrades errors to warnings in 6 mode.
Replying to
@sjs@techhub.social hmm, I don't think you need to be too dogmatic about this. But it's a last resort. Pushing the task creation up as far as it can go is usually a good strategy. But eventually (like a button) there are limits.
I also think it is bizarre that SwiftUI has no AsyncButton. Everyone needs this.
Replying to
@ph1ps@mastodon.social @bok@mastodon.social I agree. I think a large part of the lack-of-understanding stems from very difficult API that you could *mostly* just ignore before. CoreAnimation and AVFoundation are two good examples (and an improvement for CA's problems has been suggested!)
You are also on to something with RBI. It is a very valuable tool, but needs more feedback when it cannot do the thing. Again, compiler diagnostics!
Replying to
@bok@mastodon.social one of my own focus areas is reducing the number of keywords/attributes that people are exposed to. I think just seeing them, even if you do not actually need to use/care about them, is a major problem.
Replying to
@bok@mastodon.social perfect and bug free no. No one can help with that.
But for the first two points, I think it is actually not super far. 6.2 was a major leap. Better compiler diagnostics are a huge component of this, in my opinion.
Replying to
@calicoding@mastodon.social i use a slightly modified version of this technique. It’s imperfect, but does the job.
https://kean.blog/post/swiftpm-and-xcode
Replying to
@wlumley@mastodon.social great stuff! I know nothing about Kotlin so the comparison was very interesting.
(Totally separately, I also noticed so Mastodon or Bluesky links anywhere. Omission?)
Replying to
@wigging@fosstodon.org I manually highlight only things I really want to call out. I’ve thought about doing something fancier, but I think that’s a good effect for presentations for the most part. Considered it?
Replying to
@agarrharr@mstdn.social yeah, so this JWT type needs to be Sendable but is not.
But also it's weird that this is a warning and not an error. There might be more to this configuration that needs to be investigated. But that will not change the nature of the problem.
Replying to
@samdeane@mastodon.org.uk while I think this is true *for the non-wealthy*, I also think this is only one component of the net impact it will have.
(Which I believe will be extremely negative, but I hope I am wrong)
Replying to
@agarrharr@mstdn.social yup you are chasing it down. Generic types probably also need to add conditional Sendable conformances.
Replying to
@tonyarnold@mastodon.social @reveal@indieapps.space I could have sworn there was a build config option here, darn
Replying to
@helge@mastodon.social @tonyarnold@mastodon.social @reveal@indieapps.space ah yes! That’s what I was thinking of. But unsure if this can be used to control linking behavior…
Replying to
@kp@mastodon.design I believe it is a joke.
But also, the “clean room reimplementation” is legally-significant. (Not that laws actually matter much in this regard anymore)
Replying to
@colincornaby@mastodon.social @ryanlintott@mastodon.social Maybe you know how to do this?
Replying to
@samdeane@mastodon.org.uk same thing is happening for whole products. Cloning is cheap and no one can stop you.
Replying to
@reveal@indieapps.space I have had problems with this too. What about a package with two targets. One dummy, that is conditionally dependent on a second, real target. Does that also cause the undesirable linking?