Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kingfisher vs SDWebImage #12

Closed
AvdLee opened this issue Apr 19, 2015 · 3 comments
Closed

Kingfisher vs SDWebImage #12

AvdLee opened this issue Apr 19, 2015 · 3 comments

Comments

@AvdLee
Copy link

AvdLee commented Apr 19, 2015

Good to see the work done to create this purely Swift image framework. I'm using SDWebImage in a lot of my projects, purely because it's known as stable and we're used to it in our projects. As we are now switching to use Swift in our projects, I'm looking for alternatives like Kingfisher.

SDWebImage can be used in iOS 7, what about Kingfisher? This is one important requirement for our projects.
Furthermore, can you tell anything about the performance difference between using SDWebImage and Kingfisher?

@onevcat
Copy link
Owner

onevcat commented Apr 19, 2015

Hi,

Kingfisher does not support iOS 7, since it is using cancelable block object and an option of low priority when downloading, which is iOS 8 feature.

Kingfisher is very young and I suggest you persist in SDWebImage if you need to support iOS 7 for a while. Kingfisher would be a choice if you prefer sure Swift instead of Swift/OC mixed.

About the performance, I did not do a benchmark myself. But the core implementation of both is similar, so I guess you can expect similar performance if you use Kingfisher.

@AvdLee
Copy link
Author

AvdLee commented Apr 19, 2015

Thanks, clear answer. Will mark this project to use in the next iOS 8 only project.

@onevcat
Copy link
Owner

onevcat commented Apr 19, 2015

:) Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants