>>32
If you are doing simulations, then you will want to be able to perform calculations as quickly as possible. One thing that is nice about seeples is that you can set up your data structure, and then perform your calculations on it without invoking any new memory allocations. Not only do you avoid using a GC, but you can also avoid heap allocations by allocating your objects on the stack, since they will all have life time no greater than your calculation for each iteration of the simulation. And stack allocation is about as fast as it gets. The only thing better might be fixed locations in a global, static array, but this gets a little complicated if you are going to be using threads, since you'll need to make sure two threads don't use the same memory for their temporary variables. I'm not sure how much of a boost this would yield, or if it would help at all, or if it would be worth the effort. But anywho, in seeples you can do all of this explicitly. If you want things like that in c# or Java, you'll need to depend on an optimizing compiler to avoid using the GC while performing the calculations for each iteration of the simulation. But Java be fast. I've heard that Java with a just in time compiler can be around the same speed as C once you are no longer performing allocations.