Thanks for your apology. I can imagine this could happen to some random unknown software team but not to the supposed leader of the desktop. I believe this is honest apology but I am not sure I can trust that the issue was a bug and not a feature.
Thanks for your apology. I can imagine this could happen to some random unknown software team but not to the supposed leader of the desktop. I believe this is honest apology but I am not sure I can trust that the issue was a bug and not a feature.
The nature of the process used for most Feature Updates requires user data and preference migration and transfer. Notably, an entirely new installation of Windows is created and then existing user data and preferences are migrated or transferred as appropriate. There a variety of good reasons for this from a technical standpoint, but it has certain complexity and performance trade offs so is only used for certain types of updates.
Other types of updates use an in-place upgrade methodology that doesn’t require user data and preference migration but has certain characteristics that make it currently less suitable for major feature updates.
Thanks!
I have learned over the years that constraints and complexity are often abused to force one's way.
Not necessarily even consciously but if the collective train of thought in a company predominantly wants to prefer one outcome (i.e. market share, world domination) at the expense of another outcome (making users happy), then it tends to be that it's really easy to do things that result in the former and really complex and difficult to do things that result in the latter.
https://tritondatacenter.com/blog/the-power-of-a-pronoun
I completed the second decade of my software development career just a few years ago and it already seems like the third decade is speeding by. The first 17 years were in the *nix world and the last five have been as part of the Windows development team.
There have been many times that I have incorrectly assumed why a particular outcome occurred only to find out later as I suddenly became responsible for that same scenario that they had good reasons for their choices, and it was either the best possible outcome at the time given constraints or very much an unintended one.
In short, I have been extremely fortunate to have a number of mentors during my career that have helped me realize that perspective and empathy are key to understanding the complexities of software development. Through those experiences I have come to believe that software development is just as much a social discipline as a technical one, especially at scale.
Thanks for your kind consideration.
Your attitude is about fifteen years out of date. We live in a world where you have to turn off your wifi if you don't want to use a Microsoft account and any option Microsoft doesn't like us using is displayed in a tiny font that's almost the same color as the background. You don't think we can tell when we're being told to go fuck ourselves?
Thanks for chiming in :)
Gamifying browsing habits, monetizing MSN celebrity gossip on stock widgets and built-in search capabilities… etc… how are we supposed to be productive with such childish garbage?
I've been facinated by microsoft in recent years, they are really putting in a jekyll and hyde performance imo. They are consistently great at developer relations in some areas, with things like generous contributions to hackathons, visual studio code, github copilot, visual studio etc. But seem to make decisions in other areas, in my opinion particularly around the OS team, that needlessly antagonize a lot of people.
If I were living in a place where they had offices, working for MS is something I might consider one day, if only to be able to contribute to such important things that so many people use daily but I feel like I bounce back and forth on this opinion when such confusing decisions come out with seeming silence from microsoft's end.
I laughed out loud - actually. "Pass the butter Edge...."