C++ Renaissance Here Due To WinRT C++/CX ?

[SunnyInHades]

The more I look at C++/CX on WinRT (Windows 8.1) the more I like it.

C++ has been neglected by Microsoft for about the last 20 years or so - the young C#/.NET brigade have been laughing at the 'old C++ 'dinosaurs' for the last couple of decades, spouting off about the advantages of their WPF, MVVM data models and XAML data binding.

However with C++/CX on WinRT (Windows 8.1, Visual Studio 2013) Microsoft have introduced full XAML support and more importantly native code compilation. This means

a) The same functionality as C#/.NET applications - XAML for all now
b) Faster run time than C#/.NET managed code
c) Safer intellectual property (unlike C#/.NET code which can be easily reversed engineered to full source, even if obfuscated (just use d4dot), reversing C++ will require use of a disassembler - no thanks).

Also VS2013 includes full native code unit testing built in - nice to have.

VS2013 C#.NET/VB.NET Boy: I use XAML
VS2013 C++/CX Boy. I use XAML too, same components as you. However my apps will be faster than yours and can't be de-compiled. Take that !

There are plenty of blogs/web sites/books mentioning the 'C++ Renaissance' ...

"Microsoft is contributing to this renaissance through breath taking innovations like the Windows Runtime, C++11 standard implementation in the Visual C++ compiler, C++ Component Extensions, native XAML and DirectX support for Windows Store apps, C++AMP for GPGPU computing,"

Any opinions ?

[stek]

The more I look at C++/CX on WinRT (Windows 8.1) the more I like it.

C++ has been neglected by Microsoft for about the last 20 years or so - the young C#/.NET brigade have been laughing at the 'old C++ 'dinosaurs' for the last couple of decades, spouting off about the advantages of their WPF, MVVM data models and XAML data binding.

However with C++/CX on WinRT (Windows 8.1, Visual Studio 2013) Microsoft have introduced full XAML support and more importantly native code compilation. This means

a) The same functionality as C#/.NET applications - XAML for all now
b) Faster run time than C#/.NET managed code
c) Safer intellectual property (unlike C#/.NET code which can be easily reversed engineered to full source, even if obfuscated (just use d4dot), reversing C++ will require use of a disassembler - no thanks).

Also VS2013 includes full native code unit testing built in - nice to have.

VS2013 C#.NET/VB.NET Boy: I use XAML
VS2013 C++/CX Boy. I use XAML too, same components as you. However my apps will be faster than yours and can't be de-compiled. Take that !

There are plenty of blogs/web sites/books mentioning the 'C++ Renaissance' ...

"Microsoft is contributing to this renaissance through breath taking innovations like the Windows Runtime, C++11 standard implementation in the Visual C++ compiler, C++ Component Extensions, native XAML and DirectX support for Windows Store apps, C++AMP for GPGPU computing,"

Any opinions ?

Yeah, it's Microsoft.....

Nuff said.

[doodab]

In some fields C++ never went away.

[AtW]

WinRT is a dead platform.

C++ Renaissance might happen though because free lunch in terms of easy increase in CPU power (and now cores) is over - Moore's law is effectively dead. This might put people who can code "close to iron" in demand again. VB6 coderz might have to move along...

[woohoo]

WinRT is a dead platform.

C++ Renaissance might happen though because free lunch in terms of easy increase in CPU power (and now cores) is over - Moore's law is effectively dead. This might put people who can code "close to iron" in demand again. VB6 coderz might have to move along...

Damn it going to come out and say it, I loved vb6. It's time has gone but still have a soft spot for it.

[d000hg]

"Microsoft is contributing to this renaissance through breath taking innovations like ... C++11 standard implementation in the Visual C++ compiler ... DirectX support for Windows Store apps"

Implementing a standard isn't innovative, especially when other compilers also/already support it.
And DirectX support for Windows apps should be a given.

[d000hg]

Have they finally started adding refactoring tools for C++ or are we still left to use 3rd-party tools for this? It's the one area Eclipse is just amazing even compared to C#.

[LazyFan]

Hi,
As someone from the JAVA FOSS camp we are really happy about this.
By making C# a second class citizen they are in affect saying that the money in MS now goes on the C++/EXT way. And knowing MS they will force it this way in the long run.

This means more fragmentation of the MS world, whereby some will adapt and others will get peed off and then go down the FOSS route. Most but not all that go down this route never come back. Once they get the goodness of only paying for great support and not anything else, then they are done with MS for good.

Yes please keep pushing this on the Windows platform, we love it

[VectraMan]

WinRT is a dead platform.

C++ Renaissance might happen though because free lunch in terms of easy increase in CPU power (and now cores) is over - Moore's law is effectively dead. This might put people who can code "close to iron" in demand again. VB6 coderz might have to move along...

WHS. C++ was always there (you're using a C++ app to view this), but now more people are realising that power and CPU efficiency was important after all. PermieCo make proper electronic devices that go into racks and where power consumption vs throughput is all important. Anyone suggesting the software should be done in .NET or Java would be laughed at.

WinRT is for Windows 8 Metro apps, and we all know how successful that has been. C++/CX is basically C++ with COM support fudged into the language, which is interesting, but if I were doing COM I'd still do it the regular way and not rely on an MS specific language extension.

[d000hg]

I think C# is wonderful to work with, but C++ is like coming home.