sherclod holmes @wallhackio@cat.family

@lapis you can mean shoebiscuit there if you're lucky!

@vaporeon_ @aescling @The_T yeah aesc probably didn't understand you meant "java for the client" instead of "java running on a server that it is expected to be used by a web client"

@soft ​!!!

pasta time

@The_T @vaporeon_ from "JavaScript: the first 20 years":

@soft ​?

@vaporeon_ no

@vaporeon_ @aescling (+ converting things to numbers is stupid though, i agree.)

@vaporeon_ @aescling javascript slander is a reportable offense.

@vaporeon_ @aescling reported.

@vaporeon_ @aescling + inexplicably is also a unary operator that, in some contexts, will try to convert its operand to a number

it is just barely better than moses' other great feat: https://www.youtube.com/watch?v=s8xImg-SVB8

my favorite bible story is when moses drew the fifth piece of exodia and used it to kill the pharaoh

@aescling @vaporeon_ @aescling @vaporeon_ The void keyword:

void (expression) is a shorthand for (expression), undefined. That is, void evaluates its operand and returns undefined. It was introduced to enable the following idiom:

<a href="javascript:void doAThing()">Click me to do a thing :3</a>

"javascript:" is a URL protocol that allows the user to write javascript to represent the response of a hyperlink. Whatever follows after "javascript:" will be evaluated, and if the expression is a string, it is treated as if it were a HTTP/HTTPS response document and the browser navigates to that page. (If navigation occurs, the URL does not change and no history entry is created.)

When associating a tag with javascript It was often desirable for pressing the link to NOT induce page navigation and instead simply perform a side effect. This is guaranteed if what follows "javascript:" is preceded by the void keyword.

var hoisting:

The JavaScript interpreter can be thought to have a "preprocessor" phase where all variable declarations are found and initialized. This means that it is possible to use a variable before it is declared since that variable will already be initialized from the "preprocessor" phase.

This pattern is called "hoisting". Since function declarations are also initialized during preprocessing, functions can also be hoisted. Combine this with the fact that variables declared with var are not block-scoped and you can get into some very confusing situations. I have encountered real production code which hoisted a variable declared within a switch statement containing hundreds of lines .

A tangent:

This is a bit tangential to what you asked but I think you'll find it amusing. Go see what the result of ('b' + 'a' + + 'a' + 'a').toLowerCase() is :]

A unique comment directive:

I can't explain this better than how it is described in "JavaScript: the first 20 years", which is a wonderful historical document available for free as a PDF here: https://dl.acm.org/doi/10.1145/3386327. (I plagiarized some of its content in this toot actually.)

While I'm admitting my sources I should mentioned that I consulted MDN's JavaScript documentation frequently for this post.

Best book of the Bible?

@amy hi

@monorail @coriander by "taking up less room" does that mean letting Amy step in

https://x.com/korin8399/status/1941425446668861848
I need a translator asap please