3 ms·

The politics between Windows and DevDiv are just as interesting as well. For example it was @malwareminigun (used to work on MSVC compiler team) on Twitter that

by yuhong 6y ago

The politics between Windows and DevDiv are just as interesting as well. For example it was @malwareminigun (used to work on MSVC compiler team) on Twitter that complained about the CPU time that CompatTelRunner consumes (mostly by Appraiser gathering application and device inventory).

userbinator 6y ago
I'm pretty sure not everyone at MS agrees with the spyware they're adding to Windows either.
- yuhong 6y ago
  @MalwareMinigun is Billy O'Neal BTW. I have a Wikipedia article about this topic: https://en.wikipedia.org/wiki/Draft:Upgrade_Readiness https://en.wikipedia.org/wiki/Draft:Upgrade_Readiness Appraiser not only consumes CPU (and HDD/SSD!) time, but is also technically quite interesting as well. For example it loads a simple kernel driver (nxquery.sys) into your Windows 7 machine to read a MSR to determine if NX has been disabled in the BIOS.
  - saagarjha 6y ago
    Your comment seems a bit out-of-place, am I missing a connection between your link and this Hacker News post?
pjmlp 6y ago
Having been targeting Windows since the 3.0 days, I think those politics are responsible for some monumental failures. Like Longhorn, as everything .NET was hard to swallow for them. Later confirmed, from my point of view, when Joe Duffy recounts how some devs reacted at the internal success of Midori. So we got Longhorn core stuff redone in COM instead for Vista, and by the time Windows 8 came out WinRT, with an .NET runtime incompatible with CLR, including only able to understand the MSIL that the team considered relevant for firstly MDIL (Windows 8/8.x) and then .NET Native (Windows 10 onwards). Now we have Reunion trying to sort out the mess, brining everything back into Windows 7 like development stack, where UWP is just the COM evolution and both worlds (Win32 / UWP) share the same sandboxing and container models. And in the process .NET 5 is focusing on the desktop side, with .NET Native having an uncertain future, and a big question mark if CoreRT will ever take its place. Ah and then there is the whole story of them killing C++/CX via C++/WinRT, in name of ISO C++ compatibility, for a bunch of libraries that are anyway Windows specific. Now they realised that telling everyone to just wait for ISO C++23 to gain C++/CX features wasn't the most welcoming decision to "Developers, Developers, Developers". C++/WinRT only feels better for those that have eschewed C++/CX and used the real man WRL (ATL like) template library, which naturally was the Windows team. Those politics really suck from the outside.

by yuhong 6y ago

userbinator 6y ago

I'm pretty sure not everyone at MS agrees with the spyware they're adding to Windows either.

yuhong 6y ago
@MalwareMinigun is Billy O'Neal BTW. I have a Wikipedia article about this topic: https://en.wikipedia.org/wiki/Draft:Upgrade_Readiness https://en.wikipedia.org/wiki/Draft:Upgrade_Readiness Appraiser not only consumes CPU (and HDD/SSD!) time, but is also technically quite interesting as well. For example it loads a simple kernel driver (nxquery.sys) into your Windows 7 machine to read a MSR to determine if NX has been disabled in the BIOS.
- saagarjha 6y ago
  Your comment seems a bit out-of-place, am I missing a connection between your link and this Hacker News post?

pjmlp 6y ago

Having been targeting Windows since the 3.0 days, I think those politics are responsible for some monumental failures. Like Longhorn, as everything .NET was hard to swallow for them. Later confirmed, from my point of view, when Joe Duffy recounts how some devs reacted at the internal success of Midori. So we got Longhorn core stuff redone in COM instead for Vista, and by the time Windows 8 came out WinRT, with an .NET runtime incompatible with CLR, including only able to understand the MSIL that the team considered relevant for firstly MDIL (Windows 8/8.x) and then .NET Native (Windows 10 onwards). Now we have Reunion trying to sort out the mess, brining everything back into Windows 7 like development stack, where UWP is just the COM evolution and both worlds (Win32 / UWP) share the same sandboxing and container models. And in the process .NET 5 is focusing on the desktop side, with .NET Native having an uncertain future, and a big question mark if CoreRT will ever take its place. Ah and then there is the whole story of them killing C++/CX via C++/WinRT, in name of ISO C++ compatibility, for a bunch of libraries that are anyway Windows specific. Now they realised that telling everyone to just wait for ISO C++23 to gain C++/CX features wasn't the most welcoming decision to "Developers, Developers, Developers". C++/WinRT only feels better for those that have eschewed C++/CX and used the real man WRL (ATL like) template library, which naturally was the Windows team. Those politics really suck from the outside.