• Crisps@lemmy.world
    link
    fedilink
    arrow-up
    46
    arrow-down
    1
    ·
    1 year ago

    Dynamically typed languages don’t scale. Large project bases become hard to maintain, read and refactor.

    Basic type errors which should be found in compilation become runtime errors or unexpected behavior.

    • TechieDamien@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      Not really a hot take. Why do you think most dynamic languages have the option to tack on static typing?

      • xigoi@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Depends on the community. In Lisp communities, for example, it’s very much a hot take. Which is a shame, because I’d love a statically typed Lisp-like language.

      • NBJack@reddthat.com
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        You know, I wish it wasn’t. Much of Amazon was on a version of Perl for years (and may still be) for almost all of their front end hosting. Facebook has transformed PHP into Hack (which is better for types, though technically not strongly typed), strongly suggesting they were running PHP until 2014. Let’s not forget what WordPress is still in PHP too.

    • MashedTech@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      We can feel it in our bones… And boy is it a pain when you find a huge codebase that is JS only or python without types. Fucking hell dealing with that shit