Re: A re-announce on GC's defects

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Born,

B> GC is really garbage itself
B> B> Reason 1:
B> B> There is delay between the wanted destruction and the actual
B> destruction.
B> B> Negative effects by the destruction delay:
B> B> 1) Efficiency issue

Does it really bad? :) It only depends on your app context. If it doesnt meets your requirement welcome back to unmanaged world with manually memmory management

B> 2) Logic issue
B> B> The need for weak reference makes the destruction delay logically
B> incorrect.

Caching is the logically incorrect too?

B> The only problem with this approach is cyclic
B> reference. However, even if not theoretically proven, the problem
B> generally can be solved by replacing some strong references with weak
B> references.

But it's logically incorrect, as mentioned before :)

B> I believe the restriction by GC is one of the main reasons why in
B> some field (the gaming industry, for example), java or C# is rarely
B> used in serious products who face real computing challenges.

lol
What does the "serious product" and "real computing challenge" mean for your?

The FPS? :)

BTW, last DX samples are in C#. The real challenge of C# and game industry is performance.
In 2 - 3 years it will be solved


B> Solution
B> B> 1) The ideal solution is to convince the language providers to give
B> us back the ability of managing memory by our own. GC can still be
B> there, and it becomes a real addictive in that situation.

Nobody prohibits u to use C++


---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo


.

Relevant Pages

  • Re: Deterministic destruction across scope and state machines in c#
    ... that will in-turn destroy or finalise all member objects of the class ... The only cleanup your code should worry about is when dealing with resources that ..NET itself cannot be aware of, either directly or indirectly (by holding a reference to an object that implements IDisposable). ... initiating the destruction). ... Properly encapsulated, it is trivial to add the necessary call to IDisposable.Dispose() when updating the current state reference there). ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Destruction of gun
    ... destruction of any firearm to the police department within the ... mandatory reporting window. ... There's no reason why you shouldn't cut it ... as distinct from destruction; ...
    (rec.guns)
  • Re: What to Do With Cheney?
    ... "For bureaucratic reasons we settled on one issue, weapons of mass ... destruction, because it was the one reason everyone could agree on," Mr ...
    (rec.sport.golf)
  • Re: What utter piffle!
    ... Whatever happened to good old fashioned punishment? ... The reason they do it is because they know they'll get away with it ... as the destruction of property and the ... The anti-Catholic Gordon Riots of 1780 led to a large number of ...
    (uk.politics.misc)
  • Re: Bush Takes Responsibility
    ... > Administration's utter and complete destruction will suffice. ... > one reason they keep losing elections: ...
    (rec.music.classical.recordings)