Were just defining functions on the function itself instead of its prototype for 10 years? That's like avoiding using Promises because you can do things with callbacks.
Listen little boy... I know it hurts being so dumb and unexperienced and being young also means to know it all. But your time is probably better spent not trying to troll some seniors over the interwebs. I did a Google for you. Your time is better spent that way
I didn't say it was a reserved word you autistic douche, I said it was a keyword and it fits that definition. Go suck it and enjoy being wrong and a bad programmer in the same day.
Jimmies rusttled (or whatever little kids like you say), mission accomplished.
Trolling works better when you work with established facts: i.e. it is established that you're a little kid that doesn't even know what a keyword is and thinks using prototype is good and you need to learn this. Just calling me a bad programmer or saying I don't understand OOP just out of thin air is only going to work on little kids like you.
It is a keyword. And if you think it’s not useful you don’t know how to do OOP in JavaScript. So I’ve proven you to bad programmer. Also wrong. I’ve defeated you on every level. I have the higher ground.
11
u/[deleted] May 28 '19
yeah including you because first of all, that's not a keyword. Also trying to understand this bullshit isn't going to get you ANYWHERE in JS.
Source: I've written everything you can imagine in the past +10 years in JS and never needed that horsecrap.