Rosetta Code:Village Pump/Long examples: Difference between revisions

Line 6:

::: I too don't like splitting up long pages unless absolutely necessary. What is too long might depend on a lot of factors, but I would think that a page that is still usable on, say, a netbook should be OK - it is new, but low-powered hardware. --[[User:Paddy3118|Paddy3118]] 05:49, 9 January 2010 (UTC)

: (Warning: Pointless general observations ahead) Some of those notices are driven by resource availability, and when pages exceed the final size limits, things get ''nasty''. My first attempt at building the system that's now satisfied by the "tasks unimplemented in language X" pages was to build a full table cross-referencing languages and tasks. MediaWiki OOM'd when I tried uploading the resulting table wikicode, which weighed in at over 1MB.

:

: Yes, 1MB is a ''huge'' amount of data to ask to be rendered as HTML, but the example shows that resource limitations are very real. The problem with the task pages as they currently exist is that while some pages, flattened, consist of a small number of large examples, some pages, flattened, consist of a very large number of small examples. Both of those scenarios lead to pages that choke MediaWiki. Without pruning out languages, it becomes difficult to chose which of the latter examples to break out into subpages. Some of it ''may'' be able to be worked around with page transclusion, though. There will still be upper limits, but it's something to try. At some point, it may be possible to paginate overly-long transclusions, but that's a bit of a dream, at this point. --[[User:Short Circuit|Michael Mol]] 06:28, 9 January 2010 (UTC)