[Suggestions for 0 A.D.]

I badly need the possibility to limit the frame rate. I'm getting ~60 fps when I start playing, but as I play and my laptop heats up, it drops rapidly. If I could limit the frame rate I could probably play much longer.

You can limit the processor usage per-process:

http://www.cyberciti.biz/faq/cpu-usage-limiter-for-linux/

You could even have another command running to go full throttle after two hours.

[[DISCUSSION] Regenerative Resources]

If it's decided to use a non-linear regeneration rate for any food (or perhaps even in the linear case), it would be nice to note it somehow during gameplay. Some sort of report when clicking the fish saying "Current Regeneration Rate: 2" (I guess the unit is something like "food-per-turn" or "food-per-100 turns" or whatever, but I don't know that a unit is important...), or "Constant Regeneration Rate: 3". If it's contant, it could just be placed in the gameplay notes, but if it's non-constant and non-linear, it would be nice to know what's going on for those cases when, at the beginning of the game, I don't have much else to do, and I would like to optimize *something*, so I may as well micromanage some food-gathering.

[C++11 Migration: Discussion]

To integrate properly and straightforwardly with distro package managers, we should only use the default compilers in the distros we care about, which I think currently means GCC 4.6 (for Ubuntu 12.04).

Also, updating VS would be a bit of a pain for e.g. me, since I use Visual Assist (and can't stand VS without it) but only have a license for a VS2010 version. And the VS2012/2013 IDEs have a terrible UI design (uppercase menus, really?). Those aren't blocker issues, but they are downsides.

We care about Ubuntu 12.04? I don't think Canonical does... The next LTS is out and has been for a while. I'm a very late adopter, and I'm already on 14.04 :-).

[C++11 Migration: Discussion]

Is a 1-3% improvement worth the change ?

Definitely not. This change, as I see it, has nothing to do with performance increases (except those that come with the new version of Spider Monkey).

The reasons I see for going to c++11:

Because we use c++03, and c++11 is the next version of the standard. It's been a few years, the language is widely supported now, and has shown itself to be a major advancement. For instance, any team that's still using RCS should probably consider moving to a newer VCS just because RCS is old and has been greatly improved. It's not the *best* tool for *any* job, and is in

So that we can take on the new version of Spider Monkey. If Spider Monkey went Clang-only, we would have to consider more closely, but c++11 is an obvious place to go from where we are (c++03).

C++ has loads of new features that are very useful to us covering usability: lambda statements, universal initialization, auto, "for-each" for loop syntax; optimizations: move semantics (including "perfect forwarding"), right-hand references, "standard" threading support (this may not be an optimization over pthreads, but I think it's good); and other functionality: POD types expanded, random number generation is improved.

[EDIT]

Oh yeah, c++11 is largely (completely?) backward compatible. Compiling a c++03 program as c++11 should have no problems, and any new warnings that show up will only serve to improve the code.