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

expand, my opinion (ain't broke, don't fix it)
(New discussion page about subpages for long examples)
 
(expand, my opinion (ain't broke, don't fix it))
Line 1:
Recently, examples have been moved to subpages of tasks (ex: [[Closest pair problem‎]] and [[Closest pair problem‎/SmallTalk]]). The reasons for this are so that pages don't get too long for some browsers to open when editing and so that the server won't get overloaded if one of these tasks becomes popular (bandwidth may also be a concern). It has been pointed out that this solution may be counter-productive to the goals of the site. This idea and possible alternate solutions should be discussed here. --[[User:Mwn3d|Mwn3d]] 21:44, 8 January 2010 (UTC)
 
* The “requirement” I have in mind is: that no effort should be needed for one to be exposed to examples in ''all'' languages while browsing a task. As far as I know, the most efficient way to do this is to have all the examples on one page.
: I agree that there are practical limits, but I disagree that we've reached them, and e.g. [[Playing Cards/E]] (which is one of the examples [[User:Glennj]] split off) is surely not too long. Regarding “too long for ... editing”, are you referring to the automatic 32K notice Wikipedia puts up? As far as I know, we have lots of pages that long and no one's complained. I agree that length can be a technical and/or usability problem eventually, but I feel that we have not reached that point. --[[User:Kevin Reid|Kevin Reid]] 22:25, 8 January 2010 (UTC)
 
<!--
 
* Your alternate proposal here ... --~~~~
 
-->