There just has to be away of turning almost 20 years of Visual C++ experience, 13 years of C# experience and a 1st Class Degree in Computer Science into a means of working from home so I can help raise my one year old daughter. Life’s ‘pre children’ luxuries not required.
No more C++ 11 Standard compliance updates for Visual Studio 2012 then. Next stop Visual Studio 2013, which should go into public preview at the end of month as part of the BUILD conference. Fingers crossed that the final RTM for VS2013 will be no more than 3 months after that.
Here’s the quote from Microsoft on all this. It’ll be interesting to hear Herb Sutter address these points (at BUILD, and not before, one assumes):
Brian Harry MS 5 Jun 2013 5:36 AM #
@Jesper, I’m not going to dwell on this but clearly there’s a lot of interest in C++ and you’ve articulated your frustration reasonably well so I feel it deserves a response. First, I don’t work on the C++ team and it’s a bit tenuous for me to speak for them but I have talked to them about it and can share some thoughts. They understand that C++ 11 support it important. They hear the feedback. They weren’t able to get in in VS 2012 (and I think we all regret it) but that’s that. So, they released a CTP a few months after VS 2012 shipped to give people a preview. There was conversation of putting it into a Visual Studio 2012 Update, however, the feeling was that, given the nature and magnitude of the changes and type of testing cycle an Update affords, the probability of serious regressions was too high. So the decision was made to roll those capabilities into VS 2013 instead. As we get more experience with Updates will that kind of risk assessment change – I strongly believe so. Knowing then what we know now, would we have made that decision differently, I don’t know but I doubt it. You can be confident there will be C++ 11 improvements in VS 2013. I’m also confident that it won’t include everything everyone wants. I don’t think it’s hard to say that our C++ compiler is further behind the standard than we want and we are discussing what we can do to change that.
It’s somewhat vexing as a Windows developer to see Clang be feature complete, cross platform porting in a device centric world aside, C++ is still the premiere big infrastructure / performance language and Microsoft really needs to get its act together here and continue making up ground yielded during the ‘lost decade’.
This sees me blogging again after a hiatus of a few years. I work at SunGard Adaptiv where for the past two decades I’ve worked as a Technical Architect, primarily with C++ (native code) base tech. All opinions in this blog are very much my own.