Talk:Semordnilap: Difference between revisions
Content added Content deleted
| Line 13: | Line 13: | ||
:Does this mean you like pages being really big and slow to load (and perhaps enough to crash some phone browsers)? If so, perhaps we could all include a copy of that same dictionary in each implementation on the task page? As an upper bound (99 bottles of beer has what... 200 implementations?) the task page probably would not get too much bigger than 40 megabytes... |
:Does this mean you like pages being really big and slow to load (and perhaps enough to crash some phone browsers)? If so, perhaps we could all include a copy of that same dictionary in each implementation on the task page? As an upper bound (99 bottles of beer has what... 200 implementations?) the task page probably would not get too much bigger than 40 megabytes... |
||
:That said, you also left out choices D), E) and F) (fetch dict from the url every time the code runs, or represent dict as a compressed blog, or do not bother implementing the task and let someone else do it). And, if we put some thought into it, we could probably come up with a G), H) or I) also. --[[User:Rdm|Rdm]] 12:28, 12 September 2012 (UTC) |
:That said, you also left out choices D), E) and F) (fetch dict from the url every time the code runs, or represent dict as a compressed blog, or do not bother implementing the task and let someone else do it). And, if we put some thought into it, we could probably come up with a G), H) or I) also. Maybe H) can be your "look up the big version in history"? --[[User:Rdm|Rdm]] 12:28, 12 September 2012 (UTC) |
||
Revision as of 12:28, 12 September 2012
Ruby Implementation
Do we really want literal copies of the dict file on the task page? --Rdm 13:58, 10 September 2012 (UTC)
I added a note to the submitters talk page and have chopped most of it from the example for now. --Paddy3118 17:13, 10 September 2012 (UTC)
What sort of a world is it where if someone says your dict looks big an Irish number chops it? From http://rosettacode.org/wiki/User_talk:Nigel_Galloway#Huge_Ruby_example I see I have two choices:
- A) modify it to read the dict from a file
- B) move it to a sub-page on its own
I choose C. Well B+ really. The + is, it finds a use for history, which I see relied on too often.--Nigel Galloway 11:53, 12 September 2012 (UTC)
- Does this mean you like pages being really big and slow to load (and perhaps enough to crash some phone browsers)? If so, perhaps we could all include a copy of that same dictionary in each implementation on the task page? As an upper bound (99 bottles of beer has what... 200 implementations?) the task page probably would not get too much bigger than 40 megabytes...
- That said, you also left out choices D), E) and F) (fetch dict from the url every time the code runs, or represent dict as a compressed blog, or do not bother implementing the task and let someone else do it). And, if we put some thought into it, we could probably come up with a G), H) or I) also. Maybe H) can be your "look up the big version in history"? --Rdm 12:28, 12 September 2012 (UTC)