Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
iiii3907223dCannot agree. MSDN is pretty good. A bit dry, but not bad.
CptFox1766223dWhat I love about Rust is how much of the documentation can be translated into the type system.
MDN's JS documentation can be very hit or miss, especially in the form of "this function does <insert general concept here with no mention of details, input and return 'types' or edge cases>", so I kind of hate it sometimes.
1001101112770223dI'm with OP on this one. While C# seems to have a very thorough documentation, consulting it seems to leave me with more questions than I had going there, whether I found the answer to the original or not. Can't say F# docs are any better though - actually no, they are very lacking, kind of an afterthought if anything.
But the best documentations I've come across have definitely been for PHP and Vue (also, Vue-Bootstrap). Got to say Google Firebase documentation is very good, too.
SoldierOfCode519223dI have to diasagree with you on that one, I have used C# for years, and it's documentation is one of the best I've ever seen
12bitfloat6303222dIn what world does PHP have good documentation?? Actual question
Most manual pages are pretty hopeless that's why they have the "user contributed notes" section where you often find the actual information (which is also often wrong and/or out of date)
But to be fair, I haven't used much PHP so maybe I'm just missing something