Popular posts

As much as I agree, gave you a "spot on" and so forth, I do think that once you learn the underlying languages FIRST that it is important to go in and learn at least the basics of a few different such frameworks.

I've had to learn far more about any of them than I would ever want just so I have some clue how to fix them for clients. "Fixing" usually amounting to grabbing hold of them by the junk and ripping them clean out with as much passion and force as I can muster.

But I'm a bit like General Patton in that regard.

And what are the programming concepts in general?

Bhojendra Rauniyar

Code structure, language constructs (for example var vs let vs const), how the JSVM works under the hood (event loop), etc.

I think, even if you know enough JavaScript, you still have to learn the framework you're using and the standards and practices defined by that framework's community, it won't come magically, at least for me.

Bangash! The difference between learning frameworks and learning JS and then frameworks is, that you see the framework from a different perspective. It's not a way to develop for the web, but just another tool. Knowing enough JS enables you to easily recognize patterns and grasp, what the framework is doing, hence it's more like you understand the framework than you actually learn it. That way, just taking a look at the docs is often enough to start experimenting, whereas others, who learn a framework, have to go through long tutorials, always seeking new material to learn the nooks you already understand from your experience.

Yes, that's perfectly right!