Rosetta Code:Village Pump/Why not give a separate page to each language for each task: Difference between revisions
Rosetta Code:Village Pump/Why not give a separate page to each language for each task (view source)
Revision as of 03:34, 22 May 2018
, 6 years agomy opinion
(Why it copied a page when I signed it with ~~~~?) |
(my opinion) |
||
Line 5:
Why don't give a separate page for each implementation for each task?
Then you can discuss each implementation separately, watch only implementations in your favorite languages ignoring the others, include all implementations for a given language on one page. --Alexei Kopylov 16:03, 10 November 2017 (UTC)}}
:I don't think there's anything "official" about "one giant page of everything" versus "ten million tiny pages". It's just always been this way, although RC was much "smaller" back in them thar days.
:I think that most of the solutions have not been split off from the task pages because it adds an extra step to the whole process, whether looking for a solution, or adding a new one: rather than just ''task page -> scroll to desired language'', it would be ''task page -> scroll to desired language -> follow link to solution''.
:On the other hand, when comparing between languages, it's not unheard of (for me, anyway) to have 2 copies of the page open: one copy showing a language I know, the other copy showing the language I want.
:(There ''are'' some tasks here with implementations split off to their own pages, but those are few and far between. The only example that comes immediately to mind is [[Knapsack Problem/Visual Basic]], which is split off of [[Knapsack problem/Unbounded]], but I know there's more.)
:Just my opinion on the matter. You're always welcome to do as you wish, but don't be surprised if someone else comes along and makes changes you weren't expecting. -- [[User:Eriksiers|Erik Siers]] ([[User talk:Eriksiers|talk]]) 03:34, 22 May 2018 (UTC)
| |||