Oh my God!!! anybody heard of separation of interface and implementation ?.NET "is" a new API to program against. Whether it is (currently) based on the old Win32 API should be the least of your concerns. One day Microsoft will rewrite the core libraries to go straight to the kernel, without breaking your code (ok this is a bold statement) cause your code is based on an "interface". Why is it currently based on Win32 ? Probably to reduce the time-to-market. With Longhorn we will see.Net going more and more to the kernel directly. And one day.Net won't be relying on Win32/64 anymore, but coexist with it. Some 20 years later Win32/64 will be phased out.
Slashdot Mirror
Oh my God!!! .NET "is" a new API to program against. Whether it is (currently) based on the old Win32 API should be the least of your concerns. One day Microsoft will rewrite the core libraries to go straight to the kernel, without breaking your code (ok this is a bold statement) cause your code is based on an "interface". Why is it currently based on Win32 ? Probably to reduce the time-to-market. With Longhorn we will see .Net going more and more to the kernel directly. And one day .Net won't be relying on Win32/64 anymore, but coexist with it. Some 20 years later Win32/64 will be phased out.
anybody heard of separation of interface and implementation ?