My campus interview for a job at Oracle. In my technical interview, the interviewer read my CV and saw JS projects in it. He asked me, "Do all of you write JS because this is Oracle and JavaScript is by Oracle?" At first I thought he was pulling my leg. He wasn't.
I was so surprised that I wanted to laugh and bash out at him in front of his colleages. But then it was in college so of course I didn't.
I still cringe when I think about that day. π
"Use jQuery" as the answer to EVERY question -- typically by people who don't know enough HTML, CSS, or even JavaScript to be offering their opinion on the topic.
These 3 are most common one's I can recollect!
I keep coming across the following two misconceptions, on a fairly regular basis!
this)This one is a fairly common misconception, especially among the folks who make a ES5 to ES6 jump.
Arrow functions bypass the binding process which makes the outer context (this) available inside the arrow function.
I was surprised, when I first heard this; but this is a popular misconception which is also prevalent among experienced JavaScript developers.
JavaScript doesn't have classical inheritance β where you create instances (objects) out of blueprints (classes); but it has has prototypal inheritance, where instances (objects) inherit from other instances (objects). Everything in JavaScript is an object; and JavaScript is a prototypal-object oriented programming language.
you can use it for everything :) .... which is not wrong but the question is ... should you use it for everything ? you can write homepages in C as well ... I wouldn't recommend it though.
Juha Lindstedt
Creator of RE:DOM and Liike, web architect
1) the DOM is slow
2) the DOM is hard
3) you need a framework for everything
4) virtual DOM makes things faster
You can find my answers here: medium.com/re-dom/master-the-dom-bc1a2a06089b π