Javascript518.

 
Orlowsky: Dekok: In any case, prototypes are a legacy concept that doesn’t align either with the mental model of OOP programmers, *or* the actual execution model of modern JS engines.

Daughters: Profsimm: again, you’re free to think whatever about the language. Just don’t 1 attack other people; 2 spread misinformation about the language. It isn’t much to ask for

Standing: Profsimm: again, don’t spread misinformation.

Knickrehm: Dekok: you’re putting on a pedestal an abstraction which is kept entirely for BC and is present nowhere except in a spec.

Fuemmeler: Profsimm: if you don’t want to learn, that’s fine. But spreading misinformation is not acceptable

Falcon: Dekok: I don’t spread misinformation, V8 and other runtimes compile objects into cl***es

Ardd: Profsimm: have you ever tried following es-discuss? Or talking to the design committee in ES?

Formaggioni: Profsimm: they do not.

Sissell: Profsimm: “hidden cl***es” are not “cl***-based OO”

Rosinski: Two entirely different things.

Siembida: Dekok: hidden cl***es are cl***es, by your own definition up there.

Mildrum: Dekok: all objects are based on a cl***.

Hesselman: Profsimm: they’re not. You can also read about them here: http://bibliography.selflanguage.org/implementation.html

Creekbaum: Profsimm: are functions just a bunch of statements and a “jmp”?

Clasen: Http://debuggable.com/posts/understanding-hidden-cl***es-in-v8:4c7e81e4-1330-4398-8bd2-761bcbdd56cb

Andrulis: Wernert, what am I doing wrong here? http://jsfiddle.net/4k34hmea/

Castellanos: Something about call stack

Ends: Dekok: add in a stack-frame, and I’ll probably say yes

Feazell: It should eventually end, no?

Dugar: Oh great, you’re linking random blog posts who don’t even have any credibility in what they’re talking about. What a good argument! I am now thoroughly convinced

Trousdale: Dekok: I don’t care if you’re convinced. You’re some unemployed basement idiot that’s here 24/7, ready to argue with anyone about prototypes.

Heagy: Profsimm: again, stop attacking people.

Correl: Dekok, I don’t give a damn. If you’re butt-hurt, ban. It’ll make you feel better for a minute.

Marguez: Profsimm: him being here 24/7 to help people is nice, not idiocy

Moe: For me it doesn’t matter.

Servis: You’re toxic to this channel.

Wernert: Reductive reasoning and ad hominem. another day in Kimpel!

Haymer: This is a feisty channel and no mistake

Roker: Meh, he must be some random kid

Nottage: Well, she, in that case. But whatever

Trythall: Dekok: ah, good to meet :v

Laycock: Fixed it! http://jsfiddle.net/4k34hmea/1/

Wernert: Frogdr: it’s generally better to put the escape clauses first, like: if evalInt === 0 return true; if evalInt === 1 return false;

Wakley: Javascript518: For help, ask your question. Be patient. Code samples should be pasted in a paste service see !paste. Tell us 1 what you want to happen, 2 what is actually happening, and 3 any error messages you find see !describe and !debug.

Wakley: Javascript518: Show some code, but don’t paste it on the channel. For frontend code HTML/CSS/JS, you can provide a test case that we can run, so that we can help you: use https://jsfiddle.net , https://jsbin.com , or http://requirebin.com . For Node.js code, use sites like https://gist.github.com/ and https://bpaste.net .

Wakley: Javascript518: Error: https://gist.github.com/anonymous/affdf2a240655f007646 I’m trying have the While loop on line 2 prevent the user from typing anything other than the set strings. Even when a string is inputed exactly, the while loop continues infinitely. How can I stop the while loop once the parameters are true? is not a command.

Westmark: Https://gist.github.com/anonymous/affdf2a240655f007646 I’m trying have the While loop on line 2 prevent the user from typing anything other than the set strings. Even when a string is inputed exactly, the while loop continues infinitely. How can I stop the while loop once the parameters are true?

Montross: Javascript518 whileuserChoice != “scissors” “paper” “rock” will not function as you think, it will always return true because “paper” “rock is evaluated as or true or true. you will need to do something like this for your intended effect: whileuserChoice !== “scissors” userChoice !== “paper” userChoice !== “rock”