Pick a JavaScript library. Odds are its documentation is going to be frustratingly inadequate. Some (e.g., Ramda) are quite nice. Many are crap.
Ask HN: What are the most popular libraries with the crappiest documentation?
51–56 of 56 posts
Re: Ask HN: What are the most popular libraries with the crappiest documentation?
#52Re: Ask HN: What are the most popular libraries with the crappiest documentation?
#53All the AWS stuff.
Re: Ask HN: What are the most popular libraries with the crappiest documentation?
#54The contents of this comment might be very outdated, but still... I remember working with the Dojo and Dijit JS libraries around 8 years ago. They were really great, high quality code, very well structured and designed... Except the documentation wasn't always clear, the examples online were for the older versions of the libraries (not fully compatible), and — my favorite and biggest pain — even the examples on Dijit…
Those libraries were fantastic, so far ahead of the rest of the pack at the time in terms of API design and code quality. I remember looking at it and being so happy to see that there was a js utility/cross-browser library written by engineers thinking in terms of software rather than "scripts".
Re: Ask HN: What are the most popular libraries with the crappiest documentation?
#55On the flip side, does anyone you examples of projects with perfect documentation?
The actual software design is great as well, single-handedly changed my mind about ORMs.