4 ms·
One reason is scalability and distributability, though that doesn't apply to smaller wikis. There have been attempts to load Wikipedia's full history dump into
by _delirium 16y ago
One reason is scalability and distributability, though that doesn't apply to smaller wikis. There have been attempts to load Wikipedia's full history dump into a git repository, but git doesn't seem to be able to handle that volume of stuff (and frequency of edits) nearly as well as Wikipedia's current setup of distributed MySQL servers and custom code does.
- amackera 16y agoThough you make valid points, the scale of a typical Github wiki is nowhere near the scale of Wikipedia.
- _delirium 16y agoYeah, and the biggest edit bottleneck---git's serialization of updates---is probably not an issue either, since it only applies to wikis with a lot of pages that get a lot of edits. (By serialization of updates, I mean that, afaik, git can't apply two patches simultaneously, even if they're to completely disjoint sets of files; it has to apply one patch, then the other. That'd be like using a db that requires you to lock the whole db to do any writes. High-volume wikis instead will only lock the rows for the particular page they're editing, so edits to other pages can happen simultaneously without blocking.)
- philwelch 16y agoWikipedia has zero branching and doesn't require atomic commits across a range of articles. It's a mismatch for SCM.
- avar 16y agoWikipedia has branching now in the form of "approved revisions", and it has a lot of long standing TODOs like annotate that would be solved by a SCM. The storage backend for articles is its own mini-scm with a revision table + text storage. There's no reason why a Git based backend would be any worse of a fit for a wiki.
- philwelch 16y agoAre approved revisions really a branch or just a tag somewhere in a linear version history? With branches you can have n parallel branches, whereas with Wikipedia it seems--though I may be wrong--that you just have one version history, with one or more revisions within that history flagged as "approved". (Having n branches of a Wikipedia article would be frowned upon, since the community decided in the early days that you can't fork an article--that only gets in the way of building an authoritative and neutral version--though it has been argued in the past that having multiple forks on controversial topics, each written from a particular point of view, would be more informative.) Also, Git-style branches only make sense as alternative branches of the entire repository, which doesn't exist in Wikipedia terms because you can't atomically commit changes to multiple articles together. It's more than possible to have a wiki with branching and cross-page atomic commits--it's even a good idea. But it wouldn't fit Wikipedia. And to get around the atomic commit problem (given the massively concurrent editing that happens on Wikipedia) you'd have to essentially have one Git repository per article, at which point you're probably better off with a different type of backend.
- avar 16y ago> Are approved revisions really a branch or just a tag somewhere in a linear version history? A Git branch is just a different head, but no, those things don't have divergent histories. They're just moving tags. Anyway, semantics aside I meant that they're doing things now that maps effortlessly to a scm. > Having n branches of a Wikipedia article would be frowned upon Not if it was well supported. Saying "hey, I modified the article in my own private branch, check it out and merge it if you want" would beat a long argument on a talk page any day. Branch support doesn't need to entail multiple publicly accessible (as in the stuff normal readers see) versions of articles. > Also, Git-style branches only make sense as alternative branches of the entire repository What? No, they'd also make sense even if there was one Git repository per page. > you'd have to essentially have one Git repository per article, at > which point you're probably better off with a different type of > backend. We won't know until we try, will we? But there are lots of advantages to using a well understood and simple data format with multiple implementations over a custom schema, but of course a custom format has its own advantages.
- avar 16y agoThat's comparing apples to oranges. A proper comparison would be to create an individual Git repository for each article, not a giant repository containing all the data in Wikipedia. That would work more like the current MediaWiki storage backend does, and would probably do delta compression of old revisions more efficiently than the current homebrew code.