Pierre Tacchi
@pyroh.bsky.social
Head of Research & Development @ Velvet Flare.
I create and solve problems with #SwiftUI.
I create and solve problems with #SwiftUI.
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…
November 12, 2025 at 3:00 PM
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 👍
October 19, 2025 at 12:41 PM
Yep, that’s the way 👍
Et ils en auraient installé presque 800 alors ?!
October 11, 2025 at 11:28 AM
Et ils en auraient installé presque 800 alors ?!
I won’t argue on the AI part. But yeah I don’t see Apple gatekeeping everything too. Thank you for sharing your view 😃
October 8, 2025 at 7:50 PM
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, …
October 8, 2025 at 6:04 PM
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.
October 8, 2025 at 11:55 AM
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 ?
October 8, 2025 at 11:54 AM
Interested to know more. Also since we both dev on Apple platforms should we be worried as they’re IS tech also ?
J’en suis arrivé à la même conclusion.
October 5, 2025 at 8:10 AM
J’en suis arrivé à la même conclusion.
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.
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.
September 18, 2025 at 6:24 PM
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.
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.
I have trouble reading the comments and method/func names. Not enough contrast I think. But overall I like it 😃.
September 8, 2025 at 5:46 PM
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… 😕
September 7, 2025 at 4:55 PM
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…
September 7, 2025 at 4:49 PM
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)
August 21, 2025 at 12:49 PM
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.
August 12, 2025 at 12:14 PM
@ 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.
July 20, 2025 at 7:19 AM
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.
July 20, 2025 at 6:09 AM
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.
July 10, 2025 at 6:15 PM
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.
Those are indeed pretty nice !
July 7, 2025 at 5:10 AM
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...
July 2, 2025 at 8:46 AM
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...