@Sitsch, WPF isn't the problem, except in making raster fonts no longer eligible which was a horrible move on MS's part. The problem is the new Intellisense. That's what slows everything to a crawl as you actually write code, whether it's C++, C# or XAML for WPF/Silverlight.
The other problem is the new partially C++0x compliant compiler (RAM gobbler edition), which gobbles RAM like there's no tomorrow when templates are involved (e.g., boost variant anyone?). When you run multiple parallel compilers (say eight of them), which these days seems to be a good idea given the standard quad cpu (8 with hyperthreading) hosts people use for development and you better have lots of RAM (where lots >> {i.e., much greater} 4 GB). I am typing this on a host with 12 GB of RAM as we speak, which is about the bare minimum necessary for C++ software development these days.