Re: What will many cores mean to future Windows releases?

"m. Th." wrote

plus which a VM implies? Isn't better to have a compiled code straight
away?

Like many things, the architecture is over-determined. I do think that the
(MS) intent of .NET is to wean programmers from direct dependence on the
win32 API as much as possible. But that has nothing to do with being
'cross-platform' in the sense of running on Linux or Solaris or whatever. It
has to do with the fact that the win32 API is an increasingly kludged and
aging platform, and MS has to open a space to move forward. It's a
complicated process, because they have to make sure that .net programs will
run on the next MS OS, but not on current or future competitive OSs.

All that bye-the-bye, however. Programmers are going to adopt .net or not
based on whether it and the FCL make their work easier and more productive.

bobD


.

Relevant Pages

  • Re: Future FASMLIB website
    ... Do you know why assembly programmers reject the idea? ... In for a penny, in for a dollar as they say. ... in assembly language and then come back and make the argument that all ... If you're willing to make Win32 API calls, ...
    (alt.lang.asm)
  • Re: RTOSs and Windows CE question
    ... > graphical display and user interaction, especially if your programmers ... > are familiar with the Win32 API. ... from the WinCE API that experience with the Win32 API isn't all ...
    (comp.arch.embedded)