Yass_92

@DonnyWals @lupo342 I’m not sure but I think I had better performance with iOS 18 than iOS 26

Not exactly sure how a LazyVGrid handles everything but there are very simple ways to mess up performance, like having a simple if statement in the ForEach that you're using to render stuff can slow the UI down to a crawl. Also not sure whether SDWebImage keeps a cache, and how much stuff it caches. If you can, you might want to cap it to twice the number of items on screen for example

Whoever said SwiftUI List and SwiftData with Query on the main actor can’t perform well, watch this. Close to 4000 items, with relationships that I’m not even prefetching yet. Didn’t even do anything special tbh…

@DonnyWals @lupo342 I think I will try to use a collection view instead for this case and see if I have better performance. I found SwiftUI very frustrating, It’s a good framework to make view faster but in terms of performance, it’s not the better tool

@lupo342 @DonnyWals I used a lazyvgrid in my project, where cell contains image fetched from network, with sdwebimage. I also used resizing. Very bad memory performance. I set to nil the image reference when cell disappear but nothing change

@DonnyWals @yem_88 The issues I’ve run into are with images stored on device e.g images captured via the camera. Loading them on the main thread, is rather expensive. Unfortunately, swift data does this by default.

@DonnyWals @lupo342 Is it a list or Lazyvstack ? Curious about memory consumption

@lupo342 Every row loads a random image from the network: I’m using an in memory cache, no backing file storage

@twannl I think it will be better to have some child views structs in order to anticipate unnecessary redraws

Your SwiftUI views grow fast. You refactor them into extensions, computed properties, or new Views — but there’s no single right way to structure them. - Some prefer ViewModifiers. - Others extract everything into smaller Views. - And some keep logic close to the body for clarity. I’m curious — how do you approach SwiftUI architecture as your project scales? What rules (or anti-rules) have worked best for you? 👇 #swiftdevelopment #iosdevelopment #swiftui #swiftlanguage

@azamsharp Maybe with an enum State { case loading; case loaded(Int) } and use a switch case in the view

Which technique will you use to show the value of count when available else show loading message? * You are not allowed wrap the Text in any other view. * If you have better solution then write in comments. #SwiftUI

@iSapozhnik @twannl If your create a task manually with Task {}, if you don’t explicitly cancel it in view disappear, it will never be cancelled

@twannl > If your view disappears, the tasks created in onAppear will not be cancelled automatically. The .task { } modifier *will* automatically cancel when the view disappears. Sorry I read this 5 times and did not get. @twannl could you elaborate please?

This is one of the most common mistakes I see iOS developers make. The code looks solid, until you zoom into the alternative 👇 SwiftUI offers a .task { } modifier, which comes with a few benefits: - You can set an id to automatically cancel it when that id changes - A priority can be attached directly to the modifier - The task will be scheduled for execution even before the view appears The latter means a slightly better performance. But that's not all! If your view disappears, the tasks created in onAppear will not be cancelled automatically. The .task { } modifier *will* automatically cancel when the view disappears. This is just one of the five most common mistakes I've seen developers make with async/await. ✨ Check the link on my profile for a free 5-day email course, revealing all five mistakes

@FCButters T’es un ancien si t’as connu le forum sur ce site mdr

@KiksGln Il a dû filmer sur les coups de 5 h 30 du mat, sinon je ne vois pas d’explication

Pont de Bezons sans embouteillages , c’est super rare

@DonnyWals I hope the the urlsessionmethod is marked as concurrent in order not to block the main thread

Blocking the main thread is bad practice, I think we all know that. With Swift 6.2 new projects will default to running all code, including async functions on the main actor. That begs the question; will this code block the main actor? gumroad.com/l/practical-sw…

@mecid @concurrent No the method marked with nonisolated will be executed to the same context of the caller

Not sure I understand it. Why do we need @concurrent when we have nonisolated + async combination? Is it provide the same functionality?

@DonnyWals @mecid @concurrent In a vidéo session from wwdc 2025, they explicitly annotate a method with concurrent and even if the method is isolated to main actor, the method is executed in background. I don’t think that’s a bug

@mecid @concurrent Posted on the forum: forums.swift.org/t/concurrent-a…

@Paris_sginfos Le pauvre Pires qui appelle dembele et se mange des vents

🫡 Toujours aussi dévoué au travail collectif, Dembele est un exemple pour ses coéquipiers ! 🥇 En interne, ses coéquipiers commencent à le taquiner sur la perspective de le voir soulever le Ballon d’or en fin d'année tant l'attaquant français semble avoir pris une nouvelle dimension depuis quelques mois. 👀Il suffit d'ailleurs de voir l’attroupement à sa sortie du stade. Des scènes que l’on n'avait plus vu autour d'un joueur du PSG depuis le départ de Kylian Mbappé. 👥 La personnalité introvertie mais solaire du Parisien fait l'unanimité en interne, où on le voit comme le leader offensif de l'équipe. 🗞 RMCSport 🎥 Loïc Tanzi

@i2ss95 Félicitations 👌

On est le 30 août ptdrrrr j’ai eu mon 2eme voeux mais blc j’suis heureux 🥳🥳🥳🥳🥳🥳🥳🥳🥳🥳

@pointfreeco I decided to change my way of creating task by adopting yours. It’s easier for me to handle unit tests. I have to save the task as state property in order to handle cancellation, for example, when the view goes away

People often ask: “How should I perform async work from a synchronous context?”, like in a SwiftUI button closure. In such cases, it seems you have no choice but to spin up an unstructured “Task{…}”, but where should it go? 🤔 Watch for the answer:

@Mas93140 J’attends le départ de Mbappé avec impatience, merci pour tout mais faut passer à autre chose maintenant

@yem_88 Club de clowns.

Nous ne sommes pas en finale c’est vraiment dramatique mdr

@mecid An other point. What about the cancellation for the task created in your closure ?

Is it safe to call dismiss() that way. I mean, it requires running on the main thread.

COMPILATION TYSON FURY ( WINNER ) VS FRANCIS NGANNOU

@Antho_J7 @PSGinMyBlood_of Le gris en terme de maillot extérieur, pas sûr qu’on ait fait mieux

@PSGinMyBlood_of Il en manque quelques uns 😁😁🔴🔵🙏🏻🙏🏻🙏🏻 j’espère gagner

J'offre 5 équipements du stock pro au hasard parmi ceux qui me montrent leurs collection de maillots du #PSG ❤️💙 ➡️ Soyez pas timides, maillots boutiques, préparés, portés, on s'en fouuut 🥳 👇👇