Do you think reading the manual is supposed to make those problems disappear or make them less frustrating for some reason? These kind of personal attacks just because their opinion differs from yours is low effort, specially given that they clearly mentioned "official recommendation" in multiple places implying they did go through the manual.
Do you read, in an exhaustive manner, the manual of each thing you ever buy? Or each programming language and library you ever used?
And if you decide you want to "win" here and thus stubbornly reply "yes" then I'd say "you are the vanishing minority".
Approaching a piece of tech -- that's yet unknown to you -- with expectations is natural. Sometimes with tragic results but still completely natural for us the humans.
This is a tangent and I'm not trying to win an argument, but I read the manuals for databases I use, along with many other bits of documentation like language specs. If anyone reading this is thinking of doing so then I highly recommend it.
My approach is to firstly skim the index and look at anything interesting, secondly just use the docs as a reference while I learn the technology, and thirdly come back and read them cover-to-cover (skimming over the boring/irrelevant bits).