I am asking this purely out of curiosity: Why is there a specific Stack Exchange for TeX? There is no HTML.SE, Python.SE, Java.SE, etc. It appears to me that all other programming languages (and scripting languages or whatever you call them) are covered by Stack Overflow. While TeX is definitely quite unique among programming languages and has a somewhat different user base, I am sure that argument would work for some other languages, too. Furthermore, other languages exist with purposes similar to that of TeX. So why did TeX get its own Stack Exchange?
2 Answers
To understand why TeX-sx exists we need to think about the overall network aims and how sites inter-relate. I think to do that we first need a little history. The 'main site' (StackOverflow, 'SO') is about programming in general. The first sites that were created in parallel to SO (SuperUser and ServerFault, SU and SF, respectively) both have distinct audiences from SO. Whilst there is undoubtedly some programming in for example running a server, the core expertise is not the same (though the same people may be active on both).
When the 'Powers' decided to allow more StackExchange sites as part of a network, they were looking for areas that have a distinct identity and which don't directly overlap with one another. In the case of TeX-sx, there is some programming going on but also a lot of other stuff. A lot of using TeX, LaTeX, ConTeXt, etc. is not about programming in the way someone on SO would understand it. Rather, we get questions about typography, document design, etc. as well as some about TeX programming. Even within the latter category, TeX programming is rather different to many other languages and it's hard to see a large degree of overlap with many (most?) regular users on SO.
The bottom line for the existence of any site on the network is having a distinct identity where the subject doesn't form a subset of the coverage of a larger site. Over the existence of TeX-sx we have I think found that our scope is different from SO, that many good questions here would be closed there, and that this site is therefore adding to the 'public good' (or however the Powers describe it).
Note that SO does have tags for TeX, LaTeX and BibTeX and that they do have some question on them. However, they need to be pretty tightly about programming to be on-topic for SO. For example, something like adjusting the formatting of a TOC would be on-topic for us but I think off-topic for SO as it's not really a programming question.
I would note here that there have been issues with establishing what one might call 'programming-related' sites on the network as there has been a lot of tension about the degree to which they might be viewed as a subset of SO. The Programmers site, for example, deals with what one might view as 'conceptual' ideas about being a programmer, and so is regarded as distinct from SO, but there are borderline questions.
-
Still, even if your reasons are quite good, I fail to see how they don't fit HTML as well. Many question about that are likely to be questions about good web design.– GausslerCommented May 24, 2015 at 16:16
-
9@Gaussler I can't answer for other communities :-) Seriously, I presume that most HTML queries on SO have a programmatic element (CSS, PHP, JavaScript, _etc.). I've no idea what happens about HTML design questions: perhaps off-topic for SO?– Joseph Wright ModCommented May 24, 2015 at 16:21
-
2@Gaussler HTML is eventually a markup language. Same can be said about TeX is a box stacking algorithm so should be in SO. It's a matter of specialization. The graphics and design part is already different networks graphicdesign.stackexchange.com and ux.stackexchange.com respectively. The remaining part is not that different than XML. And all those markup languages are on topic on SO. Hence they don't allow for a separate specialization. TeX is pretty special on that regard.– percusseCommented May 25, 2015 at 0:07
-
4@Gaussler You can discuss pseudo-philosophical questions on end, but the very concrete reasons Joseph mentions are always going to win the day: it fits the framework of Stack Exchange sites (it’s “legal”, in a way), it has a user base (viable), people find it useful, and, more importantly, someone did the actual job of making it happen in the first place. Comparing it with other programming languages is not helpful. Communities may happen spontaneously but actual actions usually don’t. Commented May 26, 2015 at 11:22
TeX - LaTeX followed the regular Area 51 proposal process to get where it's at today.
From the Area 51 FAQ:
How do I start a new site?
If your area of expertise doesn't already have a Stack Exchange site, propose it! Stack Exchange sites are free to create and free to use. All we ask is that you have an enthusiastic, committed group of expert users who check in regularly, asking and answering questions.
The creation of Stack Exchange sites is a community-driven process. That does not mean the majority of Area 51 users have to love your site idea. It simply means you have to recruit a community of users large enough so that questions get good answers quickly. Reach out to other experts to build support for your site; bloggers, enthusiasts, and support groups can all benefit from a world-class, canonical collection of expert answers to the hardest questions.
If the proposal wasn't going to work, it would have been stopped during this proposal process.
The following may also have been a consideration:
Should my idea be part of an existing site, or its own site?
In general, if a site makes sense as part of a bigger site, it's better to have one big site than a bunch of little niche sites. Site X should be subsumed by site Y if:
- Almost all X questions are on-topic for site Y
- If Y already exists, it already has a tag for X, and nobody is complaining
- You're not creating such a big group that you don't have enough experts to answer all possible questions
- There's a high probability that users of site Y would enjoy seeing the occasional question about X
For more information, read the post Merging Season on the blog.
While some of the above suggestions might be true, not all of them are. As such, there may have been enough incentive to break free. Our scope is also somewhat broader than purely programming. That's supported by the fact that TeX - LaTeX performed really well during the three-step graduation:
It showed there was enough interest to break free from the catch-all programming of Stack Overflow.
In my opinion, suggestions like Python.SE, Java.SE, HTML.SE would not fit based on the following criteria: "In general, if a site makes sense as part of a bigger site, it's better to have one big site than a bunch of little niche sites."
-
-
@cfr Yes, I'd seen that too, but I think they are really talking about 'small' sites: there have been a few in beta for ages.– Joseph Wright ModCommented Jun 5, 2015 at 12:50
TeX.SE
exists, but why there aren't similar sites for other languages?TeX.SE
people seem to be a bit different.