MicrosoftI expect the loss of community input to be largest. I don't remember the website name, but when I go for help with a Microsoft product, I habitually scroll past any suggestions by Microsoft employees and look for the top community comment because the Microsoft responses are so rarely helpful.
I have read new FAQ. Thank you for that, aChrisDuarte.
> Many of our end users for Microsoft Learn are not familiar with GitHub; they don’t even have an account.
I think I now better understand the motivations behind the move. At first I was incredulous: What modern programmer isn't on GitHub? Then I realized: This means that at least a significant section of the Microsoft Learn target demographic are not, in fact, programmers. Microsoft Learn is more than the API documentation, which is what I access on it.
So the Microsoft Learn team has found that it can't satisfy both programmers and non-programmers with one feedback platform; therefore, the feedback experience is being split across approximate demographic lines.
At some point, I will encounter an issue for which I need to leave feedback using the new system, and the process is going to stink, and I'm going to add one more item to the list of Microsoft product interactions that make me rage due to lack of basic functionality. But by then it will be too late to protest. I oppose the move, but I can't prove that it will affect me yet; I'm not in the demographic Microsoft is targeting with the move. So I'm not sure what to say.
I do have one last argument, actually: In my experience, Microsoft feedback and community web interfaces are generally ridiculously buggy, whereas GitHub is not. New products generally have even more bugs than old ones. Therefore, the new platform will probably be quite buggy, and thus the move will result in a significant decrease in quality of user experience.
For example, look at this screenshot of this very post as I write it:
First, why should I save the post using a button if it is already auto-saved? Second, WHAT SAVE BUTTON?
