3 ms·

I've never had problems with docs in JS, both node and browser. The MDN is a limitless ressource of information for the base language, and for libraries, well y

I've never had problems with docs in JS, both node and browser. The MDN is a limitless ressource of information for the base language, and for libraries, well you're going to get undocumented libraries in any language. It might be more "obvious" in JS because of the sheer amount of libraries, but I've found python libs that were very poorly documented too. This is a problem we should be HAPPY to have. Having libraries doing EXACTLY what we want, that's just missing docs, is better than the alternative I've found in many other languages : no libraries, so we have to do everything ourselves.

Roboprog 10y ago
I think the other poster meant 3rd party libraries, rather than the runtime. That said, the docs on (most of) the libraries I have used are generally pretty good. * Prototype - excellent docs (but library since overshadowed by jQuery) * jQuery - initially the docs were hard to follow, but they seem to have gotten better * Angular - good enough docs, and plenty of books on the larger concepts of how things fit together * moment.js - excellent docs * validatejs - excellent docs * Ramdajs - generally excellent docs, but I am less familiar with some of the FP concepts used in a few cases. The quality on some of the jQuery and Angular plugins varies a bit, admittedly.