ICFP 2004 Programming Contest Results 30
jnagra writes "The results of the 2004 ICFP Programming Contest have been announced. First place is to a program in Haskell, second place is to a program in C++, and the judges' prize is to a program in OCaml. The ICFP contest is an annual contest to promote functional languages (although programs in any language are accepted) and bestows on the winners unlimited bragging rights."
Lighting division (Score:1)
From tfa :
Full Lightning Division Results
Place Points Team Team size Ant Approach Language Ant size
1 32868 RedTeam 7 L2 higher Perl 1263
2 32811 RedTeam 7 L1 higher Perl 1079
Perl scores again :)
Re:Lighting division (Score:2, Informative)
The judges just ran the output from the contestant's code through a simulator.
Ants (Score:1)
Visualizing the winners (Score:5, Interesting)
For those of you who want to see the winners in action, the Formicidae simulator from Ant Wars [ant-wars.com] can be used. It comes with a converter from the ICFP language to Ant Wars bytecode. To do so:
1. Grab a copy of Formicidae from the download page [ant-wars.com] .ant file: .antc files
2. Use the included convert.py on an ICFP
convert.py <filename.ant>
3. Run formicidae.[sh|bat], and provide a world (ICFP maps included in the worlds/ subdirectory) and two
4. Check ICFP Mode
5. Enjoy the match
Interestingly, this year's winning ant is already beaten by some of the competitors on Ant Wars, due to the fact that some Ant Wars ants have more aggressive defensive tactics that wind up decimating Dunkosmiloolump's ants that too brazenly approach their ant hill.
"Already?" (Score:3, Insightful)
Re:"Already?" (Score:3, Interesting)
I'm not trying to take away from the winning teams accomplishment, which is stupendous, but rather to point out that its interesting that there were no ants in competition which aggressively defended their bases.
Re:Visualizing the winners (Score:2)
The main tactic that is really effective against our ants is encircling our anthill. Luckily we often manage to collect more than half the food before an enemy has managed to do this. If I had time to improve our ant one of the main things I'd do is task some ants to act as a "tunnel"; this woul
What happened to Dylan? (Score:2)
Re:What happened to Dylan? (Score:5, Interesting)
It would be nice to win every year, but actually I'm pretty happy with a record that goes:
2001: 2nd
2002: 35th
2003: Judge's Prize
2004: 137th
I think this year's contest results had very little to do with how good your chosen programming language is. Instead it was all about how well you could get around the limitations of the ant instruction set and devise strategies for your ants to follow.
Sure, you could make a compiler that gave you a language with loops and subroutines and (very limited) variables and turned that into ant code -- and we did that -- but in the end you had to have something smart you wanted to get your ants to do. We spent a lot of time on making out ants explore the world and gather food efficiently (including raiding the opponent's nest), but our strategy for defening our own nest turned out to be inadequate.
For some reason the results say we used Perl, not Dylan. I don't know why. It's true that we had a quick&dirty ant assembler written in Perl that some of us used to play around with strategies while we waited for the proper compiler (written in Dylan) to be ready, but that wasn't used for the final submission.
We submitted the following programs all written in Dylan:
- world simulator library
- very fast simulator (2 sec for 100,000 rounds)
- slow simulator with OpenGL interface for visualization
- high level compiler for ant brains
Congratulations to the winners and we're looking forward to next year's contest!
The prize (Score:2)
That almost makes entering worthwhile
The annual irony (Score:2)
There should be a new prize: Most Ironic Judges' Comment For The Year. I think this year's odds-on favourite would have to be:
:-)
Congrats (Score:1)
I guess that actually using s functional programming language do help. Anyway, the winners deserve their unlimited bragging rights.
I`ll sure do better fo
Proud (Score:1)
Lisp results not very impressive (Score:4, Interesting)
It appears that winning depends more on choosing a good strategy than a good language and then implementing that strategy quickly and accurately. Choosing a winning strategy should be just as easy for a Lisp team as for anyone else, and helping you "discover" a good strategy is supposedly a strong point of Lisp. And as for implementing quickly and accurately, Lisp is said to have all sorts of advantages in that regard.
Even so, the number of teams that choose Lisp each year and the relatively poor showing of those teams implies to me that the amount of advantage Lisp provides is not as great as some (e.g., Paul Graham) would have us believe.
These contest problems are the sort of non-mainstream challenges that Lisp is supposed to be particularly good at, so I would expect more teams to choose Lisp to help them explore the problem and discover a winning strategy. Instead, Lisp appears to have, at best, average popularity among these programming language fans. I understand the overweighting in Haskell and OCaml given the name of the contest, but Lisp is roughly as functional as OCaml, so its lack of popularity puzzles me.
And of those who choose it, the results don't seem to imply that it gave them any advantage.
Yes, there are all sorts of ways in which the contest isn't a level playing field, but I'm still a bit puzzled at why the purported advantages of Lisp aren't showing up. Maybe they're real, but they don't appear to be very significant.
Re:Lisp results not very impressive (Score:4, Insightful)
One of the main advantages lisp has over languages such as haskell and ocaml is in self-modifying code, since in lisp, programs are data and it has dynamic typing. This feature probably just has not been useful in recent tasks.
The winning place entry, used haskell to implement a domain specific langugae via a monadic combinator library, something Haskell excels at, so they were definitly using the languages strengths.
Programming Haskell is truly a transcendent experience.
Re:Lisp results not very impressive (Score:3, Interesting)
It seems to me as though this would slow down the initial process of exploring the problem, as Paul Graham claims. Proponents claim that it makes up for that by making larger systems more reliable.
But these contest entries don't ever become large systems, and the extra slowdown initially wouldn't have time to pay off in the long run if the long run is only 24hrs
Re:Lisp results not very impressive (Score:2)
We definitely didn't really need the safety of wrapping side effects in monads, since we just used it for fresh labels. Didn't hurt
Re:Lisp results not very impressive (Score:2)
Personally, I find that the extra slow down in exploring data models and so on is paid back in less time debugging. (What a Lisp
Re: (Score:2, Insightful)
Re:Lisp results not very impressive (Score:1, Flamebait)
Still, a contest like this doesn't require much from the platform. You don't need to put the system into production or keep it maintained. You just have to solve a programming problem in a one-off sort of way that takes away a lot of the advantages that the most popular platforms have in more mainstream, enterprise-type problems.
Re:Lisp results not very impressive (Score:4, Interesting)
Yeah, that puzzles me as well.
Dylan is in essence a version of Lisp that happens to be written in a C/Pascal-like syntax instead of S-expressions. My friends and I have been doing pretty well using it, winning ICFP prizes in two of the last four years (2nd place in 2001 and Judge's Prize in 2003).
That's a single team's record.
There were 12 teams using Common Lisp and 9 teams using Scheme this year. I don't think we're any smarter than the other Lisp teams. In fact 7 of those 21 beat us this year, which is pretty much the same as our overall position in the field. So if our Dylan team is picking up prizes from time to time I don't know why other Lisp dialects aren't. It's a mystery.
Some reasons (Score:1)
Or maybe because OCaml and other strongly typed languages attract the most intelligent people who have time to attend (read: academics love typesystems and clean functional languages, academics are smart).
I strongly suggest that commercial Common Lisp vendors Franz and Xanalys should throw their programmers into next years competition. If developers of C
Re:Lisp results not very impressive (Score:2)
Funny, the winning team was a group of hobbyists and the team of INRIA guys (that included Xavier Leroy) finished 60th
Re:Lisp results not very impressive (Score:2)
No, I meant advantage, which showed up this year in winning the judges' prize, but your point about how badly they lost objectively is a good one. I hadn't even noticed until you pointed it out. Odd that the judges would find them so cool if the actual results of their "cool" approach were so poor....
Language of 2nd place entry. (Score:2)
Re:Language of 2nd place entry. (Score:2)
Re:Language of 2nd place entry. (Score:2)