> It is however annoying as hell to have a freaking dial pad stall for several seconds on a 512 MiB RAM phone. I don't remember such basic functionality annoying me to no end on S40 phones with ~0.5MiB RAM.
Agreed but, once again, I never saw any definitive proof that GC was to blame for that. It could just be too many background apps/daemons starting simultaneously when you just wake up the phone to make a call - an entirely different problem.
By the way and for some fun try to google "slow ipad" or "slow iphone".
> So the GC does not really help you. You still need to take care of all those resources
A typical application has an order of magnitude less network connections and files than memory objects, so GC means a LOT less to worry about.
> which means lots and lots of catching and rethrowing, not unlike C code which tries not to leak.
Which language does better and how? Please give some pseudo code example.