Thanks. Please note that I do admire the passion you have for your vision. Although we ended up having very different opinions on which direction to go, I appreciate that our debate was always level-headed and civil, whether it's out here in the open forum, or in our PMs to each other. If only we have more people like you in terms of Internet discourse.
Anyway, let me summarize the situation (do correct me if I have misunderstood anything). The vision you have is a comprehensive database of CLI tools that can be sliced-and-diced by a large number of filters (I consider badges and use cases to be a form of filter). Although that vision is nice, I consider it impractical and not very useful. What I think would be more useful would be a form of what we have currently for the main DB, with minor changes to deal with the nature of CLI tools.
I think the gulf between the two destinations is simply too wide to be bridged, so the most obvious outcome facing us is to terminate the experiment. The next question is how to proceed with this.
First, the numbers. I did a quick check of the CLI database, and overwhelmingly the entries were vevy's contribution. There were very few other contributors:
- achadwick 1
- Achille 1
- Hydaral 1
- I am Baas 2
- Midas 1
- ozok 1
- Ruby 2
- stahlworks 1
- SYSTEM 3
- TP109 1
There are a couple of questions before us now:
- vevy, what is your preference in terms of your database entries? From your previous comments, I think it is unlikely that you want any form of the database to go live at this stage, since it will fall far short of your ideals. Is that right?
- Assuming vevy wishes to reduct all his current entries, do we still want a live CLI site? Is there enough interest to make it viable?
In terms of some of the minor enhancements that we've added to the CLI site (most of them vevy's request, I might add), I do plan to backport a few of them back to the main site in due course. So at least we have made some gains there.