Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've been doing Javascript for a long time and have rarely run into issues with a lack of documentation. Maybe in projects with like 10 stars on Github ran by a single developer but in all of the major Node projects, you're going to have ample documentation and support for implementing said libraries. Just my take.


I've found most JS libraries are as the parent described, low coverage, garbage basic examples. Maybe this isn't the case on major huge libraries, but for your every day library, it's like there's a rule where you have to write the worst docs that still look pretty and all there at first glance, but totally useless and frustrating time and time again. The docs usually feel smug in the way they make it seems so easy and then they don't tell you how to do anything useful, like you are the one in the wrong for trying to use it for a real example or that you are an idiot because you can't just infer how everything would work without docs and examples. You have to learn from StackOverflow issues to understand how to actually do anything. That's my view. Maybe in general people just don't remember anything with good docs, and only the bad examples.

I feel like my ambitions for doing anything quickly are destroyed time and time again after finding a library to help me do it easily and fast the docs are the same old garbage. And these are the top starred libraries for their purpose. "How can this common thing to do on JS not have a huge, widely used and well document library that has existed for years?". It still blows my mind how after years and millions of people using it, so many libraries still have the worst docs.


Ever used Sequelize?


Haha! That’s the one that immediately came to mind. What a dumpster fire.


My question is why Node docs on nodejs.org don't have search




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: