For the first time, the Windows operating system will wall off some audio and video processes almost completely from users and outside programmers, in hopes of making them harder for hackers to reach. The company is establishing digital security checks that could even shut off a computer's connections to some monitors or televisions if antipiracy procedures that stop high-quality video copying aren't in place.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
For how long, because it is clear Microsoft are moving you away from it?
The sooner, the better. That said, unmanaged code will run on Windows as long as there's a significant need to run it. It'll likely always be allowed, however the benefits of running it will greatly deminish. Unmanaged code devs will have to use interop to work w/ the system rather than managed devs using it as it is for many things now.
You're side-stepping the real issue there. It's that extra step that's important.
I'm side-stepping nothing. I stated a fact. That "extra step", if you mean compiling to native before execution, is important for performance.
More important is the verifiable IL that the apps are distributed in by default, which lessens the exploitability of your applications and eliminates the need for distribution of multiple binaries for each architecture. It also allows the code to be optimized for the exact machine on which it will run during that "extra step", and allows for more flexible and new types of application scenarios that unmanaged code could never safely emulate because of its lack of verifyability.
Member since:
2005-07-06
Unmanaged C++ and even ASM is still supported under Windows. .NET even has facilities for unmanaged code access.
For how long, because it is clear Microsoft are moving you away from it?
BTW, all .NET code is compiled to native before execution.
You're side-stepping the real issue there. It's that extra step that's important.