56
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Oct 2023
56 points (83.3% liked)
Programming
17022 readers
230 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I don't think looking at the star counts makes you automatically a bad developer, but it certainly shouldn't be the only thing you look at. If you're unfamiliar with libraries solving a specific problem, I don't see anything wrong with looking at them from the most to the least popular. Popularity can also be a sign of community and therefore more likely continued "support"
Github offers the
Insightstab on every repository that provides you with actual data in those points. There are countless repositories out there that have thousands of stars and literally on person contributing to it. If you go by stars to sway your verdict, you are simply to lazy to do your due diligence which in turn makes you a bad developer.I'm literally writing that it's not what I am doing, so please don't talk to me about laziness when you can't even read a three-sentence long comment.
Your claim is that there is value in using a metric that has zero meaning and validate your own negligence in claiming that it makes your choice better than random through popularity. I claim this is lazy and negligent. Please tell me what I misread.