Talk:Code golf

Done

Ahh I was just about to do this exact redirect then I saw it was already done! Neddyy (talk) 11:56, 4 February 2011 (UTC)[reply]

Examples?

We need examples of Code golf. Zbuhman (talk) 04:49, 15 October 2011 (UTC)[reply]

- phpGolf: http://phpgolf.org
- CGolf: http://shiva.norgrind.net/~tom/cgolf/
- CodeGolf (Perl, Ruby, PHP, Python): http://codegolf.com

Echofish1 (talk) 19:49, 28 November 2011 (UTC)[reply]

GolfScript?

Maybe mentioning GolfScript would be a good idea? Echofish1 (talk) 08:14, 29 November 2011 (UTC)[reply]

Agreed - added a section on languages designed for golfing, including Golfscript and Flogscript. I think there are a couple of others, like goruby, but I don't know enough about them. Maybe someone else can improve. Also, there is no existing Golfscript article page, so I started one in my user namespace. Not sure if it'd be considered notable enough for Wikipedia, though. Destynova (talk) 14:09, 19 April 2012 (UTC)[reply]

The mention of Flogscript should probably be replaced with a more modern golfing language, like Jelly or Brachylog. 69.218.220.5 (talk) 10:16, 25 April 2019 (UTC)[reply]

Brevity

Golfing is usually not about implementing a certain/specific algorithm but merely to find the shortest program that solves a task. It is not uncommon that there are several algorithms for the same task where participants will choose the one which can be implemented with the fewest key stroke. It is also not uncommon that slower algorithms require less key strokes. -- Feuermonster (talk) 21:44, 26 January 2013 (UTC)[reply]

Impact on the craft and discipline of programming

Has anybody studied the impact of code golfing on important metrics of programming, such as PQRST (Precision, Quality, Readability, Speed, Testability) etc?

Some thoughts:

A sceptic might suspect that the impulse to write ever more compact (i.e. space-efficient) code could become habitual, and spill over into "real" programming work; and that if it did, it would almost inevitably lead to detrimental effects on, in particular, readability and hence on both the code's functionality and the maintainability of the code legacy of such (sadly, misguided) programmers.
An optimist might consider that the programmer's desire to write better code would spill over into "real" programming work; and lead almost inevitably into an improvement in the professionalism of all such programmers, such that their work would be functional, efficient, readable and maintainable!

One might argue either way - or differently - but does anyone have any concrete evidence on this issue?

yoyo (talk) 04:19, 17 June 2014 (UTC)[reply]

Dedicated golfing languages

It might be time to create a new page for dedicated golfing languages since as of now there are at least 4 of them that are used on a regular basis on golfing sites. -- 2A02:120B:C3DE:7AA0:112F:9629:441E:9564 (talk) 15:55, 20 September 2014 (UTC)[reply]

External link

Last external link doesn't need black text on end, right? — Preceding unsigned comment added by 94.254.148.29 (talk) 13:48, 23 July 2018 (UTC)[reply]