> correctness, performance, maintainability, and robustness
What? I want whatever he is smoking.
C++ allows for casting to/from different types (the core behind polymorphism) - but if you cast to the wrong type then that's your own fault. If you want a warm fuzzy feeling of not worrying about bad casts - use Python/Go/FreeBASIC/some other language.
That is complete and utter delusion. Your program won't run any faster or optimize better because you used the auto keyword . If anything - it will take even longer (ms longer) to compile.
I have an odd feeling about that. Yeah you can change the return type of a method or function and you don't have to worry about changing the code calling those methods/functions. But if you are changing to a vastly different type - you are going to have to change the calling code anyways.
I don't want the compiler to fix my mistakes. I want the compiler to tell me how stupid I am and force me to fix them.
CppCast  is a pretty good C++-focused podcast. Starts with a summary of recent C++ news (and related topics), followed by an interview with excellent guests (usually luminaries from the C++ community).
When it comes to Norway, be aware that the Government has proposed the introduction of tuition fees for international students outside the EU / EEA despite a unanimous Parliament that said no to this under a year ago. 
I'm running Eclipse and the emulator on a 4 year old Mac Pro. Initial startup time for the emulator is about 20 seconds, but after that first hit has been absorbed, it generally takes about 8-10 seconds whenever I run a new build of the app I'm developing. (This is with HAXM  enabled. Still far too slow, so pretty much everybody does their development on actual Android devices, but far from the times reported in this thread.)