41–50 of 51 posts
I find the Qt documentation to be excellent. If only Microsoft rose to the same level of helpfulness.
Rust docs are decent too but not quite as good as Qt.
The Android SDK is well documented with examples throughout and hyperlinked to examples and posts which explain some content in greater depth.
Really? Most of it seems to be machine generated from the code definitions - very little explanation, very little usage info. I find it terrible.
I think this is particularly a problem with Java docs because Java IDEs auto-insert useless documentation and people think "oh great it's documented".
For C and C++: cppreference.com. Why? - Very good overview pages. - Everything is cross-referenced. - Almost everything comes with an example of how to use it. - It's a wiki, so you can edit it yourself if you find anything lacking.
Maybe it’s just me being stupid, but cppreference, while absolutely of great quality, some c++ pages can be as cryptic as it gets. I know, the language is very much not trivial due to all these features, but for example the page about the different kind of l/rvalues is very very complex.
Earlier quoted context omitted.
Maybe it’s just me being stupid, but cppreference, while absolutely of great quality, some c++ pages can be as cryptic as it gets. I know, the language is very much not trivial due to all these features, but for example the page about the different kind of l/rvalues is very very complex.
Is there a simpler way to explain them, though, or is that level of complexity required for the explanation to be both 100% correct and complete?
Lots of good docs have you visually doing the setup/work, then you realise you can download/see a bunch of code for all the actions you did (e.g. everything UI doable is programmable and the tools taught you all the concepts), it minimises the actual programming, it is really hard/time consuming to mentaly translate API docs to code.