I recently asked a history question. The question was regarding popularity and was data-backed. There is a tag for history and there is a tag for popularity. But the question was closed as non-constructive. In one sense of the word constructive, no history question will ever be constructive. Why do we even have these two tags?
What is meta?
- Any Stack Exchange user can ask a question
- The community provides support, votes on ideas, and reports bugs
- Your voice helps shape the way Stack Exchange operates
Please don't use the existence of tags to justify asking questions that are clearly subjective or off-topic. Look at how the tags are actually used. Just glancing through the questions with those tags, it looks like one legitimate use of history is for questions that have to do with browser (or other application) history. The popularity tag doesn't have a tag wiki, but you can look and see that questions of the form "What's the most popular X" are frequently closed. Questions about popularity algorithms fare a little better.
The tag wiki for 'history' says, 'Do not use.' That seems pretty clear to me.
Other than that, this isn't a 'practical programming problem'.
The question did find a home on Programmers, however it still feels like a not constructive question. Although programming history questions are on topic on Programmers1, your question is based on a flawed assumption, which Thomas describes in detail in his comment:
There's no question that git is popular, however the data you present only speak about git installations on Debian. I'd strongly suggest you follow Thomas' advice and update your question accordingly. Even though it is on topic, it's already in trouble:
We've protected the question and added a post notice for long answers that provide some explanation and context on it, but you got to help us out a bit by making it a bit more concrete. There are two discussions in The Whiteboard (our main chat room) you might want to check out:
If the question gets closed, it will be automatically locked as a rejected migration, which means that you won't be able to edit it, so... if you are going to update it please do it now.