MSDN has been terribly slow all week. NJ.
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
IIRC the benefits of VB5 native compiling were limited because most of the code calls into the runtime library / COM anyway and wont gain much from native code in itself, except heavy math routines. And in the WinRT world you can always write those code in native languages. so ... I guess Herb Sutter was right about the inlining of templates, without virtual calls, C++ is still better.
yeah, I do not follow at all how a C++ WinRT app is more efficient and less power using than C# when the majority of the time the app is in the WinRT. And if a modern C++ app is supposed to use smart pointers, how is that more efficient that C# references? I thought the lesson learned by the designers of the GC was that reference counting was slower than garbage collecting.
What does this mean for Anders? Will he have to answer to the native language team before any additions to C#?
I am looking for a book that shows how to write the sys internals tools.
But users, whether consumer or business, cannot safely download and install 3rd party software on their PC. User's do not buy and install extensions for the shell and office out of fear of malware. ( I am guessing and assuming. ) Any numbers on how many Windows PC in the world are controled by Malware? http://www.zdnet.com/blog/security/report-48-of-22-million-scanned-computers-infected-with-malware/5365
And the native code development scene for Windows is pretty poor. There is a ton of stuff you have to learn to write native apps for windows. First C++ and Visual Studio. Then Win32 and COM and the shell.
WinRT sounds great. But it sounds like it does not apply to desktop apps until windows 9. The company is fine by me. Maybe the world is a safer and freer place when mega corporations are only run at half efficiency. But windows could be a lot better.
His WPF book is terrific. ( by contrast, I am getting nothing out of the Russinovich, windows internals, 6th edition, part 1 book. No code samples. )
Petzold should be the editor of MSDN magazine. Even if for a short time. Just to show how programming articles can be intelligible and instructive.
I think the problem all along has been Microsoft wanting to transitioning from a company that licenses software for a one time charge to one that gets a monthly income stream from the user's of software. Device OS software is not hard to write. It just takes a lot of programmers, trial and error. If .NET turns out to not be performant enough have other approaches in the works. But the message from the top of the company has to be that MSFT is going to have an OS for every device out there. Wherever possible apps for one device will work or can be ported to another.
why did it have to be a moneypit? There must be a market for a media device that is not a phone. One that seamlessly integrates with PCs and other media devices, which is not on all the time so it can hold a charge for an extended period of time.