Re:Future JavaScript: what is still missing?
by agd621 on Sunday January 27, 2019 @02:54PM
(#19013460)
I don’t disagree that prototype is rare in real world practice but, anecdotally, it has come up in ~20% of my interviews in some fashion. That’s enough that I would be upset if the person teaching me JavaScript didn’t also teach me prototypal inheritance.
[ Parent
| on HN ]
Re:Future JavaScript: what is still missing?
by thekaleb on Sunday January 27, 2019 @03:54PM
(#19013727)
I only bring up the prototype to determine if I would classify the interviewee as a senior JavaScript developer or not.
Re:Future JavaScript: what is still missing?
by bpicolo on Sunday January 27, 2019 @06:15PM
(#19014370)
In modern times that's something you can easily throw far back in mindbank, because in practice using ES6 it almost never comes up, and it's super easy to do a quick refresher on the semantics.
If I didn't know that interviewers tended to ask about it in frontend inteviews (because they totally do), would never bother to keep up to date with the semantics
Re:Future JavaScript: what is still missing?
by adrianhel on Sunday January 27, 2019 @04:39PM
(#19013943)
Object.defineProperty('senior', {
value: true,
enumerable: false
})
Re:Future JavaScript: what is still missing?
by scarface74 on Sunday January 27, 2019 @06:03PM
(#19014304)
There are two things I would expect even a mid level developer to know - how prototypical inheritance works and how “this” works in JS.