actually GC's aren't that bad. considerate apps on android will not hitch from the GC unless the device is quite old my bigger problem is debugging these thing

actually GC's aren't that bad. considerate apps on android will not hitch from the GC unless the device is quite old my bigger problem is debugging these things. whenever i am forced into this environment i usually end up debugging someone elses memory problem and having a really hard time of solving it because of the sloppy practice GC encourages of not thinking about memory, so you end up with some weird distant or circular reference to an object preventing it from being deleted when you know better - that the problem is the coding style which allows that reference. new and delete force you to think a tiny bit, just enough to not shoot yourself in the foot like that. i'm always extra bitter because i have a track record of writing software where the only problematic leaks are from gc or ref counted stuff in opaque libraries... if i never had to touch this stuff there are 3 or 4 apps that i wrote which would have had zero leaks.