What makes Javascript complex in your opinion?

I’m actively studying and trying to improve my JS skills. I’m at a point now where I’m focused on studying patterns. I have a thorough enough understanding of the basics but I’ve never worked on complex JS projects. Just focused on simple interactions for small projects.

I want to plan and organize my learning so I’m wondering what people consider to be complex within the world of JS. What areas require intense study and analysis? I find the world of JS patterns to be vague because I can’t quite tell if some patterns are immensely ideal for specific scenarios OR if there’s room for lots of flexibility. That’s where I am at the moment. Your thoughts?

This is what makes it complex, because it’s both. You’ll see people solving the same problem in a lot of different ways, with completely different architectures and design patterns. Just look at the frameworks to see what I’m talking about, compare the same simple program in Angular 1.x, Ember, and the React ecosystem. All 3 are very popular frameworks and solve the same basic problems in very different ways.

This is a good free book series. You don’t necessarily have to read the whole thing, but the titles of the books are the main concepts of JS. There are other resources to learn these and this book series may be a little bit too in depth.

  • async & performance
  • scope & closures
  • this & object prototypes
  • types & grammar

Just Alphabetical order, then the “es6 and beyond” book doesn’t really count in that list.

3 Likes

Okay. I intentionally framed my question the way it is because I suspected the real complexity is in the design and not/knowing when one pattern has any meaningful benefit. I think you answered that: sometimes a pattern make a real impact and then sometimes it doesn’t and then sometimes we don’t know. Sounds fair. Thanks for those links.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.