I suspect that as well.
Apart from some tweaks here and there, we're still mostly dealing with the NT6 core (even when the kernel version was bumped to 10).
Pretty much all changes have been on the shell, and the Modern app engine has been introduced.
Things can be mangled in many ways to make it look like the even/odd rule applies.
I'd simply summarize that Windows 2000, Windows 7 and Windows 10 have been the rock solid releases.
Maybe it causes stability problems when solving actual graphics problems like screen tearing?
Why would that cause any problems? A proper graphics stack can easily deal with VSYNC. I'm sure that even AMD hardware isn't so crusty that it couldn't handle such a basic feature.
heh, well a 270 wont do much. he is lying.
Huh? An R9 270 achieves a G3DMark of 4000. Hey, it's not the latest flagship Deluxe Gamerz ReaperJaws Anniversary Edition Moon Commander card, but still an extremely fast one. Should play even new games on quite high settings.
saying almost the exact opposite of TFA (which I actually read, because the summary is obvious nonsense).
Oops, indeed... 80-bit for GCC, 64-bit for MSVCRT. I stand corrected.
Which means it's a 100% windows bug
No. The MinGW version of GCC allowed to compile programs against the Microsoft C++ runtime library, but the compiler created code which did not follow the spec of the Microsoft library. There really isn't anything to blame about Windows here.
Classes, class inheritance, smart pointer, vector, operator overloading.
That should suffice as the starter pack. You can learn the rest in your job when the need comes.
I've noticed several design suggestions in your code.