News for hackers. Stuff that matters.
Re:The .NET Language Strategy by AnimalMuppet on Wednesday February 01, 2017 @05:50PM (#13546210)
So we had this security app that needed to know what version of Windows it was running on. And the Windows detection worked flawlessly... until Microsoft came out with a new version. Our program detected the new Windows as the previously-most-recent version, even though we were calling the standard Microsoft-approved which-version-are-you function.

Turns out Microsoft detected that our specific app was asking, and lied to it, because telling it the truth broke the previous version of our app (because the previous version didn't know about the new version of Windows). It was annoying, and yet still incredibly impressive that Microsoft knew who we were and was going out of their way to try not to break us.

Re:The .NET Language Strategy by euyyn on Wednesday February 01, 2017 @05:59PM (#13546261)
Viewed from the other side, someone at Microsoft was probably pretty upset with you guys when he found out :)
Re:The .NET Language Strategy by jug on Wednesday February 01, 2017 @07:11PM (#13546786)
Given the NT code leak comments... yes ;)
Re:The .NET Language Strategy by flukus on Wednesday February 01, 2017 @09:42PM (#13547632)
I've heard of nvidia doing similar things lately, patching their driver because of a bug in a game. I'm really not a fan of this approach, it's coupling on a global scale and adding a lot of complexity.