Return to Answer

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.

The list of questions confirms something I said on Area 51:

The best site for Vi/Vim questions is Stack Overflow. If you are already interested in asking and answering questions about this family of editor, you really owe it to yourself to follow that filter for a few days. ... Many of the [questions] here seem perfectly topical on Stack Overflow.

Each of the questions on Stack Overflow that you linked to share a number of characteristics:

1. Were answered to the asker's satisfaction (as evidenced by being accepted) the same day they were asked (often within minutes).

2. Have multiple upvoted answers. (In fairness, the second answer to this question was deleted after being upvoted.)

3. They remain open to new answers. If the answers insufficient, anyone may freely add an improved answer.

4. Have thousands of views.

5. Are asked on a site with thousands of users who can reasonably be called vi and vim experts.

In order to justify moving any of those questions to a new site, we'd want to know that the new site is a better home than Stack Overflow. According to objective criteria of successful Q&A, it would be irresponsible to move any of these questions. The only criteria that would indicate migrating these questions to this site is fragmentation of the topic.

So let's talk for a moment about fragmentation. It's not enough, really, to move all the questions and answers into one place; preventing fragmentation of a topic requires moving all the askers and answerers into one place too. 4 and 1/2 years ago, a site for TeX and LaTeX was added to the network. To this day, the [tex] and [latex] tags get 3 questions a day on Stack Overflow. In every case I can think of, splitting programming topics off of Stack Overflow has made fragmentation worse. It turns out many programmers would rather ask and answer questions on the site they already use. The "home site" phenomena also explains why there is still an active [ubuntu] tag on Unix & Linux.

In the last few years, we've been trying to get in the habit of talking less about topics and sites and more about communities. I want to acknowledge that the Vi/Vim community does exist and has a right to exist on our network. The same can be said about the C++ community and the Go community and the Fortran community. I think the better way to think of a site, especially Stack Overflow, is as a great city with many different types of people working together. People live in cities, with all their problems, because it's better to work with a diverse group than not. The same thing can be said of programmers on Stack Overflow.

In that analogy, splitting off a site is not so much an acknowledgement that a community has value as a ghettoization of the topic. Now that I say it, that seems a bit harsh. But spinning off a new site implies that the whole depth and breadth of the topic was not welcome in the original community. The SO questions you've listed don't demonstrate anything of the sort. I'm left wondering who is served by this site who would not be served by leaving Vi[m] questions where they are now.