[proposal] remove misleading "most liked package" from description

[iapicca]

getx has always boasted about being a "very popular package"

Some (including myself) always found the number of "likes" on pub.dev being suspicious for 2 reasons:

• by comparison to obviously more popular packages (eg: bloc, provider, etc)
• given the habit of the maintainer to make unproven claims

now

the download count is finally available on pub.dev through experimental flag and a quick comparison shows a huge disparity between "likes" and actual usage of the package

package	likes	downloads
bloc	2.9k	2.5M
riverpod	3.4k	2M
provider	10.3k	3.75M
getx	14.8k	604k

screenshots

I suggest to remove the self-appointed "most liked package" title from the package documentation since it could mislead adopters

[BlueGalaxyForest]

@iapicca Having a large number of downloads does not necessarily mean it is useful, and similarly, having a large number of downloads does not necessarily mean that the person who downloaded it likes the package I am a Flutter developer who switched from the "provider" package to "Getx". Providers are not as user-friendly as Getx, so I like Getx instead of Providers This also proves that packages with high download rates do not necessarily mean people like them. Flutter developers may have heard others say that state management should use Providers, but found that Providers are not easy to use. This explains why Providers have high download rates but fewer people like them, while Getx has lower download rates but more people like them

[jonataslaw]

Thank you for raising this point. However, I’d like to address some critical aspects regarding the use of download counts as a metric for evaluating package popularity or reliability.

Download counts are inherently susceptible to inaccuracies due to several factors:

• Frequent updates: Each new version release inflates download statistics.
• Automated processes: CI/CD pipelines (e.g., GitHub Actions) frequently re-download dependencies, artificially boosting the numbers.
• Potential misuse: Download statistics can also be skewed by malicious activity or automated attacks.

Even the NPM team advises against using download counts as a primary indicator of a package's popularity or quality. This makes relying solely on these numbers for recommendations questionable.

If you're looking for more reliable metrics, consider analyzing the number of open-source projects that depend on the package. For example:

• [Riverpod](https://github.com/rrousselGit/riverpod) is used in over 67,000 projects.
• [GetX](https://github.com/jonataslaw/getx) is utilized by more than 198,000 projects.

Such numbers reflect real-world usage and community adoption, offering a far better gauge of a package's influence and reliability.

For these reasons, I will go ahead and close this issue. If you have further thoughts, feel free to share. Thank you for your understanding!

[alok2811]

I would also like to take this opportunity to appreciate @jonataslaw and the incredible community around GetX for their commitment to providing a powerful and user-friendly state management solution. The adoption of GetX in over 198,000 projects is a testament to its impact and reliability. Kudos to the team and contributors for maintaining such a remarkable tool!