A "Nimble Canonical" category makes sense, but many other repositories (npm, 
IDE marketplaces etc.) crowdsource the decision of what's "canonical" by 
showing usage numbers and offering a rating system. If nimble had this, maybe 
even with a more differentiated rating system (compliance with best practices 
and conventions, performance, API cleanliness) maintained by curators... But 
I'm dreaming. 

Reply via email to