And perhaps TTFM.
Translate the fucking manual either from broken chinese-english or the tech-lingo + missing context information which is almost every manpage on Linux, making it nearly useless for the average user unless you got hours and hours of time to understand all the adjacent concepts and commands.
Keeping the common user stupid is the better part of Mickeysoft’s business model. The proposed solution for every problem is guessing what MS’ silly nomenclature might actually mean while poking around in GUIs that do nothing but keep you busy. Then buy something from their app store. RTFM doesn’t work in a system that’s inconsistent and undocumented by design. That’s not the fault of RTFM as a concept but a travesty of it.
Unironically, if you bing Windows API related queries rather than googling them, you’re much more likely to find a relevant manual page that answers your question clearly. I wouldn’t be surprised if Google is actively worsening Windows-related queries to make Windows look bad and sell Android devices and Chromebooks. Another example is that googling msvcp140.dll not found or similar queries gives you loads of dodgy download this individual DLL here and put it in System32 and we promise we’ve not tampered with it websites instead of the page for the universal MSVC redistributable installer that’s the only supported way to get the DLL (and a bunch of other related ones) as an end user.
As for silly nomenclature, generally on Windows, API functions are much more likely to describe what they do and much less likely to be a town in Wales. If you don’t already know what fstat does, it’s much easier to guess that GetFileTime would be the right function to get a file’s last modification time than fstat, for example.
I have been told that the reason their publically available training, problem solving, and educational material is so terrible is because there is a secret printed guidebook somewhere that makes everything make sense and if everyone had it it could negatively impact the windows economy.
I do not know if that is true, but I have been told it and it does kind of explain why sites like learn.microsoft.com are so terrible that I would rather reread the world book encyclopedia 1969 edition from A to Z including the index than try to figure out how to run a single powershell command from the educational materials available on that site.
I just want to say I’m glad other people understand how ridiculous of a suggestion this is for fixing Windows problems. It has become such a low effort nonsensical approach because people don’t truly understand what it does and it feels like doing something. It’s the new ‘have you tried turning it off and on again.’ dism and sfc. Then when someone mentions how absurd the thinking is that this fixes anything but a small negligible fraction of issues, someone always chimes in how there was this one time where it worked for them. Perpetuating this low effort, almost useless approach to troubleshooting. I’ve fixed more issues with BIOS updates than I have with either of those tools.
This is a problem with more than just Microsoft. Any software (game, application, library, whatever) that has had many years of updates some of which are breaking, will have this problem with docs.
Oh you are using version 5.5.24 of xyzlib? All these docs are a mixture of stuff when 4.2.57 was out and stuff someone tried to update when 7.5.14 released.
try to RTFM for Microsoft…lol shits updated too much and all the old information is still there and outdated. convoluted mess of shit is all they are
still, RTFM…always
In order to RTFM one must first WTFM
And FTFM. Find the fucking manual.
And perhaps TTFM. Translate the fucking manual either from broken chinese-english or the tech-lingo + missing context information which is almost every manpage on Linux, making it nearly useless for the average user unless you got hours and hours of time to understand all the adjacent concepts and commands.
Keeping the common user stupid is the better part of Mickeysoft’s business model. The proposed solution for every problem is guessing what MS’ silly nomenclature might actually mean while poking around in GUIs that do nothing but keep you busy. Then buy something from their app store. RTFM doesn’t work in a system that’s inconsistent and undocumented by design. That’s not the fault of RTFM as a concept but a travesty of it.
Unironically, if you bing Windows API related queries rather than googling them, you’re much more likely to find a relevant manual page that answers your question clearly. I wouldn’t be surprised if Google is actively worsening Windows-related queries to make Windows look bad and sell Android devices and Chromebooks. Another example is that googling msvcp140.dll not found or similar queries gives you loads of dodgy download this individual DLL here and put it in System32 and we promise we’ve not tampered with it websites instead of the page for the universal MSVC redistributable installer that’s the only supported way to get the DLL (and a bunch of other related ones) as an end user.
As for silly nomenclature, generally on Windows, API functions are much more likely to describe what they do and much less likely to be a town in Wales. If you don’t already know what
fstatdoes, it’s much easier to guess thatGetFileTimewould be the right function to get a file’s last modification time thanfstat, for example.I have been told that the reason their publically available training, problem solving, and educational material is so terrible is because there is a secret printed guidebook somewhere that makes everything make sense and if everyone had it it could negatively impact the windows economy.
I do not know if that is true, but I have been told it and it does kind of explain why sites like learn.microsoft.com are so terrible that I would rather reread the world book encyclopedia 1969 edition from A to Z including the index than try to figure out how to run a single powershell command from the educational materials available on that site.
Have you tried sfc /scannow?
I just want to say I’m glad other people understand how ridiculous of a suggestion this is for fixing Windows problems. It has become such a low effort nonsensical approach because people don’t truly understand what it does and it feels like doing something. It’s the new ‘have you tried turning it off and on again.’ dism and sfc. Then when someone mentions how absurd the thinking is that this fixes anything but a small negligible fraction of issues, someone always chimes in how there was this one time where it worked for them. Perpetuating this low effort, almost useless approach to troubleshooting. I’ve fixed more issues with BIOS updates than I have with either of those tools.
I’ve just reinstalled windows every few years to deal with the unfixable issues
MSFT’s strategy is anti-documentation.
You want help?
Money Please!
(For clarity, I am being cheeky, but I am not joking.)
Microsoft documentation actually sucks information out of your brain and leaves you knowing less than before you read it.
This is a problem with more than just Microsoft. Any software (game, application, library, whatever) that has had many years of updates some of which are breaking, will have this problem with docs.
Oh you are using version 5.5.24 of xyzlib? All these docs are a mixture of stuff when 4.2.57 was out and stuff someone tried to update when 7.5.14 released.
Or the documentation is basically empty and tells you nothing at all (looking at you WinRT…)