Both of you raise some good points. One thing that you both alluded to but didn't directly address is context. Actually on second reading, the linked post almost gets there but its still worth expanding on. I think it's important to learn not just the basics but have a very solid grasp of the 'vanilla' language and it's standard libraries, so that when you do use frameworks you can put them into context.
What I mean is that there are a lot of people who, like you mentioned, only know jQuery and don't know that the language they're writing in is JavaScript, or only know $FRAMEWORK and have no idea what comes standard with the language. When the time comes to switch frameworks, they get lost because they don't know where $OLD_FRAMEWORK ends and $LANGUAGE begins. So instead of thinking in terms of "I used $FEATURE in order to make X possible/easier in $LANGUAGE, now how can I do X in $NEW_FRAMEWORK", it becomes $OLD_FRAMEWORK-context-based like "I needed to do $FOO in $OLD_FRAMEWORK, how do I do that in $NEW_FRAMEWORK", without knowing that $FOO was required by the framework instead of the actual problem. Essentially the X-Y problem, wanting to know how to translate the solution instead of understanding why it was needed in the first place, because they have no concept of anything below the framework.
It's baffling, right? I guess it's easy for someone with no dev experience to learn how to query the DOM with jQuery. They technically are using JavaScript, but they think it's just jQuery. You'd be surprised how many people think this way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Both of you raise some good points. One thing that you both alluded to but didn't directly address is context. Actually on second reading, the linked post almost gets there but its still worth expanding on. I think it's important to learn not just the basics but have a very solid grasp of the 'vanilla' language and it's standard libraries, so that when you do use frameworks you can put them into context.
What I mean is that there are a lot of people who, like you mentioned, only know jQuery and don't know that the language they're writing in is JavaScript, or only know $FRAMEWORK and have no idea what comes standard with the language. When the time comes to switch frameworks, they get lost because they don't know where $OLD_FRAMEWORK ends and $LANGUAGE begins. So instead of thinking in terms of "I used $FEATURE in order to make X possible/easier in $LANGUAGE, now how can I do X in $NEW_FRAMEWORK", it becomes $OLD_FRAMEWORK-context-based like "I needed to do $FOO in $OLD_FRAMEWORK, how do I do that in $NEW_FRAMEWORK", without knowing that $FOO was required by the framework instead of the actual problem. Essentially the X-Y problem, wanting to know how to translate the solution instead of understanding why it was needed in the first place, because they have no concept of anything below the framework.
As one of my coworkers said: “Using the right technology for what you're solving, revolutionary.”
How can you not know Javascript if you use jQuery? In any case, you won't know the DOM API but that's all.
It's baffling, right? I guess it's easy for someone with no dev experience to learn how to query the DOM with jQuery. They technically are using JavaScript, but they think it's just jQuery. You'd be surprised how many people think this way.