| Wow -- how reputable is the source of that post? I've never developed on the 360, but I am familiar with some C# internals, and the garbage collector should definitely not be taking up enough cycles that you should be concerned about it, unless you are doing something extremely mysterious, or writing really bad code.
That's on a PC, mind you, but it's not like the 360's specs are that bad, are they? I don't understand why it would suddenly be a problem. Ditto for memory allocation. At worst, if you really, really need to manage your own memory for some resource-intensive bottleneck routine, can't you write unsafe code? (For the audience, in C#, the "unsafe" keyword on a method or class lets you use pointers for direct memory access, whereas that's normally not kosher in .NET.)
Like I said, I don't know anything about the 360, so maybe I can believe that memory usage is a bigger deal than I'd expect, but garbage collection? Really? |