Craig Symonds and Mohsen Agsen: C++ Renaissance

Play Craig Symonds and Mohsen Agsen: C++ Renaissance

The Discussion

  • User profile image

    Awesome video, I think the C++ community is gonna love it!
    Thank you Charles!

  • User profile image
    Andrew Webber FX

    Great Video,

    Thank you so much Charles for moving the spot light onto C++

    As a C++ developer my favorate secret feature is having portable code! Currently I have code that binds to OS specific UI platforms:
    1.Windows with WPF and PInvoke
    2.Mac and IPhone with Cocoa and Objective C++
    3.Linux with Java and JNI C++

    The purist in me would love to see a solution for WP7 and Silverlight? What are the chances? Currently this is only avaliable using webservices...


  • User profile image

    Good stuff!  As part of the "dark matter", we have definitely been feeling neglected in recent years, so I am very glad to see the recent trend of turning more focus back on C++.  VS2010 is a memory pig, but it is a huge improvement for C++ dev.  Sounds like there will be a lot to look forward to in the next year.

  • User profile image

    Mmmm... Mary Jo once said that the 'Jupiter' thing is related to native code and C++, and the Windows Ribbon Framework already uses Xaml in native development, maybe we'll see a new WPF-like framework for C++ developers, finally replacing MFC, heheh. Hopefully we can find some good stuff in the Silverlight for Windows Embedded in WinEC7 maybe ?

    but the first thing I want is Intellisense for C++/CLI which I am using in a daily basis. and except that, VS2010 is very lovely for C++ native coding now. Smiley

  • User profile image
    Ben Hanson

    As I understand it, you can get around the circular reference problem with reference counting pointers by the use of weak_ptr. I hope Modern C++ starts to appear in Microsoft libraries. There is a yawning gap between C++98/C with classes and Modern C++.

  • User profile image

    I am just waiting for the things to come...

  • User profile image

    I can't wait to see some of the great things to come in C++! (The c++0x standard would really be nice... come on c++ committee.. hurry up Smiley )

  • User profile image

    Fantastic video! Thanks guys, keep it coming!

    The Natives are pleased Wink

  • User profile image

    all that C-hate was really unnecessary ...

  • User profile image

    @fefe: C-hate? What do you mean? We love C Smiley In fact, C is everywhere inside our products, especially in Windows...

    Bjarne Stroustrup invented C++ to extend C's formidable capabilities with modern abstractions (classes, strong static types, generics, etc). As Mohsen mentioned, it's amazing how C++ has added language abstractions, yet not at any perceivable cost to performance. Truly exceptional!

    As Bjarne states: "C++ is a direct descendant of C that retains almost all of C as a subset. C++ provides stronger type checking than C and directly supports a wider range of programming styles than C. C++ is "a better C" in the sense that it supports the styles of programming done using C with better type checking and more notational support (without loss of efficiency). In the same sense, ANSI C is a better C  than K&R C. In addition, C++ supports data abstraction, object-oriented  programming, and generic programming"

    There is no hate for C here. Only love!

  • User profile image

    @Charles: so where is the C99 support in the MS compiler? :P

  • User profile image

    I can only encurage MS to keep up the support for native code.
    In my industry (Casino Gaming) .NET is not approved.
    We see all sort of wonderfull technology released in .Net but are unable to use any of it.
    We would really like the type of technology for cloud connectivity in WCF for native code & indenity support.

  • User profile image

    Great video, keep it comming. Excited to hear about MS future plans for c++  

  • User profile image
    Mr Crash
    @felix9: "WPF-like framework for C++ developers" eww!
  • User profile image
    Alejandro Segovia

    Excellent video! It's great to see the spotlight moving back to C++ a little.
    Like it was stated in the video, managed and native tools are complementary to one another and C++ is a very important language that can be found on lots of products and tools and it's great to learn about Microsoft's views on the language and future plans.
    Will be looking forward to the next video!

  • User profile image

    I have used MFC/ATL to some extent in the past. Granted it is not the easiest of the technologies, it was challenging to develop in these frameworks. VC++ 6 was a great IDE for the times. Thereafter VC++ seems to have taken a back seat. MFC is showing its age and ATL is too complicated for a lot of new people coming on board. But there was no investments in these fields from MS and so I had to embrace .NET What amazes me is that Apple has successfully created an awesome platform using Objective C (ugly language) and has made some Java programmers to grudgingly switch to Objective C to hop onto the Apps bandwagon. How come MS has not been able to do this? Granted Objective-C and C++ is not apples to apples comparison. But my take is that if platform & tools (also some form of a channel to monetize your IP) were compelling enough, Developers would build rich apps irrespective of the language. Everything supported in .NET does not have to be supported in C++ (Managed C++ was an effort that did not create anything significant). I hope to see some revival of VC++ in its own right - not as another language for the .NET platform.

  • User profile image
    James Gregurich

    IMO, MS needs to get rid of the virtual machine. I see no point to the extra complication of dealing with that virtual machine rather than just compiling the language to the native hardware. Apple has shown that you don't need a VM to offer a rich development environment with RAD capability. ObjC even has garbage collection if that floats ones boat. You can integrate mac/iOS specific objc code with cross-platform C++ very easily and without much of a performance penalty since there no VM/native barrier to cross.

  • User profile image

    Dont worry, its okay to hate C. We know better today.
    Also I wonder what that last quote was about. (from memory) "hope im not giving anything away.. but dont be surprised if C plus plus gets designer tools first". I wonder if that has anything to do with Nokia going all in with mobile windows7. I cant imagine nokia using any other language than c plus plus. So maybe new tools are expected there. Please correct me if anyone knows better.

  • User profile image

    @Charles:C++ was invented because multi-threading was 'too hard'.

  • User profile image

    @tre: And to add more generally useful higher level modern abstractions to C...


  • User profile image

    Even though all money maker MS software is made in C++ (OS, Office, server stuff, accounting stuff, games, etc) MS is not innovating in C++ tools area since VC++ 6 (more then 10 years). Remember Borland C++ ? If not, go find old book and wonder. What libs MS offers in C++ area? MFC, ATL, COM -technologies 15 years old! Why? Cose C++ is cross platform and it's not suited monopolistic vision of their MBA overlords.Their strategy is to enslave their customers and partners.
    They are Rockefellers of information era!

  • User profile image

    Thank you all guys for these constructive comments!! We are not commenting yet about several of your questions but there are evidently lots of things happening around C++. As Mohsen and Craig said, we'll start telling you what to expect in the months to come. In the meantime, keep watching these videos as we are making more, subscribe our weekly newsletter: The Visual C++ Weekly (, read our blog ( and keep in touch!

  • User profile image
    Craig Longman

    If you're truly serious about it, then you need to bring things like ATL Server and WTL back into the "fold" so-to-speak.  Having left Win32 C++ circa VS v6 and only coming back to v9, I totally missed the ATL Server part.  But I happened across it recently and was amazed at what it provided. I couldn't believe it was simply left to languish, presumably because C# was a better "corporate direction" for web services, et al.
    MFC has it's place, but the ATL/ATLS/WTL really should be brought back in a given their rightful status.  As you were saying about layers, MFC is the way to start, but when you want something closer to the iron, you move to ATL.

  • User profile image
    Dinesh Sharma

    This is cool. We are Dark matter. This makes us feel proud. Thanks Microsoft for this Renaissance

  • User profile image

    First of all, thanks for the awesome video and the glimpse at Microsoft’s thinking on C++.  Two suggestions from this developer are (1) please consider modernizing the OLE DB Consumer Templates API for C++ based database applications and (2) let’s get some of this “C++ renaissance” injected into the Windows Phone 7 team – I have many vertical engineering applications written for the Windows Mobile platform that I cannot afford to rewrite in C# but would like to move to WP7 as C++ apps.
    I resonated with @Craig Longman who recommended a re-emphasis on ATL and WTL -- I’ve used both technologies for years, even when they appeared to be abandoned by Microsoft.  I wonder if looking at the source for the Hilo project offers a glimpse into a modified GUI framework that’s not quite WTL but maybe more.
    Finally, I know this isn’t a Visual Studio focused video, but if you’re looking for inputs, the C++ approach to GUIs with Resource IDs, Resource View, etc. is archaic and almost collapses under its weight for large projects.  I strongly urge Microsoft to overhaul this part of Visual Studio. 

  • User profile image
    Mahfuzur Rahman

    Why all developer can't follow only C++.
    I think there should be only one language that will support everything.

  • User profile image

    @Andrew Webber FX: Hi Andrew,


    I have a question regarding your post - you mention: 


       1.Windows with WPF and PInvoke


    Do you do your WPF work with C#/.NET and make PInvoke calls with C++ to the OS ?  If not, I'd love to hear about how I can leverage WPF from C++.  I was under the impression that this was possible, but not supported and that the WPF designer was not available to C++ via VS 2010.





  • User profile image

    Since C++ is currently undergoing renaissance, this is a good news for C++ programmers because the power and flexibility of this language would be extended as expected and as mentioned, Visual C++ will be expanding its capabilities. Well, I hope that Microsoft would produce versions of Visual C++ that would on all versions of Windows starting Windows 95. Other compiler vendors still support older Windows version and one example is the Open Watcom C/C++.
    If C++ would evolve, one of the nice features that I wish to be added is the ability to do smart linking similar to Delphi and most Pascal compilers. Because smart linking would generate much smaller statically linked executables which of course require less memory space. Dynamic linking your application would require dependencies to be included every time you need to deploy it.
    Dynamically linked executables seem to be small but the bloat is actually hidden in the required DLLs needed by the application to be deployed. Statically linked executables doesn't require any runtime libraries and this avoids DLL hell.
    If smart linking feature would be added to linkers shipped with C++ compilers, then most developers won't be forced to do dynamic linking in order to create smaller applications which would actually require huge runtime libraries.
    Also, there is performance penalty in calling routines from DLLs compared to those already embedded in the application.
    For these reasons, I prefer static linking instead of dynamic and adding smart linking feature is a must aside from new optimizing capabilities.

  • User profile image
    J. C.

    If you look at the entire sequence of events for Microsoft, from, say, late 1980's until now, it sorta-kinda makes sense that we are where we are today. The beginning of all the C++ vs COM vs .NET vs C#, vs yada was initially driven Microsoft's desire to solve the x-N SDK problem, where they would be forced to provide SDK bindings to the developer community for every single language they supported. Imagine that someone at Microsoft develops ultra-cool application that can creating 3D ray-tracing objects on the screen. In the 1980's, the C programmers would want it. The Pascal programmers would want it. The Visual Basic programmers would want it. And the FORTRAN programmers would want it. So microsoft would have to provide .LIB files for all these languages. It was a nightmare. Don Box, etc..comes up with the IDE of COM, where the 3D ray-tracing thingie from Microsoft would exist not for N languages, but for just 1: COM. Then, if a language wanted to use it, they'd have do a COM-like operation to get to it. [For C programmers, it's a call to CoCreateInstance().]. Ok, fine, now Microsoft can save huge amounts of money, but the code is a bit of a mess, and seemly unending as it spreads out like an oozing goo that has no bounds, forcing the programmers to do a kind of run-time evaluation of what COM features the 3D thingy provides and which it does not. It was a mess. After trying various things to make it less messy (ATL, for example), Microsoft says: screw it. Let's just make a new language that binds well with this messy way of coding. Heck, let's make several. Furthermore, let's make the new languages very similar to those that already exist. We'll add garbage collection so that programmers can abuse polymorphism like crack. This was great for Microsoft. Code bloated. Dell & HP sold more and more power to reduce effects of bloat. Programming piglets reveled in the idea of sloppy engineering, where foresight (required if you are a C++ programmer) was cast to the wind. After all, in an interpreted environment, you can always ask, "Intepreter, tell me if my code is crappy. If yes, stop. If not continue." Then, when answer is "yes", customer calls, programmer fixes, push out new code over net, continue. Revenue at Microsoft skyrocketed. But something weird started happening around 2008-2009. Companies wised up. They notice their programmers spending days over memory management issues in interpreted languages like C#. So they said, "Wait a minute...I thought the whole point of .NET was that it would eliminate the problems encountered in C++!" Now, not only do I have memory management problems, but I also have a bunch of engineers who are predisposed to thinking that lack of foresight in engineering is OK. This has to stop. Today, Microsoft is (very smartly IMO) recognizing that tech managers everywhere are wising up, and saying, "Hmm...we'd better retract some of the fiction, at least a bit of it, before some other company comes up behind us and retracts it for us." That's why C++ will see a rebirth - because Fred Brooks is right. There is no silver bullet, and as far as bullets go, C++ is, and will be for a long time, the best bullet around, all things considered.

  • User profile image

    Wow listening to the ramblings of 65 year old C++ programmers is depressing.

    Do you have any clue about the "big picture" in software dev?

    I can tell you that C++ would provide absolutely zero benefit for 95% of the code that I write (same for most .NET devs - millions of them). In fact quite the opposite. C++ is just object-oriented assembly language. Yes you can build wonderful abstractions but at the end of the day its OO-ASM.

    The thought of going back to messing around with header files, includes, the crude tools, pointers, libs, bad errors... ewww. Makes me shudder.

    I spent 5 years doing C++ and I dont miss it one bit. It crude and appeals to minds that are more interested in bit twiddling than solving business problems. You either have to be autistic or ignorant to choose C++ as your "hammer".

    Please explain how C++ will be a more suitable language for projects that currently use .NET?

    Is it because Apple has managed to build great things using their crude idiosyncratic Objective-C "look how smooth the iOS apps run and how sexy Apple are" we must imitate them??

    Guess what? Its not the failure of the CLR that has meant that .NET apps run craply. Its because of the crap GUI frameworks we have been given to work with that are convoluted, poorly implemented, and just plain suck at performance.

    How about solving that problem - fix the .NET UI frameworks, instead of "doing a HTML5" and encouraging us all to run back to a crude OO-ASM (just because we might make apps as cool as Apple).


  • User profile image
    George Birbilis

    no wonder the software world is full of bugs - lots of it is due to C++ baggage from C

Add Your 2 Cents