Proposal: Vi and vim

Vim already falls in the scope of at leat SuperUser & StackOverflow; who do we need a separate StackExcange site?

  • 3
    See also: web.archive.org/web/20141013210740/http://… – Doorknob Nov 27 '14 at 14:32
  • 5
    @Doorknob Thank you ... Aside from that I disagree with the reasoning, removing such a proposal & all discussions attached to it from the site in its entirety is even more silly ... I did search for it, and simply assumed it didn't exist. – Martin Tournoij Nov 27 '14 at 14:36

Number of questions with the tag Vim & Vi:

StackOverflow: 15260, 1126
SuperUser: 2624, 181
UNIX: 742, 164
ServerFault: 31, 79
Programmers: 23, 5
TeX: 164, 0

There are at least 3 different places with a significant number of Vim/Vi related questions, and 3 sites with some questions. There are probably some other sites with Vim/Vi related questions as well.

This the same reason why an Emacs, TeX, or Ubuntu SE exists, all 3 SE sites fall within on the border between StackOverflow & SuperUser, and questions are scattered over those 2 (and some more) sites. Having a single resource would be an added advantage.

  • 4
    *emacs :( But as a fervent user/defender of the faith in the Church of Emacs, it's really only fair that we have a Vi(m) site as well. The growth we've seen from Emacs.SE – and the material I've learned – is evidence to its usefulness. – Sean Allred Dec 20 '14 at 1:14
  • 7
    This data cuts both ways. The other way to look at it: Vi questions can be asked on a number of sites already, so why add yet another site? – Jon Ericson Jan 24 '15 at 2:25

Just a copy/paste of my answer from the previous discussion:

I'd say that the strongest argument we have in favor of a separate Vim site is that Vim Q&A is already quite fragmented across the entire network.

First of all, almost any question at all about Vim can fit on either Stack Overflow or Super User. Indeed, I've searched for Vim questions on SO before only to finally find an answer on SU. This is a Bad Thing™.

Furthermore, fragmentation means you're not reaching your full potential audience. What if I have a question about Vim-LaTeX on Ubuntu? I only eventually decided to post on Ask Ubuntu because it got more traffic. This is also a very Bad Thing™. The people over on Tex - LaTeX don't get to see my question, so it gets less of a (specialized) audience. People from TeX - LaTeX might have the same problem, but give up because they can't find it on that site. Less questions + less answers = less happy unicorns.

Also, it's not as if I'm the first to bring this up. But yeah, any argument you can make against Vim hurts your Emacs site, and anything good you say about those Emacs people over there applies equally to us too.

  • 1
    The trouble with the fragmentation argument is that it doesn't tell us if a unified community exists; it tells us that several groups of people use the same tool. Someone could propose a Bash site and point to 46,615 questions on SO, 5,225 on Unix, 5,140 on Super User, 2,626 on Ubuntu, 2,067 on Server Fault, and even 453 on Apple. But I doubt that a nascent community is waiting for us to build a Bash.SE for them. Instead, I suspect that most bash enthusiasts are happy to ask their questions on one of the existing sites. How do we know that vi users aren't equally happy? – Jon Ericson Jan 26 '15 at 2:22
  • 1
    @JonEricson the primary difference is the bash users haven't repeatedly tried to organize themselves and actively ask for their own community. I would agree that the bash community isn't waiting but its not so easy to make the argument that the vim community isn't (given the repeated proposals and the reaction to having not been given private beta last time). – casey Jan 26 '15 at 17:41
  • 2
    @casey: Agreed. What I worry about, however, is that some of the folks committing to this proposal aren't doing so because they are in need of a site to get their vim questions answered (there's plenty of those) but because of a sense of fairness. In terms of Q&A (especially on Stack Overflow) vim looks a lot more like bash than emacs. – Jon Ericson Jan 26 '15 at 18:04
  • @JonEricson that is a fair concern. A vim site wont succeed out of spite over the existence of an emacs site or treatment of past vim proposals. – casey Jan 26 '15 at 18:07

