I think non-global actor isolation capture is buggy. I made some tests and saw assertIsolated() failing after checking the #isolation was correct and even the queue I use as executor. There may be some GCD issues like assumeIsolated that was buggy on macOS < 15. Also #isolation may be wrongly set.
Posts by Pierre Tacchi
I have an almost same pattern w/ WebSocket server actor + WS client actors. Clients are created via a factory. I tried to pass a cancel handler isolated to the server and was never able to make it work w/out data-race. I Relied on a global actor but ended up passing a weak server instance.
That’s why HAVN designed the EMF-blocking beanie. Powered by our proprietary WaveStopper™ Technology, it forms a barrier that blocks over 99% of WiFi, 5G, and Bluetooth radiation right where it matters most: your brain.
They gentrified the tinfoil hat
For the full experience you should be filling for bankruptcy, no ?
I haven’t completed it but I have started modernizing the Apple Mac HIGs here. I have topics on toolbar guidelines and layout guidelines that are detailed, illustrated, and modernized.
marioaguzman.github.io/design/
iOS 26 is ugly but as far as I experienced pretty stable. And recent changes made is readable too. But I just can’t w/ macOS 26… this sidebar design alone is an insult to whoever invented the sidebar…
Yep, that’s the way 👍
Et ils en auraient installé presque 800 alors ?!
Does someone also sees SwiftUI lists not working properly (unable to select item) on MacOS 14 for apps compiled under Xcode 26 ?
I won’t argue on the AI part. But yeah I don’t see Apple gatekeeping everything too. Thank you for sharing your view 😃
Thank you for the explanation! If we put aside app stores I’m worried about access to the platform as a whole. I write code that runs 24/7 on Mac and nobody will ever install it through any store, I do iOS tooling too. I wonder if at some point I’ll be barred from the tools / signing system, …
They’re US* tech, sorry.
Interested to know more. Also since we both dev on Apple platforms should we be worried as they’re IS tech also ?
"anti-AI people should just learn more about it" motherfucker I know so much about it, that's why I'm anti-AI
J’en suis arrivé à la même conclusion.
Sounds like fun !
Never thought about using AnyCancellable for tasks. Great idea thank you for sharing!
I think you made a mistake in the first code example featuring setup, you use the store method on the task before introducing it when should have used it on the publisher.
🥳 (thank you !)
I have trouble reading the comments and method/func names. Not enough contrast I think. But overall I like it 😃.
I never update until the x.2, earlier if stability and app availability are a consensus. But here I know I’ll wait for a backlash and a potential redesign and I know they won’t… 😕
Not a fan of iPadOS and iOS 26 but I feel that something I could acclimate to. But macOS ? An insult…
Would be great if you hadn’t to backstick them at call site. Like you do w/ keyword used as variable names (var `for` = 4)
@ FocusState and the focus modifier. But it’s way more limited than messing w/ the first responder directly.
Exactly ! This nuance is important and shows how rare the need of global actors really is.
It’s really about coordinating concurrent accesses to a unique ressource. Say a database client, writing to a single log file, etc… Global actors allow you to make this a simple decoration in your code while doing all the heavy lifting. And it’s clearly and solely about isolation.
In the early days of SwiftUI I remember asking myself “is that buggy or do I still dont get the thing” a lot ! Now it’s better, on both sides.
Hello! I’m excited to introduce an idea that’s been floating in my head for a while: PayMe
PayMe is invoicing software for creators and professionals, with just a 1% fee.
Photographer invoicing for a shoot? You could save >2% of your income using PayMe over QuickBooks!
Check it out!
usepayme.app
Those are indeed pretty nice !
Congrats ! I'd be interested to know what technique you use to generate the beat. Simple timer or something else ? I'm about to start working on a tool where I need a precise beat and I'm not sure how to do it the right way. So far I used AsyncStream + Task.sleep when needed...