You perform a cost/benefit analysis on each of the approaches, and choose the approach that has the highest overall benefit/cost ratio.
In the case of competing libraries that perform essentially the same function, the best, easiest and quickest way to perform that analysis is to stand up small prototypes using each library. Which one to prefer should then become abundantly clear.
Possible cost/benefit considerations for libraries:
- Maintainability
- Ease of use
- Adequate documentation
- Learning curve
- Overall performance
- Buy vs. Build
... etc. Note that many of these considerations can be somewhat subjective.
Whether it's a hobby or a career doesn't matter. You will (and should) use the same process if you decide to continue your explorations into an actual career.
Alternative decision-making strategy: Choose the one you like.
