yes, I practice this. however its quite difficult, as most package sites dont surface this information. so I end up comparing the go.sum of god knows how many packages:
of course its a balancing game, because if you can add one import and save 1000 lines of code, it might be worth it. I am probably the outlier though. I would guess most people just find the module with the most stars, and turn off their brain after that, regardless if that module is a bloated piece of crap.
Comments
yes, I practice this. however its quite difficult, as most package sites dont surface this information. so I end up comparing the go.sum of god knows how many packages:
https://github.com/3052/google/blob/main/go.sum
of course its a balancing game, because if you can add one import and save 1000 lines of code, it might be worth it. I am probably the outlier though. I would guess most people just find the module with the most stars, and turn off their brain after that, regardless if that module is a bloated piece of crap.