People who are against GC have never programmed anything but small, linearly structured script-like programs. If you're running a single thread, you can go ahead and allocate something, send it off to perform a task, and then wait for it to come back and kill it, since you can only do one thing at a time anyway. But when you're dealing with threads and concurrency and workers and asynchronous callbacks, it's not that simple. Either you must write your own not-as-good-as-language-x's garbage collector specifically for the program, or just end up shipping another hideously memory inefficient Windows application.
So keep on talking trash about CG while you hack away at your 200-LOC ``hello world'' app from 1982. Since you'll probably end up being a janitor it's good that you're learning to collect garbage.