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.
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.