• Ethan@programming.devEnglish
      1·
      4 months ago

      Sure. But in a sane language doing something totally nonsensical like that is an error, and in a statically typed language it’s a compiler error. It doesn’t just silently do weird shit.

        • Ethan@programming.devEnglish
          1·
          4 months ago

          I was trying to make a point without starting a flamewar that was beside the point. Personally I’d never choose a dynamically typed language for a production system. That being said, Python and Ruby complain if you try to add an array, dict/hashmap, string, or number to another (of a different type) so they’re certainly more sane than JavaScript.

    • marcos@lemmy.world
      1·
      4 months ago

      It’s not even the coercion that is the problem here. The types are already bad by themselves.

    • dejected_warp_core@lemmy.world
      0·
      4 months ago

      I take this as less of a “I can’t use this intuitive feature reliably” thing and more of a “the truth table will bite you in the ass when you least expect it and/or make a mistake” thing.

      • flying_sheep@lemmy.ml
        2·
        4 months ago

        Just use a formatter. It’ll show you that the second one is two statements:

        1. {} (the empty block)
        2. +[] coerce an empty array to a number: new Number(new Array())
  • Mesa@programming.dev
    1·
    4 months ago

    I’m in this no-experience-to-apprenticeship program and everyone in my class thinks type coercion is the greatest thing ever.

  • Holzkohlen@feddit.de
    1·
    4 months ago

    It’s best not to touch anything web related, lest you want to go mad. It’s like the elder scrolls or laying eyes on some cosmic horror creature. Tbf this also goes for C++

      • marcos@lemmy.world
        1·
        4 months ago

        I don’t think “easier” is the right way to compare here. The C++ build tools will absolutely rewrite your code into something you can’t expect to guess, but it doesn’t make them hard to “use”.

  • dan@upvote.au
    1·
    4 months ago

    Use TypeScript, and nonsensical things like adding arrays to objects will be compile-time errors.

    • CanadaPlus@lemmy.sdf.org
      2·
      4 months ago

      Yup. The libraries underneath will still allow nonsense at runtime, though, and it will now be harder to see, so it’s a partial solution as done in standard practice.

      An all-TypeScript stack, if you could pull it off, would be the way to go.

      • dan@upvote.au
        1·
        4 months ago

        Most libraries have TypeScript types these days, either bundled directly with the library (common with newer libraries), or as part of the DefinitelyTyped project.

        • CanadaPlus@lemmy.sdf.org
          2·
          4 months ago

          DefinitelyTyped is the exact kind of thing I’m talking about. You put TypeScript definitions over things, but under the hood it’s still JavaScript and can fail in JavaScript ways.

    • Schadrach@lemmy.sdf.orgEnglish
      1·
      4 months ago

      By that logic what we really need is a modernization of Ada, where there are no compiler warnings and anything that would generate one in another language is instead a compiler error, everything is strongly typed, etc, etc.

      If you aren’t familiar with Ada, just imagine Pascal went to military school.

      • dejected_warp_core@lemmy.world
        1·
        4 months ago

        Pascal went to military school.

        I’m not in love with the idea, but a language that cuts out the BS has a sudden appeal when on a group/team project.

        • Schadrach@lemmy.sdf.orgEnglish
          1·
          4 months ago

          That analogy was chosen for a reason. Ada was originally developed by DOD committee and a French programming team to be a programming language for Defense projects between 1977 and 1983 that they were still using at least into the early 2000s. It’s based on Pascal.

          It was intended for applications where reliability was the highest priority (above things like performance or ease of use) and one of the consequences of that is that there are no warnings - only compiler errors, and a lot of common bad practices that will be allowed to fly or maybe at worst generate a warning in other languages will themselves generate compiler errors. Do it right or don’t bother trying. No implicit typecasting, even something like 1 + 0.5 where it’s obvious what is intended is a compiler error because you are trying to add an integer to a real without explicitly converting either - you’re in extremely strongly-typed country here.

          Libraries are split across two files, one is essentially the interfaces for the library and the other is it’s implementation (not that weird, and not that different than C/C++ header files though the code looks closer to Pascal interface and implementation sections put in separate files). The intent at the time being that different teams or different subcontractors might be building each module and by establishing a fixed interface up front and spelling out in great detail in documentation what each piece of that interface is supposed to do the actual implementation could be done separately and hypothetically have a predictable result.

  • Victor@lemmy.world
    1·
    4 months ago

    In node, I get the same result in both cases. "[object Object]"

    It’s calling the toString() method on both of them, which in the array case is the same as calling .join(",") on the array. For an empty array, that results in an empty string added to "[object Object]" at either end in the respective case in the picture.

    Not sure how we’d get 0 though. Anybody know an implementation that does that? Browsers do that maybe? Which way is spec compliant? Number([]) is 0, and I think maybe it’s in the spec that the algorithm for type coercion includes an initial attempt to convert to Number before falling back to toString()? I dunno, this is all off the top of my head.

    • PoolloverNathan@programming.dev
      1·
      4 months ago

      The inspector REPL evaluates as a statement-with-value (like eval), so the {} at the beginning is considered an empty block, not an object. This leaves +[], which is 0. I don’t know what would make Node differ, however.

      Edit: Tested it myself. It seems Node prefers evaluating this as an expression when it can, but explicitly using eval gives the inspector behavior:

      • Victor@lemmy.world
        1·
        4 months ago

        So there’s yet another level of quirkery to this bullshit then, it seems. 😆 Nice digging! 🤝

        I also noticed that if you surround the curlies with parentheses, you get the same again:

        > eval('{} + []')
0
> eval('({}) + []')
'[object Object]'
  • orangeboats@lemmy.world
    1·
    4 months ago

    This is why I try my damnedest not to write in weakly typed languages.

    string + object makes no logical sense, but the language will be like “'no biggie, you probably meant string + string so let’s convert the object to string”! And so all hell breaks loose when the language’s assumption is wrong.

    • Blackmist@feddit.ukEnglish
      1·
      4 months ago

      Some automatic conversion is fine.

      a=3+0.2

      print(“Hello {name}. You are {age} years old”)

      That kind of thing. But the principle of least surprise definitely applies. If you get to the point where you’re adding two booleans and a string, I feel like the language should at least say something. At least until the technology exists for it to physically reach out of your screen and slap you.

    • bahbah23@lemmy.world
      1·
      4 months ago

      I’ve read different defenses for JavaScript for cases like this, which usually runs somewhere from you shouldn’t be doing that anyway all the way up to if you just understood the language better you’d know why. While I agree with both of those points strongly as general principles, JavaScript also violates the principle of least surprise enough to make it concerning.

      For what it’s worth, I do like JavaScript. I really don’t think that there is any perfect programming language.