Talk:Semordnilap: Difference between revisions

→‎Ruby Implementation: Why should ~200K of repeated data remain?
(→‎Ruby Implementation: Why should ~200K of repeated data remain?)
Line 14:
 
: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)
 
:Hi Nigel, as I tried to explain, we try not to have overly large examples, and if you look around, those measures I outlined are used by others when they have large examples to post or others may create sub-pages for them without the snide remarks.
:There are other examples and tasks that use the dictionary and yours is the first example that chose to stick the whole dictionary in the source code. The program you wrote may work, but that is not the only consideration for its inclusion, we also like to have a main task page that doesn't put undue load on browsers and ~200K of source I thought was too much. (The line length was excessive too). --[[User:Paddy3118|Paddy3118]] 16:47, 12 September 2012 (UTC)
 
:P.S. If you think the site makes the rules up as it goes along, then in essence you are correct. The users are encouraged and empowered to make RC 'better'. We may struggle at times, but I think Rdm and I made a reasonable request, and made an appropriate change. --[[User:Paddy3118|Paddy3118]] 16:47, 12 September 2012 (UTC)
Anonymous user