I just go straight to Apple Store for a new MacBook when doing that

Yea I like that domain 😆 stems from a lot of confusion when I got started with swiftui

Amazing! Curious where you found it?

Death by a 1000 cuts 😏

Is there any perf difference between the two?

Shameless plug check out swiftui.wtf 😀

True if RN ever wants to become a sui wrapper instead UIKit wrapper (which I don’t think it should), but for simple “entry point” you can just make an RN component that takes a sui view and handles the UIHostingController bridging and that’s about it no?

Sounds like the same issue CK had… the solution they went with is to write a wrapper of CK with syntax almost identical to SUI to make fb engineers happy, but it’s like Xamarin/Osmeta so it still doesn’t solve interop with actual sui (eg like Charts or Widgets which are sui native)

Are there any blockers or just not implemented? On the surface it seems like SUI is actually a much more natural fit for RN declarative style than UIKit

Oh interesting I had no idea RN has significant outside contributions!

Oh this is niceeeee

Oh rewatching the the vid I see it’s a standalone app and quite different. Was it built in house and open sourced or outside by the community? I always felt like some things (gql, react) are fully embraced and enhanced by the community while RN still felt like “meta’s baby” that others just use?

Is this basically exported from Flipper/Sonar?

Hi me too! 😀

LazyVStack is lazy but doesn’t recycle the views. Once they are created - they stay and aren’t reused.
List can’t create view on the fly (ie make them lazy) if the view size is ambiguous (size being number is resolved views, not point size)
This ww covers it:
developer.apple.com/videos/play/...

AL does the layout on main thread, and it doesn’t scale for very large/complex apps. I honestly don’t know if SwiftUI is doing layout on main (i think it does actually) but it must be more optimized than AL. IIUC it’s kinda like web’s flexbox model