[deaddodo]

I have no idea how you got that idea about Microsoft's developer documentation. It's always been one of the more robust options out there.

You can find full tutorials and documentation on the entirety of WinUI3, which is the literal bleeding edge; for instance.

[p_l]

You will also often see big chinking warnings that the site is no longer updated pointing you to homepage of current docs site, despite the APIs you're looking for being still current.

[deaddodo]

Is the new documentation lacking something you need? Is there some reason you don't use the outdated documentation, if it's working for you? Are you mad because there are redundant resources available to you?

I'm literally writing this to you on a Laptop exclusively running Fedora Linux. I do most of my development in OSS tools. I'm not some fanboy, yet despite that (or maybe due to that) I'm still able to recognize the very obvious fact that Microsoft has very robust documentation.

[p_l]

It's a problem because it makes one doubt whether they are in right place.

What's more, it's a step back from how well Microsoft did it in the past.

It's essentially like stepping into half-done move between two different places, and never being able to tell where did you put what.

They can, and in the past did, do better.

[deaddodo]

That doesn't answer any of the questions. That just introduces another vague problem of feelings.

[p_l]

Perception is important in discoverability of documentation, and yes, vibes are also part of it.

The complaint is that now it often ends up disjointed, especially when you're starting to search for a topic, and the links pointing you to "new site because this one no longer updated" don't point to the same topic (or area) on the new site.

Also, I have absolutely no idea where you come from with fanboyism or Microsoft hate as context in previous comment.