Timeline for Picking an answer
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 3, 2011 at 18:05 | comment | added | Timwi | I wouldn’t mind you doing this, but I definitely would not recommend this as general practice because people forget and a longer answer stays accepted. It is a huge problem that the accepted answer can only be updated by the challenge setter, so it must only be done if the challenge setter is very likely to stay around for the (potentially unbounded) lifetime of the challenge. | |
| Jan 28, 2011 at 20:33 | comment | added | moinudin | @Chris That's great to know! I've never really looked into it. So the solution is to have more complex code golfs. :) | |
| Jan 28, 2011 at 20:07 | comment | added | C. K. Young | @marcog: Contrary to urban legend, GolfScript is not suitable for every golfing problem. For example, no one has written a GolfScript solution for Decision Tree code golf, and even if someone did, it's very, very unlikely to beat the Perl solution. (The easy-path solution requires floating point and symbols, neither of which GolfScript has.) | |
| Jan 28, 2011 at 20:05 | comment | added | C. K. Young | @dmckee: Good question. In the case of "stack overflow code golf" I went with "fastest gun in the west" (and certainly Anarchy Golf uses the same policy), but that may not be appropriate for every code golf challenge. Comments welcome. | |
| Jan 28, 2011 at 19:30 | comment | added | moinudin | Do we always want golfscript winning? See comments on this answer. | |
| Jan 28, 2011 at 19:24 | comment | added | dmckee --- ex-moderator kitten | This is certainly reasonable. What do you do in the event of a tie? Earliest? Highest voted? | |
| Jan 28, 2011 at 19:21 | history | answered | C. K. Young | CC BY-SA 2.5 |