Obligatory caveat: I haven't discussed this with the rest of the Community team. The opinions below are my own and I reserve the right to change them without notice. Satisfaction guaranteed or double your money back. (Offer void for internet transactions.)

I think 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. I just can't help comparing these actual questions to the example questions on this proposal. Area 51 example questions rarely make good questions on beta sites, but many of the examples here seem perfectly topical on Stack Overflow.

To tackle the elephant in the room: Emacs set the precedent for splitting off programers' editors from Stack Overflow. Before the private beta, I proposed some criteria for spinning off topics. A topic split can only be successful if the new site reaches a new audience; cannibalizing an existing site is both inefficient and detrimental to people seeking answers. TeX/LaTeX was a good candidate because so many TeX users (mathematicians) do not consider themselves programmers. The same can be said for the various CMS sites.

After 122 days in beta, we have enough data to see if the Emacs spinoff was successful. Before the private beta, there were ~7 Emacs questions per day across the network. As of today, the rate is ~5 q/day with the emacs tag. However, Emacs.SE is getting nearly 12 per day. Something like 40% of those questions (by my estimation) would be off-topic on any other site on the network. A reasonable guess is that splitting off the topic added somewhere between 3 to 10 Emacs questions a day to the network.

Do those questions get answered as quickly and as well as they would on Stack Overflow? The data suggests they are:

Tag/Site         questions views score closed answers accepted answer TTA
                          median   avg      %     avg      avg      %   *
-------------------  ----- ----- ----- ------ ------- -------- ------ --- 
[elisp]               3088   165   3.2    1.8     1.9     77.3   96.8  56         
[emacs]              12161   234   3.7    3.3     1.9     68.2   93    70
Emacs                 1564    77   4.3    1.6     1.6     65.3   91.7  69 

It turns out that the [emacs] tag is not particularly well-served compared to other tags in terms of time-to-answer (TTA):

Stack Overflow     8684846   243   1.6    4.4     1.7     57.1   88.3  24

Which brings us to the topic at hand:

[vi]                  1157   275  11.3    6.7     2.8     71.5   95.9  10         
[vim]                15642   254   5.2    4.4     2.1     73.1   95.8  23          

Questions in the [vim] tag are answered as quickly, more often, and better than the typical tag. Plus those answers are viewed by more people. The data strongly suggests that Vi/Vim askers get the answers they need on SO. I'd be shocked if Vi.SE could improve on that.

However, I'm willing to give this proposal a shot at private beta. Partially, I'm encouraged by the momentum of commitment:

133 committers in just over 24 hours.

As I mentioned on the Emacs proposal:

The first couple of pages of committers by reputation shows these are folks who are very comfortable with our network, but still want a [dedicated site]. These are people who are voting with their feet. It seems very likely that our existing sites are not meeting their particular needs.

Like the Emacs committers, a good percentage are active on other sites:

committers active in
65.4% Stack Overflow
24.1% Super User
20.3% Unix & Linux
18.0% Meta Stack Overflow
17.3% Meta Stack Exchange
15.8% Ask Ubuntu

