Bad things about your favourite programming language

Problem is, WPF is getting on - many applications are starting to switch over to WPF. It is now 4 years old, and Microsoft themselves have moved over: VS2010 is full WPF.

Also, the using statement does not release memory. The GC still needs to do it's job before the memory is actually released.

C++'s downfall would be memory management. You must manage memory yourself.

I said resources, not memory. To be more precise, I meant "resources that are not managed memory". Things like process handles, synchronization primitives, database connections, etc.Anything that needs to be released when you're done with it.

If you use Windows Forms or WPF, you're basically giving up on your program ever being cross-platform (at least without a significant amount of work), just like if you're using C++ and use MFC, ATL, DirectX, or COM and don't abstract it behind a cross-platform layer.