• Digital Mark
    link
    fedilink
    English
    -62 years ago

    Strong typing is for weak minds.

    You absolutely do not need a computer telling you what types you can put in a collection. Put an assert, write some unit tests, if you aren’t sure where data sources come from and can’t write a one-line comment.

    Dynamic typing makes you fast, it’s empowering. Try it and quit being so scared.

    • @[email protected]
      link
      fedilink
      English
      92 years ago

      I agree, strong typing is for weak minds. I work with a weak mind so I want strong typing.

      There’s no difference in speed between typing disciplines. In point of fact, there cannot be. You must know the structure of your data to program against it. Whether you write it down explicitly or implicitly changes nothing but the location you wrote it down.

    • GaveUp [she/her]
      link
      fedilink
      English
      52 years ago

      Hate to be a pedantic nerd but seeing as the subject is coding

      I think you mean static typing, not strong typing

      • @[email protected]
        link
        fedilink
        12 years ago

        Plus, most statically typed languages either do type inference by default or let you opt in somehow.

        Even Java, which is probably the reason everyone hated static typing for the first decade of the century or so, now has var.

      • GaveUp [she/her]
        link
        fedilink
        English
        12 years ago

        It’s not just the typing

        It’s the fact that you can be extremely flexible with data structures and variables

        E.g. you can have a list of strings and ints in Python but not java

      • @[email protected]
        link
        fedilink
        32 years ago

        I’m not any faster in languages without static types. It’s the opposite, I’m fastest when I can write accurate type hints, since it makes the editor experience much better.

    • T (they/she)
      link
      fedilink
      22 years ago

      Until you’re oboarded on a codebase that’s heavy on tech debt and that also doesn’t have proper documentation of the data being used.

      • Digital Mark
        link
        fedilink
        English
        12 years ago

        Terrible projects are terrible because of the developers, not because of the language.

        I find dynamic projects easier to refactor and fix, just write some tests and if it’s green bar before and after, you’re fine.

          • Digital Mark
            link
            fedilink
            English
            12 years ago

            All my career. They can’t program, they have no valid opinion about programming, as long as we finish the user stories. Which is several times faster in a nice dynamic language than a bondage language.