The pros and cons depend on the requirements. Each framework has its own characteristics, advantages and disadvantages. Different usage scenarios will bring different pros and cons. It is not easy to generalize. The frameworks you mentioned are all excellent image processing frameworks. In terms of overall performance, Glide > Fresco > Picasso > UIL > xUtils, imageLoader? I don’t know which one you are talking about, it’s roughly the same.
I have used Fresco, Picasso, and Glide in my projects. Since I needed to support Gif later, I excluded Picasso. Passed the test: When loading the same number of Gifs, Fresco uses one-third of the CPU of Glide. So I chose Fresco. But what the questioner uses depends on the needs.
fresco’s scalability and completeness of functional support should be the strongest, followed by UIL, which has many parameter configurations
If the requirements are not so many, other libraries except Fresco can generally be solved with one or two lines of code (using the default configuration)
Each library has its own advantages
picasso is characterized by easy and smooth loading, while glide is better optimized and supports gif
fresco and UIL are powerful and meet various needs, but UIL has stopped updating, so some bugs need to be solved by yourself
xUtils is not a dedicated image library, so it is suitable for simple needs, and performance and other aspects are not as good as dedicated libraries
I have used all those libraries, and then I used Fresco, and I have been using Fresco ever since. The configuration is complex, but the function is powerful and the performance is superior.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The pros and cons depend on the requirements. Each framework has its own characteristics, advantages and disadvantages. Different usage scenarios will bring different pros and cons. It is not easy to generalize. The frameworks you mentioned are all excellent image processing frameworks. In terms of overall performance,
Glide > Fresco > Picasso > UIL > xUtils, imageLoader? I don’t know which one you are talking about, it’s roughly the same.I have used Fresco, Picasso, and Glide in my projects.
Since I needed to support Gif later, I excluded Picasso.
Passed the test: When loading the same number of Gifs, Fresco uses one-third of the CPU of Glide. So I chose Fresco. But what the questioner uses depends on the needs.
fresco’s scalability and completeness of functional support should be the strongest, followed by UIL, which has many parameter configurations
If the requirements are not so many, other libraries except Fresco can generally be solved with one or two lines of code (using the default configuration)
Each library has its own advantages
picasso is characterized by easy and smooth loading, while glide is better optimized and supports gif
fresco and UIL are powerful and meet various needs, but UIL has stopped updating, so some bugs need to be solved by yourself
xUtils is not a dedicated image library, so it is suitable for simple needs, and performance and other aspects are not as good as dedicated libraries
Use Fresco to pass by
I have used all those libraries, and then I used Fresco, and I have been using Fresco ever since. The configuration is complex, but the function is powerful and the performance is superior.
http://blog.csdn.net/github_3... Here is a detailed introduction and detailed comparison