You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SwiftUI inherently struggles to deliver fluid scrolling performance for large, dynamically sized collections like chat timelines. Neither does it expose mechanisms by which developers can easily optimize such performance. The primary architectural justification for a pure SwiftUI implementation is cross-platform deployment, though there is currently no indication this is planned.
AppKit’s NSTableView and NSCollectionView are specifically optimized for smooth rendering and memory efficiency when displaying extensive collections of indeterminate size. Integrating either into the current view hierarchy via NSViewRepresentable is a standard procedure.
Is there a specific engineering constraint preventing the adoption of AppKit for the timeline view to leverage these performance optimizations? Are iOS/iPadOS clients utilizing this shared codebase actively contemplated?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
SwiftUI inherently struggles to deliver fluid scrolling performance for large, dynamically sized collections like chat timelines. Neither does it expose mechanisms by which developers can easily optimize such performance. The primary architectural justification for a pure SwiftUI implementation is cross-platform deployment, though there is currently no indication this is planned.
AppKit’s NSTableView and NSCollectionView are specifically optimized for smooth rendering and memory efficiency when displaying extensive collections of indeterminate size. Integrating either into the current view hierarchy via NSViewRepresentable is a standard procedure.
Is there a specific engineering constraint preventing the adoption of AppKit for the timeline view to leverage these performance optimizations? Are iOS/iPadOS clients utilizing this shared codebase actively contemplated?
All reactions