I still think this proposal is a waste of time and effort. Maybe I'm close-minded and biased, but I don't suspect that a site for Vi will draw a different audience than the one we already have on Stack Overflow. There will no doubt be plenty of questions in the private beta, but I'm going to be looking for questions that can't be asked on other sites. If Vi.SE succeeds, it will be by addressing questions that have nothing to do with programming.

  • 1
    I don't quite understand your last sentence and a half: "I'm going to be looking for questions that can't be asked on other sites. If Vi.SE succeeds, it will be by addressing questions that have nothing to do with programming." Does Emacs.SE have many questions that have nothing to do with programming? Or does that not matter either (1) because the Emacs.SE beta generates more questions than the tag on SO would or (2) because Emacs questions are not on-topic on as many other sites as Vi[m] questions (or both)? – Earthliŋ Jan 24 '15 at 2:34
  • 2
    @Earthliŋ: We were pretty explicit in the Emacs private beta: focus on non-programming questions. When we looked at Emacs questions, we excluded all the ones that could have been asked on Stack Overflow from our consideration. Any Vi/Vim private beta will be evaluated the same way. – Jon Ericson Jan 24 '15 at 2:36
  • 3
    What sort of programming? A question about some facet of vim's language that came up while writing a plugin should be on topic here. Just as QML questions are on topic on AU and scripting is on topic on U&L. – user118877 Jan 24 '15 at 10:43
  • 2
    You know I rather agree with you. I can see where emacs could form a site and where vi/vim might not be able to quite make it. I see where vi/vim is probably working just fine elsewhere on the network. But what keeps me coming back to this proposal is the hope that I can become part of a community centered around the use of vi/vim. A place where I can learn from the experts and even share my somewhat limited knowledge. Something to create and build a community on. A few tags scattered across the network is not a solid (nor easy) base to build this on. – Seth Jan 24 '15 at 19:49
  • 3
    "I don't suspect that a site for Vi will draw a different audience than the one we already have on Stack Overflow." I don't participate on Stack Overflow. I don't have the time nor expertise. I would however participate on a vi site, and I know others in the some position. I think you suspect wrong. – Seth Jan 24 '15 at 19:51
  • @muru: Those questions will certainly be ontopic. That's not the issue here. What is at issue is whether a Vi/Vim site brings anything new to the network. A site that just hosts questions that Stack Overflow, Super User, and Unix already accepts makes the internet just a little worse for people to find answers about Vi/Vim. – Jon Ericson Jan 25 '15 at 7:00
  • 1
    @Seth: I'm often wrong and would be delighted to be wrong this time. A vibrant site about the vi-family of editors would be a great asset to the internet if it doesn't undercut existing sites. It's hard to imagine that a dedicated site could improve on the speed and quality of answers. But perhaps you are correct that a community will form around a Vi/Vim Q&A site. That's exactly why I'm inclined to let y'all try. – Jon Ericson Jan 25 '15 at 7:12
  • I would be inclined to agree with you about SO being the best site for vi/Vim questions if it weren't for that fact that SO seems very conflicted about whether it actually wants Vim questions. It's not hard to find Vim questions that have been closed as "off-topic" and the guidelines about what is on-topic have recently been changed in way such as to make it clear that many Vim questions are not on-topic: meta.stackexchange.com/a/130810/146632 – Rich Feb 9 '15 at 10:50

There was a large (now deleted) discussion of this on the old Vi(m) proposal. The closing of the proposal resulted in the most downvoted announcement on Area 51 (this announcement has also been deleted), with many answers arguing against the closing.

Still, the motivation for closing a fully committed proposal remains a mystery for me, but I would like to quote the reasoning from this answer, which discusses why the Coffee proposal might be granted a site of its own, although there is already "Seasoned Advice" for "Food & Cooking experts"

A network (or group of sites) isn't always worth exactly the sum of its parts. If there is an audience out there we are failing to attract by lumping all these subjects under one umbrella (a culinary site), then splitting that subject off into a site of its own may actually result in a net gain overall. But if we're simply splitting apart one site to create two — for, essentially, the same audience — then that would be a poor allocation of subject space and completely undesirable… and we would take appropriate action.

But the only way to know for sure is to give the site a try. And so far the subject of "Coffee" has passed the first trials of Area 51: gauging interest.

It seems to me that the same reasoning may apply to granting Vi(m) a (try at a) site of its own, since I think there exists a different audience for Vi(m), which doesn't fit under the umbrella of StackOverflow users. (I assume that this reasoning also supported the creation of the Emacs proposal.)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .