4 years plus the time that at least intel, gcc, clang and vc++ support it, are too long in computer time.
Who knows how the computing landscape will look like in 2020, time the C++17 should be available in mainstream compilers, maybe.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
The best way to help developers bring their OpenGL ES games to the Windows Store, would be to just rejoin Khronos and provide an implementation for the 3D API supported by the majority of the industry.
All compiler vendors provide language extensions, so I am not criticizing Microsoft doing language extensions.
However, all the C and C++ compiler vendors with exception of Microsoft tend to follow standard first and then do whatever else fulfills their goals. At Microsoft the priorities are inverted, because standard code means it is easy to move the code to other platforms.
I use Microsoft products since the MS-DOS 3.3 days, among many other vendors as well, so I am not just criticizing without experience.
That is easy to tell.
When COM was being introduced on Windows back in the day, improving C++ extensions for COM support was more important than standards compliance.
Then came .NET, improving Managed C++ and its sucessor C++/CLI were again more important than standards compliance.
Eventually we got this C++ Renaissance discourse, but in the end improving C++ AMP extensions and C++/CX take precedence over standards compliance.
From the outside, one gets the impression work on standards compliance is only done when tickets for extension related bugs are closed.
Thanks for sharing the presentation.
Looking forward to see such optimizations also available to the JIT and NGEN compilers in the .NET platform.
Will we ever be able to get a proper native code compiler for .NET or must we rely in projects like Mono?
Nice discussion, thanks for making it available.
While I enjoyed the talk, I got disappointed that the future of F# part did not address the 2nd class status that F# seems currently to enjoy in Visual Studio.
I for one would like to have proper F# support for Web development, WP and Windows 8 in Visual Studio.