Talk:Solve a Hopido puzzle: Difference between revisions

← Older edit

Talk:Solve a Hopido puzzle (view source)

Revision as of 14:11, 12 April 2016

554 bytes added , 8 years ago

Let's see if I can edit pages now...

Rdm

6,951

edits

Revision as of 00:28, 12 April 2016 (view source) Rdm (talk \| contribs) (Oh, the injustice...) ← Older edit		Latest revision as of 14:11, 12 April 2016 (view source) Rdm (talk \| contribs) (Let's see if I can edit pages now...)
(One intermediate revision by one other user not shown)
Line 3: Quoting from this Rosetta Code task preamble: :''Knowing the kindness in the heart of every contributor to Rosetta Code, I know that we shall feel that as an act of humanity   '''we must solve these puzzles for them in let's say milliseconds'''.''▼ Gleaning from this, should the computer program entries display the (elapsed) time used to solve the problem (let's say), rounded up to <sup>'''1'''</sup>/<sub>'''10'''</sub> of a second?   -- [[User:Gerard Schildberger\|Gerard Schildberger]] ([[User talk:Gerard Schildberger\|talk]]) 04:04, 11 April 2016 (UTC) ▲''Knowing the kindness in the heart of every contributor to Rosetta Code, I know that we shall feel that as an act of humanity   '''we must solve these puzzles for them in let's say milliseconds'''.'' : Maybe. Personally, though - since no upper bound was specified - I'd be inclined to accept anything up to at least a million milliseconds. Or, if that quip was intended to be a constraint on programmer time, I'd personally think we should allow much, much higher than that. --[[User:Rdm\|Rdm]] ([[User talk:Rdm\|talk]]) 00:28, 12 April 2016 (UTC)▼ :: Well, from my ole mainframe days, when somebody used the word   ''milliseconds'',   it was always assumed to mean   ''sub-second''.   -- [[User:Gerard Schildberger\|Gerard Schildberger]] ([[User talk:Gerard Schildberger\|talk]]) 01:38, 12 April 2016 (UTC) ~~Gleaning~~::: ~~from~~I ~~this,~~was ~~should~~being ~~the~~a ~~computer~~bit ~~program~~tongue-in-cheek. ~~entries~~That ~~display~~said, the ~~(elapsed)~~guidelines ~~time~~for ~~used~~[[Rosetta_Code:Add_a_Task\|adding toa ~~solve~~task]] ~~the~~do ~~problem~~suggest ~~(let's~~that ~~say),~~we ~~rounded~~should uptry to ~~<sup>'''1'''</sup>/<sub>'''10'''</sub>~~favor ofwhat apeople ~~second?~~can ~~ ~~supply over overly strict requirements. -- [[User:~~Gerard Schildberger~~Rdm\|~~Gerard Schildberger~~Rdm]] ([[User talk:~~Gerard Schildberger~~Rdm\|talk]]) 0414:0410, 1112 April 2016 (UTC) ▲: Maybe. Personally, though - since no upper bound was specified - I'd be inclined to accept anything up to at least a million milliseconds. Or, if that quip was intended to be a constraint on programmer time, I'd personally think we should allow much, much higher than that. --[[User:Rdm\|Rdm]] ([[User talk:Rdm\|talk]]) 00:28, 12 April 2016 (UTC)