Re:Why do Windows functions all begin with a pointless MOV E...
by cousin_it on Wednesday September 21, 2011 @12:12PM
(#3022530)
That's true, but sadly they don't put as much effort into compatibility of development tools. Old code has to be ported to new versions of Visual Studio. Even just sticking with C++, I ran into issues with winioctl.h and unicode fstreams requiring different code for different versions of VC++. I imagine other people may have a longer list.
Re:Why do Windows functions all begin with a pointless MOV E...
by ajross on Wednesday September 21, 2011 @12:35PM
(#3022646)
That's sort of the flip side of the same coin. Associating specific runtime versions with apps at build time reduces the bug surface. They don't have to worry about breaking last year's apps with this year's changes to the standard libraries.
And yes, I agree it sucks. But that's the world of proprietary software. I think MS has done this about as well as anyone could.
Re:Why do Windows functions all begin with a pointless MOV E...
by rsynnott on Wednesday September 21, 2011 @03:58PM
(#3023422)
Unfortunately, it took them quite a while to have an actually vaguely conforming C++ implementation, and there are still issues (there was a nice example on Hacker News a while back involving some stl method being dramatically slower than both its equivalent in other major implementations, and a near-equivalent MS-specific method), which may explain some of that.
Driver compatibility is less of an issue; older hardware becomes less common (and thus less of an issue) over time, and strictly adhering to kernel compatibility limits your ability to add new features to the kernel significantly.