quote:
Originally posted by riahc4
And again you should give me the impression that you dont know about Vista by saying that Vista runs 16-bit programs when it does not; It has very limited compatibility for 16 bit programs and is not supported at all on 64 bit processors running 64 bit Windows Vista
you said it doesn't. the 32-bit version does. it does just as well as every other version of windows ever has, not "limited compatibility"
quote:
If there are better solutions, then go working at Microsoft. I bet they will pay millions if you have a better solution for all their ActiveXs which they STILL use to this day (for example: MSIE and many many MANY other NATIVE programs).
i think you mean COM, not ActiveX. and what's wrong with COM?
quote:
Yes but dont you see a trend? Less and less everyday ActiveX DLLS or VB6 or whatever your oldschool ways are, are used. .NET for example is being pushed as the "next great thing" and developers should enbrace it (sorry for sounding like Steve).
well, .NET is the official successor to COM and is completely compatible backward and forward with it...
quote:
One of the reason IS that Vista doesn't accept them. Some APIs are not in Vista anymore. And how do you know Vista is "more effecient" in handling its API functions? You have the source of both XP and Vista and you can interpret it?
Those APIs that have been removed arent because Microsoft decided to fuck some developers; They were removed because other functions possibly replaced them with a more effecient and better way of handling and interpreting data.
what are both of you talking about? if microsoft is about anything, it's backwards compatibility. pretty much everything that was there in 2k3 is still there in vista, plus even more. the only thing that i could think of being removed is DirectSound...
/ 
