Oh, I so adore articles dedicated to the scroll optimization and this one isn't an exception. Even though this article was written in the distance 2015, there are a lot of techniques that are still actual nowadays. Especially I like the tip about Subpixel Rendering.
p.s. Don't be afraid of Objective-С.
https://medium.com/ios-os-x-development/perfect-smooth-scrolling-in-uitableviews-fd609d5275a5
#iOS #performance
p.s. Don't be afraid of Objective-С.
https://medium.com/ios-os-x-development/perfect-smooth-scrolling-in-uitableviews-fd609d5275a5
#iOS #performance
Medium
Perfect smooth scrolling in UITableViews
Story about optimizations for reaching 60 FPS in iOS most frequently used building block
A bit of array performance - need to be aware when it's preferable to use reserveCapacity rather than a simple array allocation. Be familiar with the Big-O notation! 😉
https://www.hackingwithswift.com/articles/128/array-performance-append-vs-reservecapacity
#swift #performance
https://www.hackingwithswift.com/articles/128/array-performance-append-vs-reservecapacity
#swift #performance
Hacking with Swift
Array performance: append() vs reserveCapacity()
Sometimes its faster to let Swift figure things out for you
I always prefer writing ==
https://twitter.com/nicklockwood/status/1324491275291295749
#swift #performance
for bool comparison rather than ! for better readability, but ... oh, common, it dramatically slower.https://twitter.com/nicklockwood/status/1324491275291295749
#swift #performance
Twitter
Nick Lockwood
TIL writing if foo == false {} Compiles dramatically more slowly in Swift than: if !foo {} And you should probably always use the latter even if you find it less readable: https://t.co/9MI7XteFRZ