I wrote an x86 NT utility back in 1996 on NT4 (with no service packs). It still executes and works perfectly on an x64 Windows 8 machine.
That's a mere 17 years ago.
There are two APIs now. The old one isn't going away either.
I wrote an x86 NT utility back in 1996 on NT4 (with no service packs). It still executes and works perfectly on an x64 Windows 8 machine.
That's a mere 17 years ago.
There are two APIs now. The old one isn't going away either.
I think they would be batshit insane to do otherwise.
Nobody wants to be locked into a single vendor's platform. It's good for the vendor and bad for everybody else. How can they be surprised that everybody else now dislikes them for doing it?
The bit people forget is: stop procrastinating and build some shit.
To be honest, most people really don't give a shit. The next cigarette or pay day is far more important. Perhaps I'm getting old, but there are more important things to worry about.
The difference is that not all ecosystems are tied to a single vendor. Nobody has a lock on POSIX or Java like Microsoft has on Win32. And the hardest part of getting a portable C program to run on Windows, Linux and OSX is to get the program that was much more easily ported between Linux and OSX to run on Windows, because Microsoft has to do a million inane things like using WSAGetLastError instead of errno just to be different.
>The bit people forget is: stop procrastinating and build some shit.
I don't think people forgot that. We've just started building shit for and on non-Microsoft platforms and found it to our liking.