Microsoft is also not "micro" any longer... and not "soft". Devices, services, none social. Time to add another couple of paragraphs.
The definition of what a microcomputer is has certainly blurred such that what might be called a microcomputer is now more powerful than a supercomputer at the time Microsoft was created but that is the result of technology in general. Microsoft does not
make devices, they just sell devices made by others. I don't consider any of that to be relevant enough; we need to keep on subject, otherwise the real problems will become diluted.
The MSDN forums were originally intended to augment the documentation. Something happened and the original intent got lost so now StackOverflow augments the documentation. When I search the MSDN I
sometimes get mostly StackOverflow answers when I should be getting MSDN documentation. The main problem with that is that the StackOverflow people can be really arrogant and some of that arrogance seems to have infected the MSDN moderators
even.
Look at the documentation of processors; their architecture and instructions, such as the
Intel® 64 and IA-32 Architectures Software Developer’s Manual (PDF). Documentation such as that tends to be clear and precise, such as the section "6.2 STACKS". If we try to explain to Microsoft what clear and
precise documentation is then they seem incapable of understanding. More than half a century ago the basic design criteria of the COBOL language was a common business-oriented language that non-programmers can understand. UWP is far from that; it supports
shock and awe more than it supports business requirements and it can be highly complicated for relatively simple things. I wish I knew how to explain all that to Microsoft.
Sam Hobbs
SimpleSamples.Info
