Combining vs Concurrency - What Is the Difference?

5min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Swift is using both combined and concurrency in different places, actually in the same pipeline. We had to do some crazy things to get performance on this horrible device. To get that to work seamlessly, probably not 60 frames per second, but maybe 30 frames per second,. And so what we do is we use combined to limit the number of concurrent tasks that we have or download in an image. When we are done downloading that image, we scale it down to 25%. Then on the UI, and we cache that. And then on theUI, we are showing you, it's like almost blurred image while we are fetching the full resolution photo. There is some crazy logic to do

Guest

Aviel Gross - @avielgr

Youtube Video: https://youtu.be/G8I8xdGJB68

Related Episodes

Related Links

Sponsors

Stream - Free In-App Messaging SDK & UI Kits for iOS/Swift

Stream Chat is the easiest way to add messaging to your iOS app. High-level UI components connect the Stream Chat API with minimal coding.

Try Stream Chat free for 30 days https://gstrm.io/empowerapps or
apply for your Maker Account, free forever for qualifying teams https://gstrm.io/empowerappsmaker

Try for free

Bushel - the macOS virtual machine app for developers
I'm looking for beta testers!

For developers who want to be rigorous and uncompromising in their app testing.
You can set up your virtual machine for almost any configuration, from a fresh, factory reset of the Ventura beta all the way back to Big Sur.
Test, simulate, roll back and debug apps and scripts however you need to without worrying about destroying your machine.

If you want to be invited to our first TestFlight, or even if you just want updates on Bushel, sign up at the website, and we will get in touch with you.

swiftpackageindex.com is the place to find Swift packages.

over 5,000 packages indexed now, you’ll find a package that can help.
help you make better decisions about your dependencies.
host DocC-based documentation for package authors.

You can see how well maintained every package is, what platforms and Swift versions it’s compatible with based on real-world build data, how many other dependencies it will bring in and much more. Unlike an open-source library, running an open-source website requires ongoing time for maintenance and supporting package authors in addition to the time we spend on new features. Our work is primarily funded by you - the Swift community
If the site has helped you find a package, or if you want to support a community-run open-source project, please go to swiftpackageindex.com, look for the pink heart, and join over a hundred other people who support our work through GitHub sponsors.

Show Notes