So, with WinHEC coming to a close, the biggest talk was of course the newest release of Microsoft (R) Windows (R) Codename Longhorn, now at build 5048. With nearly one year since the previous release (build 4074) build 5048 sports some new features and lacks some others. Recently, the talk was centered around the lack of WinFS, the new futuristic Windows File system. However, we'll get to all that a little later.
Permalink for comment
To read all comments associated with this story, please click here.
I would be interested in seeing how much managed code services are running. Could somebody with access to this longhorn build run perfmon and look at the various CLR performance counters such as global/"# Bytes in all heaps"?
The really important thing about longhorn is that it will have the successor to win32, winfx, which is supposedly mostly managed code. If they can pull this off they will have the technological base to have a really secure OS and to add features very quickly.
I agree with the other posters that apple has not much to worry about though.
I would be interested in seeing how much managed code services are running. Could somebody with access to this longhorn build run perfmon and look at the various CLR performance counters such as global/"# Bytes in all heaps"?
The really important thing about longhorn is that it will have the successor to win32, winfx, which is supposedly mostly managed code. If they can pull this off they will have the technological base to have a really secure OS and to add features very quickly.
I agree with the other posters that apple has not much to worry about though.