Well, here goes a sophomoric short life story. A programmer who started developing his skills with C, C++ or any other imperative language, arriving at JavaScript could think that he has nothing to learn except the syntax and a few syntactic sugars the language'd provide. Well, like every movie, there has to be a not so ambiguous twist, and here we go - It's definitely going to result in vain if that thought is his perseverance. In a contradiction, he might think this is a broad effort (quote: learning the language), but his goals are not to simply regurgitate the things he learnt, but to help boil down to what's important to get him on his way. Coming to the next part of his JavaScript life, he would understand that, it's merely a language which leaves out some of the basic structures and components that are so commonly used/needed. To reduce these boiler-plates and abstract browser inconsistencies, and to increase the level of tools/API, he would choose to use libraries which satisfy few/most of the requirements. He gets caught up in excitement and understands how easy development could be. And, it wouldn't be anytime sooner, that he would understand, these libraries, some of them, don't play well together. They overlap in functionality and features.

Like there comes a time in every developer's life where we arrive at some hypothesis of writing our own code for a library, he scrawls some code implementing some features. Before we continue, I would like to analyse his mistakes. May be he thought that his work'd be superior as he is eliminating most of the unnecessary stuff the library provides (or) may be he didn't do enough research on what's likely to be the most necessary thing in the application (or) may be there's just this one small thing that isn't quite right in the library, so he wants to rewrite it from scratch. The truth is, he has done it, I've done it, and you likely have too. The next phase of his life would be the annoying part. He realizes, but slowly, that he is doing nothing but what is so called as "re-inventing the wheel" and  whatever functionality he writes is already there under development for a significant amount of time, and the community that develops these things must have experienced something similar. He finds it funny that he wasn't the only one who fell into this ludicrous life.

Not a great scheme for an ending. I know. But some of you would've got the memo. :).

The advice section:

The long-evo idea about libraries is that these are developed in some remote part of the web and the community that develops these things is not available to approach by normal people. The idea, as certain as Heisenberg could be, is nothing but drivel.

One thing that most of us don't understand immediately is that, Learning JavaScript is not a one-time event. It'll happen over a long period of time, but (with a little/more stress on this point) it's important that you actually make it a priority to LEARN the language. Often people learn libraries, and not the language, a mistake which will certainly bite you in the end.

Blah blah stuff

Don't get me wrong about writing your own libraries. It's completely possible ;) .