• stevehobbes@lemmy.world
    3 years

    Jennifer is a lesbian. Her wife, now husband, who she’s proudly supportive of, is FtM, with 3 previous children that Jennifer adopted. Jennifer has never had penetrative sex with a man.

    • Kraivo@lemmy.world
      3 years

      Lesbian, in marriage with another lesbian and adopted 3 kids. Still virgin.

    • IGuessThisIsForNSFW@yiffit.net
      3 years

      I was thinking they were his kids from the previous marriage, though artificial insemination works just as well!

    • scottywh@lemmy.world
      3 years

      I’ve had a JavaScript certification for over a decade now and I think I hate you.

    • Comment105@lemm.ee
      3 years

      Java devs are prima mental gymnasticists, always able to make anything make sense.

      • Konlanx@feddit.de
        3 years

        JS !== Java

        Try Javascript some day!

        • We have truthy and falsy! Empty string or null? Yeah, that’s false!
        • Of course we can parse a string to number, but if it’s not a number it’s NaN!
        • null >= 0 is true!
        • Assign a variable with =, test type equality with == and test actual equality with ===. You will NEVER use the wrong amount of = anywhere, trust me!
        • Our default sort converts everything to string, then sorts by UTF-16 code. So yes, [1, 10, 3] is sorted and you are going to live with it.
        • True + true = 2. You know I’m right.

        Try Javascript today!

        • Durotar@lemmy.mldeleted by creator
          3 years

          Our default sort converts everything to string, then sorts by UTF-16 code. So yes, [1, 10, 3] is sorted and you are going to live with it.

          I’m not sure whether this is satire or not.

          • Konlanx@feddit.de
            3 years

            It’s not. The default sorter does that, because that way it can sort pretty much anything without breaking at runtime. You can overwrite it easily, though. For the example above you could simply do it like this:

            [3, 1, 10].sort((a, b) => a - b)

            Returns: [1, 3, 10]

            • sociablefish@programming.dev
              3 years

              The default sorter does that, because that way it can sort pretty much anything without breaking at runtime.

              who the fuck decided that not breaking at runtime was more important than making sense?

              this js example of [1, 3, 10].sort() vs [1, 3, 10].sort((a, b) => a - b) will be my go to example of why good defaults are important

        • Comment105@lemm.ee
          3 years

          I made the thing in the thing print “hello world” with C# once, is Javascript for me?

        • Beanie@programming.dev
          3 years

          True + true = 2. I’ve heard memes about Javascript, but jeez. It’s really that bad?

  • Throwaway@lemm.ee
    3 years

    Simple. Malformed data from.a bad actor. Always sanity check your shit.

  • Coreidan@lemmy.worldEnglish
    3 years

    If you have that much difficulty with JavaScript then it’s likely you’ll suffer with any language.

    • MakeAvoy@programming.dev
      3 years

      Except strict equality, that’s a JavaScript only problem. Imagine thinking "0" should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus !"0"=="0" is true. They couldn’t just throw away == and start over nooooo let’s add === . Utter madness

      • soloner@lemmy.world
        3 years

        Browser compatibility. Design flaws can’t easily be fixed like how other languages can just switch to a new major version and introduce breaking changes. ES must keep backwards compatibility so has had to do more additive changes than replacing behavior altogether so that older web pages pages don’t break.

      • JonEFive@midwest.social
        3 years

        Strict vs loose equality has gotten me so many times, but I can sort of see why they did it. The problem you mention with integers 0 & 1 is a major annoyance though. Like it is fairly common to check whether a variable is populated by using if (variable) {} - if the variable happens to be an integer, and that integer happens to be 0, loose quality will reflect that as false.

        But on the other side, there have been plenty of occasions where I’m expecting a boolean to come from somewhere and instead the data is passed as a text string. “true” == true but “true” !== true

  • royal_starfish@lemmy.world
    3 years

    And I thought kotlin was crazy with whatever (modifier: Modifier = Modifier) means to make it happy