cross-posted from: https://lemmy.world/post/10094818

spoiler

Gender variability as declarations in JavaScript: const / let / var

Meme is based on Jordan Peterson “approival / disapproval” format, him being a conservative who disapproves of gender fluidity.

Transcript:

  • Jordan Peterson approval image: const gender;
  • Jordan Peterson angry image: let gender;
  • Jordan Peterson crying image: var gender;
  • andrewEnglish
    104•5 months ago

    Joke’s on you because they’re all still mutable objects behind the reference.

      • @soloner
        21•5 months ago

        Reassignment isn’t the same as mutation. But mutation depends on the type of value. If gender was a string like “female” it wouldn’t be mutable cuz strings are immutable in JS.

        • andrewEnglish
          5•5 months ago

          Yeah this is true. My joke makes an assumption about the type not being a primitive type.

      • andrewEnglish
        7•5 months ago

        var isn’t global unless it’s not inside a function. var is just function scoped, with declaration auto hoisted to the beginning of the function. let is a little more intuitive since you can’t refer to it before it’s been declared and has block scope rather than function scope.

          • @shotgun_crabEnglish
            6•5 months ago

            Classic javascript doing javascript things (this is why they introduced let and const)

          • CheezyWeezle
            3•5 months ago

            Kind of. With hoisting, the compiler/interpreter will find variable declarations and execute them before executing the rest of the code. Hoisting leaves the variables as undefined until the code assigning the value to the variable is executed. Hoisting does not initialize the variables.

            For example:

            console.log(foo);
            var foo;
            //Expected output: console logs ‘null’

            foo = ‘bar’;
            console.log(foo);
            var foo;
            //Expected output: console logs ‘bar’

            console.log(foo === undefined);
            var foo;
            //Expected output: console logs ‘true’

            This means you can essentially write your code with variable declarations at the end, but it will still be executed as though the declarations were at the beginning. Your initializations and value assignments will still be executed as normal.

            This is a feature that you should probably avoid because I honestly cannot think of any good use case for it that won’t end up causing confusion, but it is important to understand that every variable within your scope will be declared at the beginning of execution regardless of where it is written within your code.

          • andrewEnglish
            2•5 months ago
            var a;
(function() {
  a='hoisted';
  console.log(a);
  var a;
})()
console.log(a);

            Should log hoisted and then undefined, showing that you’ve assigned to the later-declared var a which was hoisted vs the external global a.