One of the most gratifying things about the "Game Jam" is that it puts all those flame wars over development environments to the test.
Most of the time, the people who stick to C/C++ tend to get demolished by the overhead of fighting the compiler. There are always exceptions - especially since the tiny scope means that code isn't the only bottleneck - but for the most part, it's shown very clearly that making games in a short period requires fast code iteration.
Most of the time, the people who stick to C/C++ tend to get demolished by the overhead of fighting the compiler. There are always exceptions - especially since the tiny scope means that code isn't the only bottleneck - but for the most part, it's shown very clearly that making games in a short period requires fast code iteration.
http://wolverinesoft.org/event/contest/48hourcontest7/
I'm pretty sure Sid used Unity, while the students are using all sorts of things: SDL, ClanLib, SFML, C#/XNA, Flash, and Java.