Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re^2: The Lighter Side of Perl Culture (Part III)

by eyepopslikeamosquito (Chancellor)
on Jan 24, 2005 at 08:01 UTC ( #424522=note: print w/replies, xml ) Need Help??


in reply to Re: The Lighter Side of Perl Culture (Part III)
in thread The Lighter Side of Perl Culture (Part III): Obfu

eyepopslikeamosquito faints. Nice work and sorry about the crack about Python's indentation rules. ;-)

Silly me, never thought to google for "Obfuscated Python". Won't make that mistake again. Researching the next installment, googling for "Perl Golf" gives me SourceForge Perl Golf as expected, while googling for "Python Golf" gives me ... a nice pair of ladies golf shoes. Don't tell me Pythoneers play golf too? Update: they do now apparently (see also PyContest).

Update (2011): Surprisingly, Python has now become, by far, the most popular language in which to play competitive code golf, as described in The golf course looks great, my swing feels good, I like my chances (Part IV) (in the "Which is the Most Popular Golfing Language?" section).

  • Comment on Re^2: The Lighter Side of Perl Culture (Part III)

Replies are listed 'Best First'.
Re^3: The Lighter Side of Perl Culture (Part III)
by Anonymous Monk on Jan 28, 2005 at 03:38 UTC
    Golfing in Python is rare because good python code tends to be not very much longer than the shortest possible version. There's also less in the core than Perl and far fewer side effects/context-dependencies.

    That said, you occasionally see golfing - for example Wypy was golfed down from about 21 lines - and Java converts posting Java-ish Python to comp.lang.python tend to receive suggestions for how to reduce their code by about 70%... ;-)

    yrs Disciple-of-another-Faith-ly, -T.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://424522]
help
Chatterbox?
[choroba]: Discipulus I was taught so by a Londoner
[shmem]: Corion: very clear case of missing sequence number
[Corion]: shmem: Yeah. I guess they have a sequence number but distribute the events across threads or machines or whatever.
[karlgoethebier]: choroba: another chapter of "Learning English At The Monastry"?
[shmem]: Corion, well then... next issue, sequence number not a shared resource :P
[Discipulus]: shmem i'm searching it.. but failing i was sure was in Re: Let's Make PerlMonks Great Again! -- suggestions and dreams
erix recommends Vanished Kingdoms
[Corion]: shmem: Yeah, something like that. Not that that would be a solved issue. Simply process all events that come in from a single interface sequentially. Ah well.
[Discipulus]: their

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (11)
As of 2017-05-23 08:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?