If that's all you're arguing about; querySelector is part of an API because the function doesn't do just one thing but different things depending on the string passed. It's an API to access the elements in the DOM. Sure we can "Google" and find someone explaining it differently, but OP's explanation has nothing wrong about it and you're being very harsh by saying things like that.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
A function doing different things based on the string passed does not make that function anything close to an API. And you, an intern, arguing with me, with 20+ years development experience, is laughable, especially because your argument isn't even close to being correct.
You using people's status to validate your point is laughable. You can say all you want about your 20 years experience but it has literally no value in this argument. Use that experience to make better points instead of just saying everyone is incorrect because a single thing doesn't fit exactly your understanding.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
Didn't read your reply, and won't be reading any more of them. If you don't like my replies, flag them. Or more constructively, give the following a read: dev.to/dexygen/dev-to-posts-tagged...
@simon
Landry
Like you wrote querySelector is part of API, nobody objects to this. But is not The API.
I hope you are not claiming that the Document object what exposes the querySelector method has 30+ APIs, one for each method. All those methods are part of the same API. Generally speaking: one API -> many objects with many methods.
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.
If that's all you're arguing about; querySelector is part of an API because the function doesn't do just one thing but different things depending on the string passed. It's an API to access the elements in the DOM. Sure we can "Google" and find someone explaining it differently, but OP's explanation has nothing wrong about it and you're being very harsh by saying things like that.
A function doing different things based on the string passed does not make that function anything close to an API. And you, an intern, arguing with me, with 20+ years development experience, is laughable, especially because your argument isn't even close to being correct.
You using people's status to validate your point is laughable. You can say all you want about your 20 years experience but it has literally no value in this argument. Use that experience to make better points instead of just saying everyone is incorrect because a single thing doesn't fit exactly your understanding.
Didn't read your reply, and won't be reading any more of them. If you don't like my replies, flag them. Or more constructively, give the following a read: dev.to/dexygen/dev-to-posts-tagged...
@simon Landry
Like you wrote querySelector is part of API, nobody objects to this. But is not The API.
I hope you are not claiming that the Document object what exposes the querySelector method has 30+ APIs, one for each method. All those methods are part of the same API. Generally speaking: one API -> many objects with many methods.