Conor said:
Obviously what was in that link was above your level of understanding.
I probably understand more about it than you do seeing how I have written
real-time multitasking operating systems for embedded devices complete with
memory management and file systems.
For that reason, all those cute little keywords in that article don't
impress me as much as they do the average user.
Yea they have made some nice internal changes and I understand what they
did, why they did it and how they did it. Do I care though? No.
I care about my hardware working and my software working on it and being
able to do my work and being able to meet my deadlines and not dealing with
operating system problems. How it manages its memory, file system and
tcp/ip stack are of little concern to me.
One of the things near the bottom actually annoys me, being the .Net
Framework 3.0 and them essentially forcing people into it by no longer
putting the new features into the win32 API.
I've worked with the .Net Framework for years, yea doing UI work with it is
very nice, it has some very nice features. But it also has a very large
drawback I didn't even discover how bad it was until I ported one of
my .Net apps to C++ and OpenGL.
Dataset: 40,000 polygons 2D and 125,000 lines 2D
..Net Framework & MDX render time: 150ms single core, 80ms two cores.
C++ Render time running on a single core only: 10ms
My C++ engine will run circles around the Managed .Net engine and it isn't
even nearly as optimized.
To be honest with you, the biggest problem I have with Vista is microsoft
pushing "their way" onto everyone ranging from users to developers.
--
Stephan Rose
2003 Yamaha R6
å›ã®ã“ã¨æ€ã„出ã™ã²ãªã‚“ã¦ãªã„ã®ã¯
å›ã®ã“ã¨å¿˜ã‚ŒãŸæ™‚ãŒãªã„ã‹ã‚‰