Quote from book

[StrangerInBeijing]

Just got this in a book I'm busy with, so was wondering if someone can comment...

However, as with all design trade-offs, garbage collection comes at a price. You don't know the order in which objects will be destroyed. Objects are not necessarily destroyed in the reverse order of their creation (as they are in C++). You also don't know when the garbage collector will decide to destroy objects. An object is not destroyed at the moment that it becomes unreachable. Because destroying objects can be a time-consuming operation, the garbage collector destroys objects only when it is necessary (when the heap memory is exhausted) or when you explicitly ask it to (by calling the System.GC.Collect method). Clearly, this makes C# unsuitable for some time-critical applications

How would you define "time-critical" applications and what is to be used instead in such case?

[mendhak]

A time critical app would be one where, for example, you are reading data from a source which is constantly updating the information it's sending out.

[StrangerInBeijing]

you write pages about ufo's and nonsense, and give me this..no hell, gimme more info! lol

ps....Unique, really cool profile one MVP site!!