True story: a lot of the Microsoft engineers I interact with actually do use Apple hardware. Admittedly, I onto interact with the devs on the .NET (and related technologies) departments.
Specifically WHY they use Apple hardware is something I can only speculate on. Presumably it's easier to launch Windows on Mac than the other way around, and they would likely need to do that as .NET and its related technologies are cross platform as of 2016. But that's a complete guess on my part.
Am *NOT* a Microsoft employee, just an MVP for Developer Technnolgies.
I still don't understand how Microsoft lets standby remain broken. I can never leave the PC in my bedroom ij standby because it will randomly wake up and blast the coolers.
Consumers _do not care_ if it is the firmware or Windows.
Dell was one of the earlier brands, and biggest, to suffer these standby problems. Dell has blamed MS and MS has blamed Dell, and neither has been in any hurry to resolve the issues.
I still can't put my laptop in my backpack without shutting it down, and as a hybrid worker, having to tear down and spin up my application context every other day is not productive.
Yeah I hear you. One of the reasons I’m still inclined towards Mac laptops for “daily drivers” is precisely because it’s disruptive to have to do a full shutdown that obliterates my whole workspace. Other manufacturers can be fine for single-use machines (e.g. a study laptop that only ever has Anki and maybe a browser and music app open), but every step beyond that brings increased friction.
Maybe the most tragic part is that this drags down Linux and plagues it with these hardware rooted sleep issues too.
S3 sleep was a solved problem until Microsoft decided that your laptop must download ads^Wsuggestions in the background and deprecated it. On firmwares still supporting S3, it works perfectly.
Sleep used to work perfectly fine up until, I don't know, 10 years ago. I doubt hardware/firmware/BIOS got worse since then, this is 100% a Microsoft problem.
Sadly even if Microsoft had a few lineups of laptops that they'd use internally and recommend, companies would still get the shitty ones, if it saves them $10 per device.
To be fair, this was also my experience with Macbooks. This "smart sleep" from modern OS manufacturers is the dumbest shit ever, please just give me a hibernate option.
I used to have trouble with sleep on M-series macs on occasion, but after turning off wake on LAN they’ve all slept exactly as expected for the past several years.
100% true story - until a couple of months ago, the best place to talk directly to Microsoft senior devs was on the macadmins slack. Loads of them there. They would regularly post updates, talk to people about issues, discuss solutions, even happy to engage in DMS. All posting using their real names.
The accounts have now all gone quiet, guess they got told to quit it.
Because Windows' UX is trash? Anyone with leverage over their employer can and should request a Mac. And in a hot market, developers/designers did have that leverage (maybe they still do) and so did get their Macs as requested.
Only office drones who don't have the leverage to ask for anything better or don't know something better exists are stuck with Windows. Everyone else will go Mac or Linux.
Which is why you see Windows becoming so shit, because none of the culprits actually use it day-to-day. Microsoft should've enforced a hard rule about dogfooding their own product back in the Windows 7 days when the OS was still usable. I'm not sure they could get away with it now without a massive revolt and/or productivity stopping dead in its tracks.
The problem of what happens when the author is unable to keep working on the source code has come up a LOT in the .NET space. One author (of both books and OSS) has even written up [0] the pro-active steps he's taken for when "The Emnuggerance" (as Pratchett called it) takes his abilities.
Specifically WHY they use Apple hardware is something I can only speculate on. Presumably it's easier to launch Windows on Mac than the other way around, and they would likely need to do that as .NET and its related technologies are cross platform as of 2016. But that's a complete guess on my part.
Am *NOT* a Microsoft employee, just an MVP for Developer Technnolgies.
reply