Decouple C++ compiler releases from Visual Studio releases
In VS2010 and subsequently in VS2010sp1, many features of C++11 was implemented. But it is still far from covering the full spec. And we can assume that the full spec will not be available even in VS2011(or v.next). Because, MS is polling developers for prioritizing certain features of C++11. May it will take some time to have a fully supported C++11 with VS. And that is true for almost all the C++ implementations. And probably, the C++ compiler supplied with VS v.next will not be usable with VS2010.
We can see, C++ compiler releases(full version or service packs) are coupled with VS releases. So, it becomes cumbersome and sometimes impossible to use later versions of C++ compilers with earlier versions of VS. So, I suggest decoupling these two releases. So, that developers can enjoy latest implementations of C++ without further hassles of upgrading VS, sp or full release.
E. B. commented
This is important. Otherwise people have to live with a half-a**ed compiler for up to 4 years before they get an update. Are you kidding me? By that time people would've developed and moved to another language!
John M. Długosz commented
I heard that this was indeed the case at the GN2012 conference.
I'm not using my votes for it not because I don't care but because I believe this is already accepted. It is in fact very important to me.
@Mystere Man: when was the last time a feature was added to the C++ compiler in a service pack?
The feature packs (which *also* don't add features to the C++ compiler) are for Ultimate only.
Well who can use the new compiler in the near future? Not a lot devellopers I think, because most of them still have to target Windows XP!
Mystere Man commented
I don't really see the problem here. MS has shown a willingness to add features to the compiler in service packs. They also have "feature packs" they release. MS is perfectly capable of releasing new versions as they see fit.